oracle enterprise manager 12c installation

Copyright 2015 Mokum Solutions, Inc. All rights reserved.Distribution of the Oracle Cloud Cookbook or derivative of the work in any form is prohibited unless prior permission is obtained from the Copyright holder.

About Mokum Solutions, Inc.Founded in March 2011, Mokum Solutions, Inc. specializes in the implementation, delivery and support of Oracle technologies in private and public clouds. Mokum corporate headquarters are located in San Francisco, CA http://mokumsolutions.comor call 1 415 252 9164

About the AuthorThe author of the Oracle Cloud Cookbook is none other than the owner of Mokum Solutions, Inc., Roddy Rodstein. Roddy is one of the most respected Oracle Cloud Computing experts, having designed and managed many of the worlds largest and most complex Oracle private clouds. Before establishing Mokum in March 2011, Roddy spent three years at Oracle on the Oracle VMand Oracle Linux team designing and supporting Oracle's largest and most complex customer environments. Before Oracle, Roddy spent six years at Citrix,designing and supporting Citrix's largest and most complex customer environments,Including Oracle's. With Mr. Rodsteins rich background and knowledge, there can be no better resource for revealing the Oracle Cloud recipe.

AudienceThe Oracle Cloud Cookbook is a comprehensive, field tested reference design thatguides you through each step to move to your Oracle software portfolio to an elasticOracle cloud using the Oracle VM product line, Oracle Linux, Oracle Engineered Systems managed by Oracle Enterprise Manager 12c, with total control over Oracle processor licensing.

Mokum is the only full-time Oracle virtualization integrator with the expertise to help you virtualize your Production, Test and DR Oracle workloads.

[email protected]
http://mokumsolutions.com/

Last update: 01/27/15

This chapter of the Oracle Cloud Cookbook describes how to plan for, install, and update Oracle Enterprise Manager 12c Release 4 on OracleLinux 6 using the Oracle Universal Installer (OUI).

Table of ContentsOracle Enterprise Manager 12c Installation and Upgrades IntroductionOracle Enterprise Manager 12c Inter Component Communication and Data ExchangeOracle Enterprise Manager 12c System Design ConsiderationsOracle Enterprise Manager 12c Server SizingOracle Enterprise Manager 12c Release 4 UpgradeOracle Enterprise Manager 12c Linux Operating System Installation PrerequisitesInstall the oracle-validated RPM on Oracle Linux 5Install the oracle-validated RPM from the Oracle Public Yum Repository on Oracle Linux 5Install the oracle-rdbms-server preinstall on Oracle Linux 6Install the oracle-validated or oracle-rdbms-server preinstall RPM from the Oracle Linux DVDDisable iptablesDisable SELinuxConfigure the /etc/hosts FileConfigure SSH and X11 ForwardingConfigure the ulimit /etc/security/limits.conf ValuesOracle Database 11g Enterprise Edition R2 (11.2.0.4.0) Installation PrerequisitesCreate the Required Directories using the Optimal Flexible Architecture (OFA) StandardAdjust the Shared Memory File System for the Database HostOracle Database 11g Enterprise Edition R2 (11.2.0.4.0) InstallationAutomate the Oracle Database Startup and ShutdownOracle Database 12c Release 1 Enterprise Edition (12.1.0.1.0) Installation PrerequisitesDownload and Stage the Database SoftwareCreate the Required Directories using the Optimal Flexible Architecture (OFA) StandardConfigure the ulimit, /etc/security/limits.conf and /etc/security/limits.d/oracle-rdbms-server-12cR1-preinstall.conf ValuesAs the Installing User, Setup ~/.bash_profileOracle Database 12c Release 1 Enterprise Edition (12.1.0.1.0) InstallationPost Installation StepsOracle Enterprise Manager 12c R4 InstallationConfigure the .bash_profile File with the Oracle Environment Variables (Oracle 11gR2 DB)Change Log

Share on Twitter Share on Linkedin

Oracle Enterprise Manager 12c Installation and Upgrades IntroductionOracle Enterprise Manager 12c is a systems management framework consisting of an Oracle database, Oracle WebLogic, a J2EE application, anapplication development frame work 11g (ADF) administrative Web GUI, server and client side plug-ins, and a client side agent. In the context ofOracle Enterprise Manager, the Oracle database repository is named the Oracle Management Repository or OMR. WebLogic is the J2EEplatform called the Oracle Management Service or OMS, that runs the Oracle Enterprise Manager 12c J2EE application. The administrativeWeb GUI is named Oracle Enterprise Manager Cloud Control. The client side agents are named the Oracle Management Agents or OMA. Theserver and client side plug-ins share a unique name for the managed product or technology. Monitored hosts are referred to as targets. All of theOracle Enterprise Manager components are commonly referred to as Oracle Enterprise Manager (OEM) or Enterprise Manager (EM).

The Oracle Management Repository, the Oracle Management Service along with the Oracle Management Agent can be installed on a singlex86-64 Linux host in an all-in-one configuration or in an n-tier configuration. Traditionally, production Oracle Enterprise Manager environmentsare not be placed on a single server, nor should the Oracle Management Repository be shared with production or test databases on the sameserver. For production, the Oracle Management Repository as well as WebLogic should be on dedicated virtual or physical servers. If your OracleEnterprise Manager environment starts out small, make sure to have a plan to scale out your Oracle Enterprise Manager infrastructure.

Each of the Oracle Enterprise Manager 12c components can be installed using the Oracle Universal Installer (OUI) GUI, or using silentinstallation scripts, or with the software only, configure later installation mode. The software only installation mode allows you to install only theOracle Enterprise Manager software binaries without any configurations. The software only installation mode is ideal if you want to install thesoftware at one point and configure the software later.

Figure 1 shows an all-in-one Oracle Enterprise Manager 12c installation with the Oracle Management Repository and the Oracle ManagementService on a single Linux node with three managed Oracle Linux hosts. All-in-one Oracle Enterprise Manager 12c installations are ideal forevaluations.

http://mokumsolutions.com

Mokum Solutions, Inc. +1 415 252-9164 4 of 52

Figure 2 shows a multiple node Oracle Enterprise Manager 12c installation with the Oracle Management Repository on one Linux node, theOracle Management Service on a second Linux node with three managed Oracle Linux hosts. Multiple node Oracle Enterprise Manager 12cinstallations are ideal for small, medium and large sites.

Figure 3 shows a high availability Oracle Enterprise Manager 12c installation with the Oracle Management Repository on a two node Linux RACcluster, the Oracle Management Service on two load balanced Linux nodes with three managed Oracle Linux hosts. High availability OracleEnterprise Manager 12c installations are ideal for medium and large sites.



There are several Oracle Enterprise Manager Cloud Control 12c Release 4 Installation and Upgrade options.

The first option is a fresh installation using the Oracle Enterprise Manager Cloud Control 12c Release 4 installation media. 1.The second option for Oracle Enterprise Manager on Release1 (12.1.0.1+BP1) or Release 2 (12.1.0.2), or on older releases 11g and 10.2.0.5,is to download the Oracle Enterprise Manager Cloud Control 12c Release 4 installation media, then upgrade directly to Oracle EnterpriseManager Release 4.

2.

As of this writing, Oracle Enterprise Manager 12c Release 1 (12.1.0.1) up to Release 2 (12.1.0.4) are supported on the following Oracle Linux andRed Hat Enterprise Linux x86-64 operating systems:

Oracle Linux and Red Hat Enterprise Linux 6+ (all 6 releases, i.e. 6.0 through 6U5)Oracle Linux and Red Hat Enterprise Linux 5+ (all 5 releases, i.e. 5.0 through 5U10)

As of this writing, the Oracle Management Repository is certified with the following database releases for Oracle Linux 5 and 6, x86_64:

12.1.0.1.011.2.0.4.011.2.0.3.011.2.0.2.011.2.0.1.011.1.0.7.010.2.0.5.0

Oracle Enterprise Manager 12c Inter Component Communication and Data ExchangeOracle Enterprise Manager 12c Could Control, the Oracle Management Repository, the Oracle Management Service and the Oracle ManagementAgents and Plug-ins can be on different hosts throughout your enterprise. Understanding Oracle Enterprise Manager's intra componentcommunication and data exchange will help you configure your firewalls in order to allow Oracle Enterprise Manager to operate in yourenterprise. During the Oracle Enterprise Manager installation, the default communication ports for each component will be selected andassigned. If the default ports are modified be sure to use the new port assignments when you configure your firewalls.

Table 1 shows the default ports used by Oracle Enterprise Manager.Service Default Port

Enterprise Manager Upload HTTP Port 4889 - 4898

Enterprise Manager Upload HTTPS (SSL) Port 1159, 4899 - 4908

Management Agent Port 3872

Management Repository Database Port 1521

Cloud Control Console HTTP Port 7788 - 7798

Cloud Control Console HTTPS (SSL) Port 7799 -7809

EM Domain WebLogic Admin Server HTTP Port 7001

EM Domain WebLogic Admin Server HTTPS (SSL)Port 7101 - 7200

Cloud Control Managed Server HTTP Port 7201 - 7300

Cloud Control Managed Server HTTPS (SSL) Port 7301 - 7400

WebLogic Node Manager HTTPS (SSL) Port 7401 - 7500

JVM Diagnostics Managed Server 3800

JVM Diagnostics Managed Server (SSL) 3801

Application Dependency and Performance RMIRegistry Port 51099

Application Dependency and Performance JavaProvider Port 5503

Application Dependency and Performance RemoteService Controller Port 55000

Oracle Enterprise Manager 12c System Design ConsiderationsThe Oracle Management Repository, the Oracle Management Service along with the Oracle Management Agent can be installed on a single hostin an all-in-one configuration or in an n-tier configuration. Traditionally, small Oracle Enterprise Manager environments are hosted on a singleserver, and large and medium Oracle Enterprise Manager environments are set-up in an n-tier configuration with the Oracle ManagementRepository as well as the Oracle Management Service (WebLogic) on dedicated virtual or physical servers. If your Oracle Enterprise Managerenvironment starts out small, make sure to have a plan to scale out your Oracle Enterprise Manager infrastructure.

For the Oracle Management Repository, scaling out means moving to RAC for the Oracle Management Repository database. An importantconsideration when scaling out an Oracle Enterprise Manager environment, is to determine if the underlying hardware where the Oracle



Management Repository database runs is capable to transition to RAC? If the hardware is not capable to transition to RAC, it is possible to moveand/or export the Oracle Management Repository database to a different system with more resources. If the Oracle Management Repository ishosted on an Oracle VM virtual machine, transitioning to RAC is a trivial operation.

Scaling out the WebLogic and Oracle Management Service tier entails adding a load balancing (SLB) solution to front end multiple WebLogicservers hosting the Oracle Management Service. Adding a load balancer with additional WebLogic servers introduces a virtual host name for theWebLogic cluster. Introducing a virtual host name into an existing Oracle Enterprise Manager environment will require a reconfiguration of all ofyour Oracle Management Agents to resolve to the new virtual host name. Reconfiguring a couple Oracle Management Agents is no trouble,although reconfiguring a lot of Oracle Management Agents would demand a long service window. When you deploy Oracle Enterprise Manager,consider using a virtual host name for the web tier.

An additional consideration when scaling out the WebLogic and Oracle Management Service tier is to provision shared storage to hosts the XMLfiles and the software library.

Oracle Enterprise Manager 12c Server SizingOracle Enterprise Manager 12c server sizing is calculated by a) total number of managed agents and targets, b) the future growth of your OracleEnterprise Manager environment and c) your organization's high availability requirements. For example, if you know the total number ofmanaged agents and targets, sizing WebLogic and the Oracle database is as simple as following Table 1, Table 2, and Table 3. As you add moreagents and targets, it is important to consider the future growth of your Oracle Enterprise Manager environment as well as the ability to scale upor to scale out with additional CPU, RAM and storage.

Table 1 shows the recommended Oracle Enterprise Manager hardware requirements for an evaluation, small, medium and large deployment.

Deployment Size OMS Hosts OMS CPUCoresOMSRAM

DBHosts

DB CPUCores

DBRAM

All-in-oneInstall Recommendation

Eval < 10 agents < targets 1 2 *4 GB 1 2 6 Yes

Small < 100 agents < 1000targets 1 2 *6 GB 1 2 6 No

Medium < 1000 agents 1000 agents >10,000 targets 2 4 *6 GB

2*2 with

RAC

8 for each RACnode 16 No

* To use BI Publisher add 1.5 GB of RAM.

Table 2 shows the minimum storage requirments for the database server hosting the Oracle Management Repository.

Deployment Size MGMT_TABLESPACE (GB) MGMT_ECM_DEPOT_TS (GB) TEMP ARCHIVE LOG AREA (GB)

Eval < 10 agents < targets 15 GB 1 3 Off

Small < 100 agents < 1000 targets 50 GB 1 10 25

Medium < 1000 agents < 10,000 targets 200 GB 4 20 100

Large > 1000 agents > 10,000 targets 300 GB 8 40 150

Table 4 shows the minimum storage requirements for a standalone Oracle Management Agent installation.

Platform Storage TMP Directory

Linux 32 bit 1.2 GB 400 MB

Linux x86_64 1.2 GB 400 MB

Oracle Enterprise Manager 12c Release 4 UpgradeThis section describes how to upgrade Oracle Enterprise Manager 12c Release 2 (12.1.0.2) or 12c Release 3 (12.1.0.3) to 12c Release 4(12.1.0.4). Before starting the Release 4 upgrade, it is necessary to meet several database and operating system prerequisites.

1) First, apply the appropriate Database patch(s) to the Oracle Management Repository database.

Table 5 shows the Database patch matrix:Oracle Database Release Patches

Oracle Database 11 Release 1 (11.1.0.7) On Linux apply patch 17082366 (Patch Set Update 17), then apply patch 9577583,and patch 8405205.

Oracle Database 11g Release 2 (11.2.0.1) On Linux apply patch 12419378 (Patch Set Update 6).

Oracle Database 11g Release 2 (11.2.0.2) On Linux apply patch 11061801 and patch 9748749.

Oracle Database 11g Release 2 (11.2.0.3), 10g Release 2(10.2.0.5) On Linux apply patch 11061801.



Oracle Database 12c Release 1 (12.1.0.1) On Linux apply patch 16619249, and patch 13496395.

Note: Consult the patch README for the Database patch installation details.

2) Confirm that the privileges for the DBMS_RANDOM package meets Oracle's prerequisites. As the installing user, i.e. the user account used to install the Oracle database, set thefollowing environment variables.

$ export ORACLE_SID=$ export ORAENV_ASK=NO$ . oraenv$ export ORAENV_ASK=YES

# sqlplus / as sysdbaGRANT EXECUTE ON dbms_random TO dbsnmp; GRANT EXECUTE ON dbms_random TO sysman;REVOKE EXECUTE ON dbms_random FROM public;

3) Confirm that there are no invalid objects in the Oracle Management Repository database.

SELECT owner, object_name, object_typeFROM dba_objects WHERE status = 'INVALID'AND owner IN ('SYS', 'SYSTEM', 'SYSMAN', 'MGMT_VIEW', 'DBSNMP', 'SYSMAN_MDS');

If you need to recompe, the following examples show the syntax:EXEC UTL_RECOMP.recomp_serial('SYS');EXEC UTL_RECOMP.recomp_serial('DBSNMP');EXEC UTL_RECOMP.recomp_serial('SYSMAN');

4) Confirm that the "/etc/security/limits.conf" file has the number of file descriptors to at least 4096. As root, edit the /etc/security/limits.conf fileand confirm that the following line exists:oracle soft nofile 4096

5) Backup the Oracle Management Repository database.

6) Copy the emkey using the following commands. The WebLogic user account name and password will be required to copy the emkey. Changethe path, hostname, and database SID to meet your requirments.$ export OMS_HOME=/u01/app/oracle/product/Middleware/oms$ OMS_HOME/bin/emctl config emkey -copy_to_repos_from_file -repos_host -repos_port 1521 -repos_sid -repos_user sysman -emkey_file $OMS_HOME/sysman/config/emkey.ora

Oracle Enterprise Manager Cloud Control 12c Release 3 Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.Enter Admin User's Password : Enter Enterprise Manager Root (SYSMAN) Password : The EMKey has been copied to the Management Repository. This operation will cause the EMKey to become unsecure.After the required operation has been completed, secure the EMKey by running "emctl config emkey -remove_from_repos".$

7) Stop the Oracle Management Service.$OMS_HOME/bin/emctl stop oms -all

8) Create a directory for the out-of-place Oracle Management Service upgrade.$ mkdir -p /u01/app/oracle/product/MiddelwareR4

9) Unzip the Oracle Enterprise Manager R4 software into a staging directory. Change the path to meet your requirments.$ mkdir -p /u01/app/oracle/product/MiddelwareR4$ unzip -d /u01/scratch em12104_linux64_disk1.zip$ unzip -d /u01/scratch em12104_linux64_disk2.zip$ unzip -d /u01/scratch em12104_linux64_disk3.zip$ cd /u01/app/oracle/oms12cr4

10) Run the Oracle Universal Installer (OUI) to begin upgrade.$ cd /u01/scratch$ ./runInstallerStarting Oracle Universal Installer...

Checking Temp space: must be greater than 400 MB. Actual 12133 MB PassedChecking swap space: must be greater than 150 MB. Actual 14322 MB PassedChecking monitor: must be configured to display at least 256 colors. Actual 16777216 PassedPreparing to launch Oracle Universal Installer from /tmp/OraInstall2014-06-24_05-30-24AM. Please wait $

After a couple moments, the Oracle Universal Installer will appear and show Step 1 or 9, the My Oracle Support Details screen.

My Oracle Support Details screenOn the My Oracle Support Details screen to receive information from Oracle (optional), enter your email address, select the I wish to receivesecurity updates via My Oracle Support checkbox, enter your My Oracle Support Password and click the Next button, or uncheck the Iwish to receive security updates via My Oracle Support checkbox and click the Next button.Figure 4



Software Updates screenOn the Software Updates screen select one of the following software update options, then click Next to proceed:

Skip to Skip looking for updatesSearch for Updates (Prerequisites, Critical Patches, Interim Patches, etc.)

Local Directory (select this option if you have allready pulled down the Prerequisites, Critical Patches, Interim Patches, etc.)My Oracle Support (select this option to search My Oracle Support for the Prerequisites, Critical Patches, Interim Patches, etc.)

For this example we selected Search for Updates, and My Oracle Support, entred a User Name and Password, then clicked Search forUpdates, there were no updates. Click the Next button to proceed. Figure 5

Prerequisite Checks screenOn the Prerequisite Checks screen the installer checks the system prerequisites. Failed steps can be fixed and be retested or justignored. The Prerequisite Checks screen shows if the minimum system requirements to perform the installation are met.

Click Rerun if you fixed the problems and you would like to verify the system requirements again.



Click Ignore to ignore the problems and move forward with the upgrade.

Click the Next button to proceed.Figure 6

Installation Types screenOn the Installation Types screen select Upgrade and One System Upgrade. The existing Middelware home should automataically seletced.Click the Next button to proceed.Figure 7

Installation Details screenOn the Installation Details screen enter the new R4 Middleware home. Use the Browse button to select, or type in the R4 Middleware HomeLocation path. The Host Name should auto-populate. If the hostname does not auto-populate, enter the fully qualified domain name (FQDN) ofthe host.Click the Next button to proceed.Figure 8



Database Connection Details screenOn the Database Connection Details screen enter the Database SYS and SYSMAN Passwords, select the Confrim that you have backedup the Management Repository checkbox. Click the Next button to proceed.Figure 9

Error screenOn the Error screen click Yes to automatically fix the issues and proceed.Figure 10



Plug-ins Upgrade screenOn the Plug-ins Upgrade screen accept the defaults and click Next to proceed. Figure 11

Select Plug-ins screenOn the Select Plug-ins screen select any additional Plug-ins. Click the Next button to proceed.Figure 12



Extend WebLogic Server Domain screenOn the Extend WebLogic Server Domain screen enter the Admin Server Host name, Admin Server Port, WebLogic UserName and Password. The OMS Instance Base Location should auto-populate. Click the Next button to proceed.Figure 13

Review screenOn the Review screen confirm the installation setting and continue if correct. Click the Install button to proceed with installation.Figure 14



Installation Progress Details screenOn the Installation Progress Details screen you can monitor the progress of the installation until user input is required.Figure 15

Execute Configuration scripts screenAs requested on the Execute Configuration scripts screen, as the root user, run the allroot.sh script.Figure 16



# /u01/app/oracle/product/MiddlewareR4/oms/allroot.sh

Starting to execute allroot.sh .........

Starting to execute /u01/app/oracle/product/MiddlewareR4/oms/root.sh ......Running Oracle 11g root.sh script...The following environment variables are set as:ORACLE_OWNER= oracleORACLE_HOME= /u01/app/oracle/product/MiddlewareR4/omsEnter the full pathname of the local bin directory: [/usr/local/bin]:Copying dbhome to /usr/local/bin ...Copying oraenv to /usr/local/bin ...Copying coraenv to /usr/local/bin ...Entries will be added to the /etc/oratab file as needed byDatabase Configuration Assistant when a database is createdFinished running generic part of root.sh script.Now product-specific root actions will be performed./etc existCreating /etc/oragchomelist file.../u01/app/oracle/product/MiddlewareR4/omsFinished execution of /u01/app/oracle/product/MiddlewareR4/oms/root.sh ......Starting to execute /u01/app/oracle/product/agentr4/core/12.1.0.4.0/root.sh ......Finished product-specific root actions.Finished execution of /u01/app/oracle/product/agentr4/core/12.1.0.4.0/root.sh ......#

Installation Progress Details screenOnce the Installation Progress Details screen shows 100%, you will be preseneted with the FInish screen.Figure 17



Finish screenThe Finish screen shows the location of the setupinfo.txt file and the URLs for Oracle Enterprise Manager Cloud Control and the WebLogicAdmin server. Click the Close button to close the installation program

Note: The details from the Finish screen are also available in the file setupinfo.txt file.

Figure 18

The following is an example of the setupinfo.txt file from this install.$ cat /u01/app/oracle/product/MiddlewareR4/oms/install/setupinfo.txtThis information is also available at: /u01/app/oracle/product/MiddlewareR4/oms/install/setupinfo.txt

See below for information pertaining to your Enterprise Manager installation:

Use the following URL to access:



1. Enterprise Manager Cloud Control URL: https://oem-sisko.local.mokumsolutions.com:7802/em 2. Admin Server URL: https://oem-sisko.local.mokumsolutions.com:7102/console

The following details need to be provided during the additional OMS install: 1. Admin Server Hostname: oem-sisko.local.mokumsolutions.com 2. Admin Server Port: 7102

You can find the details on ports used by this deployment at : /u01/app/oracle/product/MiddlewareR4/oms/install/portlist.ini

NOTE:

An encryption key has been generated to encrypt sensitive data in the Management Repository. If this key is lost, all encrypted data in theRepository becomes unusable.

A backup of the OMS configuration is available in /u01/app/oracle/product/gc_inst/em/EMGC_OMS1/sysman/backup on hostoem-sisko.local.mokumsolutions.com. See Cloud Control Administrators Guide for details on how to back up and recover an OMS.

NOTE: This backup is valid only for the initial OMS configuration. For example, it will not reflect plug-ins installed later, topology changes like theaddition of a load balancer, or changes to other properties made using emctl or emcli. Backups should be created on a regular basis to ensurethey capture the current OMS configuration. Use the following command to backup the OMS configuration:

/u01/app/oracle/product/MiddlewareR4/oms/bin/emctl exportconfig oms -dir

The upgrade is now complete and ready for login. You will be presneted with the Accessibility Preferance screen. Selct your AccessibilityPreferance or click I'll deal with this later to access Cloud Control.Figure 19

Oracle Enterprise Manager 12c Linux Operating System Installation PrerequisitesOracle recommends installing Enterprise Linux using the default software package selections without any customization. Using the defaultsoftware packages without customizations includes most of the prerequisite packages for Oracle Enterprise Manager 12c, and helps limit thenumber of manual prerequisites. After an Oracle Linux and/or Red Hat Enterprise Linux installation, for 5+, install the oracle-validated RPM,for 6+ install the oracle-rdbms-server-11gR2-preinstall or oracle-rdbms-server-12cR1-preinstall (dependent on db version), to meet all ofthe remaining Oracle Enterprise Manager 12c software RPM prerequisites as well as the system configuration prerequisites.

Install the oracle-validated RPM on Oracle Linux 5The oracle-validated RPM simplifies meeting the software and system configuration prerequisites for installing Oracle Enterprise Manager 12c.Installing the oracle-validated RPM automatically installs all of the software RPM prerequisites for the Oracle Enterprise Manager 12c and theOracle Database as well as meeting the system configuration prerequisites, such as creating an oracle user and the oinstall and dba groups,configuring the sysctl.conf settings, system startup parameters, user limits, and driver parameters.

The oracle-validated RPM is available at the Oracle Unbreakable Linux Network, on the Oracle Linux media, and from the Oracle public yumrepository. The oracle-validated RPM can be installed from the Oracle Unbreakable Linux Network by typing "up2date --install oracle-validated",ULN registration and a valid Linux CSI is required. If you do not have access to Oracle Unbreakable Linux Network, the oracle-validated RPMcan be installed from a local DVD repository as well as from Oracle' public yum repository.



Install the oracle-validated RPM from the Oracle Public Yum Repository on Oracle Linux5To install the oracle-validated RPM from the Oracle public yum repository, as root type the following commands:# cd /etc/yum.repos.d/# wget http://public-yum.oracle.com/public-yum-el5.repo# yum install oracle-validated

Note: The oracle-validated RPM is only for Oracle Linux 4 and 5, not 6. For Oracle Linux 6, install the oracle-rdbms-server preinstall RPM.

By default the public-yum-el5.repo file has the el5_latest RPM channel enabled. The Oracle public yum server latest RPM channel include thebase OS version installation RPM packages along with the latest software patches, updates and fixes. Patch jobs using the latest RPM channelupdate hosts to their respected latest version update with the latest software patches, updates and fixes. A patch job executed on a Oracle Linux5U5 host would update the host from 5U5 to 5U10 with the latest latest software patches, updates and fixes. To keep a host at its respectedupdate level, a valid CSI and the Unbreakable Linux Network is required. With the Unbreakable Linux Network, it is possible to register a hostthe el*/ol*_base channel along with the el*/ol*_patch RPM channel. When hosts are patched using the el*/ol*_base and el*/ol*_patch RPMchannels, the hosts are patched with the latest software patches, updates and fixes from their respected update channel, i.e. 5, 5U1, 5U2 and5U3, etc...

Note: If the host is not 5U10/latest, once the oracle-validated is installed, edit the public-yum-el5.repo file and disable the el5_latest RPM channelby changing enabled=1 to enabled=0.

The next example shows the el5_latest entry from the public-yum-el5.repo file with the enabled=1 flag, i.e. the el5_latest RPM repository isenabled. [el5_latest]name=Oracle Linux $releasever Latest ($basearch)baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/latest/$basearch/gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oraclegpgcheck=1enabled=1

The next example shows the el5_latest entry from the public-yum-el5.repo file with the enabled=0 flag, i.e. the el5_latest RPM repository isdeisabled. [el5_latest]name=Oracle Linux $releasever Latest ($basearch)baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/latest/$basearch/gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oraclegpgcheck=1enabled=0

A good practice after the oracle-validated RPM installation is to set the password for the oracle user created during the script. As root, type thefollowing:$ passwd oracleChanging password for user oracle.New password:Retype new password:passwd: all authentication tokens updated successfully.$

Install the oracle-rdbms-server preinstall on Oracle Linux 6The oracle-rdbms-server-11gR2-preinstall or oracle-rdbms-server-12cR1-preinstall (dependent on db version) RPM, formally know asoracle-validated, simplifies meeting the software and system configuration prerequisites for installing the Oracle Database, Oracle EnterpriseManager, and many other Oracle technology products on Oracle Linux 6. Installing the oracle-rdbms-server-11gR2-preinstall or oracle-rdbms-server-12cR1-preinstall RPM automatically installs all of the software RPM prerequisites for Oracle Database and Oracle EnterpriseManager, as well as meeting the system configuration prerequisites, such as creating an oracle user and the oinstall and dba groups, configuringthe sysctl.conf settings, system startup parameters, user limits, and driver parameters. After the installation of the oracle-rdbms-server-11gR2-preinstall or oracle-rdbms-server-12cR1-preinstall RPM, you can confidently start the Oracle Database and Oracle Enterprise Managerproduct installer. The oracle-rdbms-server-11gR2-preinstall and oracle-rdbms-server-12cR1-preinstall RPMs are available at the OracleUnbreakable Linux Network, on the Oracle Linux media, and from the Oracle public yum repository.

Note: A prerequisite for the oracle-rdbms-server-11gR2-preinstall and oracle-rdbms-server-12cR1-preinstall RPMs is the UnbreakableEnterprise Kernel (UEK).

To install the oracle-rdbms-server preinstall RPM from the Oracle public yum repository, as root type the following commands:# cd /etc/yum.repos.d/# wget http://public-yum.oracle.com/public-yum-ol6.repo

Install the oracle-rdbms-server-12cR1-preinstall package as the root user:# yum install oracle-rdbms-server-12cR1-preinstall

Install the oracle-rdbms-server-11gR2-preinstall package as the root user:# yum install oracle-rdbms-server-11gR2-preinstall

By default the public-yum-ol6.repo file has the ol6_latest RPM channel enabled. The Oracle public yum server latest RPM channel include thebase OS version installation RPM packages along with the latest software patches, updates and fixes. Patch jobs using the latest RPM channelupdate hosts to their respected latest version update with the latest software patches, updates and fixes. A patch job executed on a Oracle Linux6U1 host would update the host from 6u1 to 6U5 with the latest latest software patches, updates and fixes. To keep a host at its respected update



level, a valid CSI and the Unbreakable Linux Network is required. With the Unbreakable Linux Network, it is possible to register a host theel*/ol*_base channel along with the el*/ol*_patch RPM channel. When hosts are patched using the el*/ol*_base and el*/ol*_patch RPM channels,the hosts are patched with the latest software patches, updates and fixes from their respected update channel, i.e. 6, 6U1, 6U2 and 6U3, etc...

Note: If the host is not 6U5/latest, once the oracle-rdbms-server preinstall is installed, edit the public-yum-ol6.repo file and disable the el6_latestRPM channel by changing enabled=1 to enabled=0.

The next example shows the el6_latest entry from the public-yum-el6.repo file with the enabled=1 flag, i.e. the el6_latest RPM repository isenabled.[ol6_latest]name=Oracle Linux $releasever Latest ($basearch)baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/$basearch/gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oraclegpgcheck=1enabled=1

The next example shows the el6_latest entry from the public-yum-el6.repo file with the enabled=0 flag, i.e. the el6_latest RPM repository isdisabled.[ol6_latest]name=Oracle Linux $releasever Latest ($basearch)baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/$basearch/gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oraclegpgcheck=1enabled=0

A good practice after the rdbms-preinstall RPM installation is to set the password for the oracle user created during the script. As root, type thefollowing:$ passwd oracleChanging password for user oracle.New password:Retype new password:passwd: all authentication tokens updated successfully.$

Install the oracle-validated or oracle-rdbms-server preinstall RPM from the OracleLinux DVDLinux maintains yum repositories in the /etc/yum.repos.d/ directory. For example, to setup a DVD repository, mount the Oracle Linux DVD ISO file,and create a file in the /etc/yum.repos.d/.repo directory that instructs the yum client to use the DVD repository. The next examplesshows the syntax of a .repo file pointing to a mounted Oracle Linux DVD in the /mnt/dvd/ directory.

# cat /etc/yum.repos.d/ol-5U7-dvd.repo[ol5_u7_dvd]name=Oracle Linux $releasever - $basearchbaseurl=file:///mnt/dvd/Server/enabled=1gpgcheck=1gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle

Note: Change the folloiwing sections to meet you DVD requirments:

Change the name of the .repo file. For example, for 5U10, ol-5U10-dvd.repo, or for 6U5, ol-6U5-dvd.repo.Change the name of the respitory [ol5_u7_dvd] to meet your requirments, i.e. for 5U10, [ol5_u10_dvd], or for 6U5, [ol6_u5_dvd].Replace baseurl=file:///mnt/dvd/Server/ with your DVD mount point.

Once the DVD is mounted and the .repo file is created, as root type the following command:# yum install oracle-validated (For Oracle Linux 5)or# yum install oracle-rdbms-server-11gR2-preinstall (for Oracle Linux 6)or # yum install oracle-rdbms-server-12cR1-preinstall (for Oracle Linux 6)

A good practice after the rdbms-preinstall RPM installation is to set the password for the oracle user created during the script. As root, type thefollowing:$ passwd oracleChanging password for user oracle.New password:Retype new password:passwd: all authentication tokens updated successfully.$

Disable iptablesiptables is a userspace firewall application used to configure the Linux IPv4 and IPv6 packet filtering rulesets. iptables is installed and enabled bydefault on Oracle Linux with a default policy and ruleset in /etc/sysconfig/iptables. iptables rules can be configured at the command line as well aswith the system setup utility, i.e. "/usr/bin/setup".



Host firewalls, for example iptables, are a fundamental part of an information security program. If your information security program requireshost firewalls, a best practice is to configure host firewalls during the last phase of the Enterprise Manager deployment.

iptables can be disabled by typing the following command as root.# service iptables stop && service ip6tables stop && chkconfig iptables off && chkconfig ip6tables off

iptables can be re-inabled by typing the following command as root.# service iptables start && service ip6tables start && chkconfig iptables on && chkconfig ip6tables on

Disable SELinuxSecurity Enhanced Linux (SELinux) is a default Linux feature that offers mandatory access controls, using Linux kernel security modules (LSM)along with user-space tools. Starting with Oracle Database 11g Release 2 (11.2), Security Enhanced Linux is supported for Oracle Linux 4, RedHat Enterprise Linux 4, Oracle Linux 5, and Red Hat Enterprise Linux 5. Security Enhanced Linux is not supported for the Oracle EnterpriseManager 12c Oracle Management Service.

Mandatory access controls, for example Security Enhanced Linux, may be a part of your organizations information security program. If yourinformation security program requires mandatory access controls for the 12c Oracle Management Repository, a best practice is to configureSecurity Enhanced Linux during the last phase of the Enterprise Manager deployment.

To confirm the status of SELinux, as root type sestatus as shown in the next example.# sestatusSELinux status: disabled

The above example shows a host with SELinux disabled.

Security Enhanced Linux can be temporarily set to permissive by typing "echo 0 > /selinux/enforce", as root. Security Enhanced Linux can bere-enabled (enforcing) by typing "echo 1 > /selinux/enforce", as root.

Security Enhanced Linux can be permanently disabled by changing the "SELINUX=enforcing" entry to "SELINUX=disabled" in the "/etc/selinux/config" file. Security Enhanced Linux can be re-enabled by changing the "SELINUX=disabled" entry to "SELINUX=enforcing" in the "/etc/selinux/config" file. A re-boot is required after changing the "SELINUX= value to enable to new settings.

Configure the /etc/hosts FileOracle technology products, including Oracle Enterprise Manager, rely on a properly formatted /etc/hosts file which allows the host to bepingable, with long and short host names. The host name in the /etc/hosts file must be associated with the server's public IP address.

The next example shows the proper syntax from a /etc/hosts file. Note that the localhost entries are one one line, and the IP address with the longand short names are on the next line.

127.0.0.1 localhost.localdomain localhost192.168.4.8 servername.com servername

The next example shows an improperly formatted /etc/hosts file. Note that the long and short names are on the same line as the localhost entries.

127.0.0.1 servername.com servername localhost.localdomain localhost192.168.4.8 servername.com servername

Tip: The following IPv6 entries in Oracle Linux 5 & 6 /etc/hosts files should be removed to aviod "Bug 13652664 : AGENT DEPLOY FAILS WITHAGENT PORT PASSED BY USER IS BUSY" with Oracle Management Agent installations:::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

The /etc/hosts file can be edited by the root user bu typing vi /etc/hosts, as shown in the next example.

# vi127.0.0.1 localhost.localdomain localhost192.168.4.8 servername.com servername:wq!

Configure SSH and X11 ForwardingInstalling the Oracle Enterprise Manager 12c components using the Oracle Universal Installer (OUI) GUI requires local or remote access to theserver' console or a remote X Windows (X11) session. Please note that the only software requirements on the Linux Oracle Enterprise Managerhost for remote X Windows (X11) sessions is the xauth RPM package. The xauth RPM package handles the X11 forwarding authentication.X-windows and xhost are not required on the Linux Oracle Enterprise Manager host for remote X Windows (X11) sessions.

SSH and X11 forwarding enables the redirection of an X11 session from a remote Oracle Linux machine to a local desktop. For example, from alocal desktop, ssh to a remote Oracle Linux server using X11 forwarding and run the Oracle Universal Installer, i.e. by typing ./runInstaller. TheOracle Universal Installer will be displayed on the local desktop and the Oracle Enterprise Manager 12c components can be installed on theremote Oracle Linux server.

On the Oracle Linux server, enable X11 forwarding in the /etc/ssh/sshd_config by adding "ForwardX11 yes" to the file as shown in the nextexample.Change#X11Forwarding no



ToX11Forwarding yes

Once the "ForwardX11 yes" entry has been added to the /etc/ssh/sshd_config file, to enable X11 forwarding, as root, restart the ssh service by typing:# service sshd restartWith X11 forwarding enabled, the Oracle Universal Installer (OUI) GUI can be exported from the Oracle Linux server to your local desktop.

Tip: To aviod X11 challanges install the xauth and xorg-x11-apps RPMs on the Linux host. To check for the RPMs, as root type:# rpm -qa | grep -i xauth and rpm -qa | grep -i xorg-x11-appsTo install xauth and the xorg-x11-apps RPMs, as root type:# yum -y install xorg-x11-apps xauth.

To enable X11 forwarding from a Linux desktop, use the "-X" switch with ssh. For example, type "ssh -X oracle@" tocreate a ssh tunnel with X11 forwarding. Do not forget that -X enables X11 forwarding, and -x actually disables X11 forwarding. Also, using the sucommand within a SSH session with X11 forwarding breaks X11 authentication.

To test remote X Windows (X11), open a new ssh session with X11 forwarding enabled (ssh -X user@servername), and type xclock. The xclockapplication should open on your desktop. xclock is an X window client application that is included in the xorg-x11-apps RPM package. xclock isoften used to test remote X Windows (X11) sessions.

Tip: To troubleshoot ssh connections, use ssh verbose mode, i.e. ssh -v -v -X user@servername

If your using a Windows PC, a PC X Server like XMing is required to run an X Windows session, along with an ssh client like putty that supportsX11 forwarding.

If you get X11 forwarding request failed on channel 0 messages from an ssh connection, on the target Oracle Linux server edit the /etc/ssh/sshd_config file,and ensure that "X11Forwarding yes" is not commented, add "X11UseLocalhost no", and uncomment "AddressFamily any". Next, restart sshd by typing "service sshdrestart", and your X11 apps will successfully run.

Configure the ulimit /etc/security/limits.conf ValuesOne of the Oracle Enterprise Manager 12c OMS installation prerequisites is to increase the number of file descriptors to at least 4096. As root, edit the /etc/security/limits.conf fileand add the following two entries: soft nofile 4096 hard nofile 4096

As the installing user, i.e. oracle, confirm the new file limits by typing:$ ulimit -nand$ /bin/sh -c "ulimit -n"

The value should be greater than 4096.

Oracle Database 11g Enterprise Edition R2 (11.2.0.4.0) Installation PrerequisitesBefore starting the Oracle Database 11g R2 installation, it is necessary to meet several database, and operating system prerequisites, and to create the installation directories.

Create the Required Directories using the Optimal Flexible Architecture (OFA)Standard The Optimal Flexible Architecture (OFA) standard is a set of file naming recommendations for managing Oracle installations. The Optimal FlexibleArchitecture standard offers mount point, directory, and file-naming conventions that work with the Oracle Universal Installer. The OptimalFlexible Architecture includes where to install each part of each Oracle product including the storage of the applications and the data.

To create the directories for Oracle software installation using the Optimal Flexible Architecture standard, as root, type the following:# mkdir -p /u01/app/oracle/product/# chown -R oracle:oinstall /u01# chmod -R 775 /u01

Adjust the Shared Memory File System for the Database HostTo meet the Oracle Management Repository configuration requirements, the shared memory file system size should be increased to 4 GB.

Note: The shared memory file system size needs to be increased only on the Database host.

To check the current size of the shared memory file system, type df -k /dev/shm as shown in the next example.

# df -k /dev/shmFilesystem 1K-blocks Used Available Use% Mounted ontmpfs 3056052 0 3056052 0% /dev/shm

The above examples shows a 3 GB shared memory file system.

To set the shared memory file system size to 4 GB, as root, type the following commands.



# umount tmpfs# mount -t tmpfs shmfs -o size=4g /dev/shm

Next, add the following entry in /etc/fstab to automatically mount the 4 GB shared memory file system.tmpfs /dev/shm tmpfs size=4g 0 0

Oracle Database 11g Enterprise Edition R2 (11.2.0.4.0) InstallationThis section walks through the installation of Oracle Database 11g Release 2 (11.2.0.4.0) using the Oracle Universal Installer (OUI) on OracleLinux 5 or 6.

With the software downloaded and staged on the Oracle Linux host, as the installing user, i.e. oracle, run the runInstaller script by typing"./runInstaller" as shown in the next example.

# ssh -X oracle@$ cd /u01/app/stage/database$ ./runInstallerStarting Oracle Universal Installer...

Checking Temp space: must be greater than 120 MB. Actual 3967 MB PassedChecking swap space: must be greater than 150 MB. Actual 6189 MB PassedChecking monitor: must be configured to display at least 256 colors. Actual 16777216 PassedPreparing to launch Oracle Universal Installer from /tmp/OraInstall2013-11-30_04-53-29PM. Please wait ...

On the Configure Security Updates screen, to receive information from Oracle (optional), enter your email address and My Oracle Supportpassword and click the Next button, or uncheck the I wish to receive security updates via My Oracle Support checkbox and click the Nextbutton.Figure 20

On the Download Software Updates screen, select one of the following three software update options, then click Next to proceed:

Use My Oracle Support credentials for downloadUse pre-downloaded software updatesSkip software updates

For this example we selected the Skip software updates option and then Next to proceed. Figure 21



On the Select Install Option screen, select Create and configure a database. Click the Next button to proceed.Figure 22

On the System Class screen, select the Server Class option. Click the Next button to proceed.Figure 23



On the Grid Installation Options screen, select the Single instance database installation option. Click the Next button to proceed.Figure 24

On the Select Install Type screen, select the Tipical install option. Click the Next button to proceed.Figure 25



On the Typical Install Configuration screen, accept the defaults, enter a Administrative password. Click the Next button to proceed.Figure 26

On the Create Inventory screen, accept the defaults. Click the Next button to proceed.Figure 27



The Perform Prerequisite Checks screen shows if the minimum system requirements to perform the database installation are met.

Click Check Again, if you fixed the problems and you would like to verify the system requirements again.Click Fix & Check Again, if you want the installer to try to fix the problems and verify the system requirements again.Click Ignore All to ignore the problems and move forward with the database installation.

Note: If you get numerous i386 and i686 package failures, it is possible that you are installing an earlier version of 11g R2, i.e. 11.2.0.2.0. Downloadthe 11.2.0.4.0 code and start the installer again.

Click the Next button to proceed.Figure 28

On the Summary screen, click the Install button to start the database installation.Figure 29



The Database Configuration Assistant screen shows the progress of the database configuration.Figure 30

The second Database Configuration Assistant screen shows the database configurations. Click the OK button to close the DatabaseConfiguration Assistant screen.Figure 31



The Execute Configuration script screen appears and shows what scripts needs to be executed as the root user. As the root user, open aterminal and run both of the root.sh scripts. Next, click OK to close the Execute Configuration script screen.Figure 32

The Finish screen shows the Enterprise Manager Database Control URL. Click the Close button to close the installation programFigure 33



Next, after the Database Installation, add the following Oracle user environment settings in the installing user's .bash_profile file. For example, if the Database was installedusing the oracle user acount, add the following Oracle user environment settings in the /home/oracle/.bash_profile file. Edit the appropriate lines to meet the setting youselected during the Database install.

# Oracle SettingsTMP=/tmp; export TMPTMPDIR=$TMP; export TMPDIRORACLE_BASE=/u01/app/oracle/product; export ORACLE_BASEORACLE_HOME=$ORACLE_BASE/11.2.0/dbhome_1; export ORACLE_HOMEEMDROOT=$ORACLE_BASE/11.2.0/dbhome_1; export EMDROOTORACLE_SID=oracle; export ORACLE_SIDORACLE_UNQNAME=oracle; export ORACLE_UNQNAMEORACLE_TERM=xterm; export ORACLE_TERMPATH=/usr/sbin:$PATH; export PATHPATH=$ORACLE_HOME/bin:$PATH; export PATHLD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATHCLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH

if [ $USER = "oracle" ]; then if [ $SHELL = "/bin/ksh" ]; then ulimit -p 16384 ulimit -n 65536 else ulimit -u 16384 -n 65536 fifi

Next, as the oracle user drop Enterprise Manager Database Control by typing the following command. Substitute with thesys password and with the sysman password selected during the database installation. Change the bold Database SIDand Listener port number as per your Database install.

$ $ORACLE_HOME/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD -SYSMAN_PWD

STARTED EMCA at Jan 27, 2015 11:32:37 AMEM Configuration Assistant, Version 11.2.0.3.0 ProductionCopyright (c) 2003, 2011, Oracle. All rights reserved.

Enter the following information:Database SID: orclListener port number: 1521

----------------------------------------------------------------------WARNING : While repository is dropped the database will be put in quiesce mode.----------------------------------------------------------------------Do you wish to continue? [yes(Y)/no(N)]: YJan 27, 2015 11:32:47 AM oracle.sysman.emcp.EMConfig performINFO: This operation is being logged at /u01/app/oracle/cfgtoollogs/emca/emrepo/emca_2015_01_27_11_32_37.log.Jan 27, 2015 11:32:48 AM oracle.sysman.emcp.util.DBControlUtil stopOMSINFO: Stopping Database Control (this may take a while) ...



Jan 27, 2015 11:32:59 AM oracle.sysman.emcp.EMReposConfig invokeINFO: Dropping the EM repository (this may take a while) ...Jan 27, 2015 11:34:31 AM oracle.sysman.emcp.EMReposConfig invokeINFO: Repository successfully droppedEnterprise Manager configuration completed successfullyFINISHED EMCA at Jan 27, 2015 11:34:35 AM

Next, assess the database as sysdba and create a pfile from the spfile.

$ sqlplus / AS SYSDBASQL*Plus: Release 11.2.0.3.0 Production on Mon Apr 8 08:53:22 2013

Copyright (c) 1982, 2011, Oracle. All rights reserved.

Connected to:Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> create pfile from spfile;

File created.

SQL> quit

Next, create a directory for the redo log files, as shown in the next example.$ mkdir /u01/app/oracle/product/redo_logs/

Next, access the Database as sysdba and make either the Eval, Small, Medium, or Large Site initialization parameters, then restart the database.

The following tables show the minimum Oracle Management Repository Database settings for an Eval, Small, Medium and Large Site.

Table 6: Eval Configuration Minimum Database SettingsParameter Minimum Value

Processes 300

memory_target 700 MB

redo log file size 50 MB

shared_pool_size 450 MB

session_cached_cursors remove

Table 7: Small Site Minimum Database SettingsParameter Minimum Value

*memory_target of 3 GB can be used in place of sga_target and pga_aggregate_target

processes 300

pga_aggregate_target* 1024 MB

sga_target* 2 GB



db_securefile PERMITTED

Table 8: Medium Site Minimum Database SettingsParameter Minimum Value

*memory_target of 5.25 GB can be used in place of sga_target and pga_aggregate_target

processes 600


sga_target* 4 GB




Table 9: Large Site Minimum Database SettingsParameter Minimum Value

*memory_target of 7.5 GB can be used in place of sga_target and pga_aggregate_target

processes 1000


sga_target* 6 GB






The next example shows applying the Small Site Oracle Management Repository Database initialization parameters, including force logging, andadding the redo log files.

Note: Please consult with your DBA to confirm your redo log file settings. The below ALTER DATABASE ADD LOGFILE GROUP commands areonly an example that will create the necessary redo log file for the Oracle Enterprise Manager installer.

The SQL commands to be entered are listed below in BOLD ITALIC.

$ sqlplus / AS SYSDBASQL> ALTER SYSTEM SET processes=300 SCOPE=SPFILE;System altered.SQL> ALTER SYSTEM SET pga_aggregate_target=1024M SCOPE=SPFILE;System altered.SQL> ALTER SYSTEM SET sga_target=2G SCOPE=SPFILE;System altered.SQL> ALTER SYSTEM SET shared_pool_size=600M SCOPE=SPFILE;System altered.SQL> ALTER SYSTEM SET db_securefile=PERMITTED SCOPE=BOTH;System altered.SQL> ALTER DATABASE ADD LOGFILE ('/u01/app/oracle/product/redo_logs/log1c.rdo', '/u01/app/oracle/product/redo_logs/log2c.rdo', '/u01/app/oracle/product/redo_logs/log3c.rdo') SIZE 100M;System altered.

SHUTDOWN IMMEDIATE;SQL> CREATE SPFILE FROM PFILE;SQL> STARTUP;ORACLE instance started.

Total System Global Area 3206836224 bytesFixed Size 2217632 bytesVariable Size 1744832864 bytesDatabase Buffers 1442840576 bytesRedo Buffers 16945152 bytesDatabase mounted.Database opened.

SQL> quit

Automate the Oracle Database Startup and ShutdownThere are several steps to automate the database startup and shutdown process with Oracle Linux.

Once the database has been installed, a file called oratab is created in the /etc directory. The oratab file has a Y/N flag to specify if the databaseshould be re-started when the server boots.

As root, edit the /etc/oratab file and change N to Y, as shown below.

The default setting is N, as shown in the next example.orcl:/u01/app/oracle/product/11.2.0/dbhome_1:N

Change the N to Y, as shown in the next example.orcl:/u01/app/oracle/product/11.2.0/dbhome_1:Y

The next example shows an oratab file from the above database installation with the Y flag.# cat /etc/oratab#

# This file is used by ORACLE utilities. It is created by root.sh# and updated by the Database Configuration Assistant when creating# a database.

# A colon, ':', is used as the field terminator. A new line terminates# the entry. Lines beginning with a pound sign, '#', are comments.## Entries are of the form:# $ORACLE_SID:$ORACLE_HOME::## The first and second fields are the system identifier and home# directory of the database respectively. The third filed indicates# to the dbstart utility that the database should , "Y", or should not,# "N", be brought up at system boot time.## Multiple entries with the same $ORACLE_SID are not allowed.##orcl:/u01/app/oracle/product/11.2.0/dbhome_1:Y

Next, as root, using your favorite text editor, create a database startup and shutdown script named /etc/init.d/dbora. The dboar script calls the dbstartand dbshut routines. The next example show the /etc/init.d/dbora script.



Resource: http://docs.oracle.com/cd/E18676_01/doc/server.112/e10839/strt_stp.htm

#! /bin/sh -x## Change the value of ORACLE_HOME to specify the correct Oracle home# directory for your installation.

ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1## Change the value of ORACLE to the login name of the# oracle owner at your site.#ORACLE=oracle

PATH=${PATH}:$ORACLE_HOME/binHOST=`hostname`PLATFORM=`uname`export ORACLE_HOME PATH#if [ ! "$2" = "ORA_DB" ] ; then if [ "$PLATFORM" = "HP-UX" ] ; then remsh $HOST -l $ORACLE -n "$0 $1 ORA_DB" exit else rsh $HOST -l $ORACLE $0 $1 ORA_DB if [ "$PLATFORM" = "Linux" ] ; then touch /var/lock/subsys/dbora fi exit fifi#case $1 in'start') $ORACLE_HOME/bin/dbstart $ORACLE_HOME & ;;'stop') $ORACLE_HOME/bin/dbshut $ORACLE_HOME & ;;*) echo "usage: $0 {start|stop}" exit ;;esac#exit

Note: The above script can only stop Oracle Net listener for which a password has not been set. If the listener name is not the default name,LISTENER, then you must specify the listener name in the stop and start commands:$ORACLE_HOME/bin/lsnrctl {start|stop} listener_name

After the dbora script is created, as root, change the group membership and set the privileges, by typing:# chmod 750 /etc/init.d/dbora# chgrp dba /etc/init.d/dbora

Next, create symbolic links to the dbora script in the run-level directories:# ln -s /etc/init.d/dbora /etc/rc.d/rc0.d/K01dbora# ln -s /etc/init.d/dbora /etc/rc.d/rc3.d/S99dbora# ln -s /etc/init.d/dbora /etc/rc.d/rc5.d/S99dbora

Oracle Database 12c Release 1 Enterprise Edition (12.1.0.1.0) Installation PrerequisitesBefore starting the Oracle Database 12c Release 1 installation, it is necessary to meet several database, and operating system prerequisites, as well as to download and stage thesoftware.

Download and Stage the Database SoftwareDownload the Oracle Enterprise Manager 12c R4 software from OTN: http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

Next, as the installing user, create a directory to stage the software.$ mkdir -p /u01/stage/db12c

Copy the linuxamd64_12c_database_1of2.zip and linuxamd64_12c_database_2of2.zip files to the staging directory /u01/stage/db12c, then unzipeach file:$ unzip linuxamd64_12c_database_1of2.zip



$ unzip linuxamd64_12c_database_2of2.zip

You should now have a directory called database with the installation files.$ ll /u01/stage/db12c/

total 2419492drwxr-xr-x 1 oracle oinstall 110 Jun 10 2013 database-rw-r--r-- 1 oracle oinstall 1361028723 Jun 16 17:52 linuxamd64_12c_database_1of2.zip-rw-r--r-- 1 oracle oinstall 1116527103 Jun 16 17:53 linuxamd64_12c_database_2of2.zip

Create the Required Directories using the Optimal Flexible Architecture (OFA)Standard The Optimal Flexible Architecture (OFA) standard is a set of file naming recommendations for managing Oracle installations. The Optimal FlexibleArchitecture standard offers mount point, directory, and file-naming conventions that work with the Oracle Universal Installer. The OptimalFlexible Architecture includes where to install each part of each Oracle product including the storage of the applications and the data.

To create the directories for Oracle software installation using the Optimal Flexible Architecture standard, as root, type the following:# mkdir -p /u01/app/oracle/product/12.1.0/dbhome_1# chown -R oracle:oinstall /u01/*# chmod -R 775 /u01/*

Tip: /u01 should be owned by root user

Configure the ulimit, /etc/security/limits.conf and /etc/security/limits.d/oracle-rdbms-server-12cR1-preinstall.conf ValuesOne of the Oracle Enterprise Manager 12c installation prerequisites is to increase the number of file descriptors to at least 4096. As root, edit the/etc/security/limits.conf file and add the following two entries: soft nofile 4096 hard nofile 4096

If using oracle-rdbms-server-12cR1-preinstall the settings will be in the oracle-rdbms-server-12cR1-preinstall.conf file. As root, editthe /etc/security/limits.d/oracle-rdbms-server-12cR1-preinstall.conf file as shown in the next example.Changeoracle soft nofile 1024Tooracle soft nofile 4096

There is also a limit on the number of max user processes in the /etc/security/limits.d/90-nproc.conf file. As root, edit the /etc/security/limits.d/90-nproc.conf file and make the following changes.Change* soft nproc 1024To* - nproc 16384

Confirm the new limits by looking at output of ulimit -a:$ su - oracle$ ulimit -acore file size (blocks, -c) 0data seg size (kbytes, -d) unlimitedscheduling priority (-e) 0file size (blocks, -f) unlimitedpending signals (-i) 96073max locked memory (kbytes, -l) 64max memory size (kbytes, -m) unlimitedopen files (-n) 4096pipe size (512 bytes, -p) 8POSIX message queues (bytes, -q) 819200real-time priority (-r) 0stack size (kbytes, -s) 10240cpu time (seconds, -t) unlimitedmax user processes (-u) 16384virtual memory (kbytes, -v) unlimitedfile locks (-x) unlimited

As the Installing User, Setup ~/.bash_profileAdd the following Oracle variables in the installing user's .bash_profile file as a reference point for your 12c environment.

Add the following to the end of the installing user's ~/.bash_profile file.

Note: Confirm the variable setting for your enviroment. For example, the confirm the bold section above, i.e. paths, the SID, and the unqname.



# Oracle variablesTMP=/tmp; export TMPTMPDIR=$TMP; export TMPDIRORACLE_HOSTNAME=hostname.domain.com; export ORACLE_HOSTNAMEORACLE_BASE=/u01/app/oracle; export ORACLE_BASEORACLE_HOME=$ORACLE_BASE/product/12.1.0/dbhome_1; export ORACLE_HOMEAGENT_HOME=$ORACLE_BASE/product/agentr4/agent_inst; export AGENT_HOMEOMS_HOME=$ORACLE_BASE/product/MiddlewareR4/oms; export OMS_HOMEORACLE_INSTANCE=/u01/app/oracle/product/gc_inst/WebTierIH1; export ORACLE_INSTANCEORACLE_SID=MYSID; export ORACLE_SIDORACLE_UNQNAME=MYSID; export ORACLE_UNQNAMEPATH=/usr/sbin:$PATH; export PATHPATH=$ORACLE_HOME/bin:$PATH; export PATHLD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATHCLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH

Next, source the .bash_profile:$ source ~/.bash_profile

Oracle Database 12c Release 1 Enterprise Edition (12.1.0.1.0) InstallationTip: ensure you ssh in as the installing user, i.e. oracle, or the graphic installer may not work and give a prerequisite error for display export.

$ cd /u01/stage/db12c/database$ ./runInstallerStarting Oracle Universal Installer...

Checking Temp space: must be greater than 500 MB. Actual 12143 MB Passed

Checking swap space: must be greater than 150 MB. Actual 14335 MB PassedChecking monitor: must be configured to display at least 256 colors. Actual 16777216 PassedPreparing to launch Oracle Universal Installer from /tmp/OraInstall2014-06-23_11-54-13AM. Please wait ...$

Configure Security Updates screenFrom the Configure Security Updates screen, to receive security update information from Oracle (optional), enter your email address and MyOracle Support password and click the Next button, or uncheck the I wish to receive security updates via My Oracle Support checkbox andclick the Next button.Figure 34

Download Software Updates screenFrom the Download Software Updates screen, select one of the following three software update options, then click Next to proceed:

Use My Oracle Support credentials for downloadUse pre-downloaded software updatesSkip software updates

For this example we selected Skip software updates then Next to proceed.Figure 35



Select Installation Option screenFrom the Select Installation Option screen select Create and configure a database. Click the Next button to proceedFigure 36

System Class screenFrom the System Class screen select the Server Class option. Click the Next button to proceed.Figure 37



oracle enterprise manager 12c installation

Documents