Cloud 12C

Install Oracle Enterprise Manager (OEM) Cloud Control 12c on
OEL 6.1
Oracle announced recently at OOW 2011 the release of the brand new re-
engineered OEM Cloud Control 12c (c stands for the cloud). This is the
first product from the 12c family of products intended for the cloud. At
present, as of the time of the writing of the article, OEM 12c is only
available for download for Linux x86 (32bit) and Linux x86-64 (64bit)
from OTN.
In the article you will have a look at how to prepare the OEL 6.1 and
subsequently install OEM 12c on OEL 6.1. OEM 12c requires a repository
database. In the article Oracle 11.2.0.3 database is used a repository. I
will provide pointers to MOS or Oracle documentation for supported OS and
repository database versions.
Select a supported OS and install supported Oracle database for

repository. MOS maintains a list of certified platforms and products for
a product. For OEM 12c you will be interested in
1. Certified OS for installation

2. Certified Oracle database for repository
3. Certified targets
Always check the certification matrix as it is updated as new supported
OS are added and new inter-operability database patches are added.
Oracle® Enterprise Manager Cloud Control Basic Installation Guide
12c Release 1 (12.1.0.1) also
contains a list of prerequisites for OEL and repository database. The
complete set of OEM 12c documentation is available here.
In the article the following software products will be used.
1. Oracle 11gR2 (11.2.0.3) for Linux (x86-64). Patch 10404530.

Download from MOS here.
2. Oracle Enterprise Linux OEL 6.1(x86-64). Download from here.
3. Oracle VM VirtualBox 4.1.4. Download from here.
4. Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1).
Download from here.
In the article I will reuse the OEL61 VM created here to install OEM
12c and will outline the steps to follow if you start from a new OEL 6.1
installation. Proceed for OS configuration and OEM 12c installation once
you are on supported OS and have a supported Oracle RDBMS database for an
OEM repository.
Installation of OEL 6.1 and Oracle 11.2.0.3 GI and RDBMS and creating RAC
database is covered here.
A complete prerequisite check list can be found here. In the article an

assumption is made that an Oracle RDBMS is created for a repository prior
to OEM 12c installation. The database in this article is RAC 11.2.0.3.
Configure OEL 6.1
1. Hardware Requirements
I increased the OEL61 RAM to 8GB and restarted. Create a VM or

choose a server accordingly sized.
2. Package, Kernel parameter and library requirements
I did a full OEL6.1 install and additionally added glibc-devel-

2.12-1.25.el6.i686.rpm as OUI was asking for glibc-devel-2.5-
49.i386.rpm.
Install the following packages or later from OEL media if you have
a fresh OEL 6.1 install.
For OMS
 make-3.81
 binutils-2.17.50.0.6
 gcc -4.1.1
 libaio-0.3.106
 glibc-common-2.3.4
 libstdc++ -4.1.1
 sysstat-5.0.5
 glibc-2.5.12
 glibc-devel-2.5-49
For agent
 make-3.81
 binutils-2.17.50.0.6
 gcc -4.1.1
 libstdc++ -4.1.1
The kernel parameters were already set for Oracle RAC 11.2.0.3
deployment and met the OEM 12c requirement for kernel.shmmax
parameter to a value less than 4 GB.
The /etc/sysctl.conf for Oracle GI and RAC RDBMS 11.2.0.3 is as

follows ( in red the OEM 12c requirements):
# Controls the maximum number of shared memory segments, in pages
kernel.shmall = 4294967296
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
fs.aio-max-nr = 1048576
fs.file-max = 6815744
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048586
net.ipv4.conf.eth2.rp_filter = 2
kernel.shmmax = 2074277888
fs.suid_dumpable = 1
# Controls the maximum number of shared memory segments, in pages
[root@oel61 stage]#
Value kernel.shmmax = 2074277888 is within the OEM 12c requirements.
1. File descriptor requirements
Modify as root /etc/security/limits.conf to make sure that you set

a minimum of 4056 max open files. This is the content for Oracle
RAC 11.2.0.3. Only the values in red a required for OEM 12c.
cat /etc/security/limits.conf
<………..>
oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 4096
oracle hard nofile 65536
grid soft nproc 2047
grid hard nproc 16384
grid soft nofile 4096

grid hard nofile 65536
# End of file
OMS will complain and display a warning if descriptors are not

properly set. See the Annex 1.
2. Create users and groups
Since I am installing it on a RAC node I have oracle user already

created. OEM 12c can be installed using that oracle user. Assuming
that Oracle RDBMS is created for OEM 12c repository you can install
OEM as Oracle owner or any user that is part of oinstall and dba
group. As part of GI and RAC installation I did.
groupadd -g 1000 oinstall
groupadd -g 1020 asmadmin
groupadd -g 1021 asmdba
groupadd -g 1031 dba
groupadd -g 1022 asmoper
groupadd -g 1023 oper
useradd -u 1100 -g oinstall -G asmadmin,asmdba,dba,asmoper grid
useradd -u 1101 -g oinstall -G dba,asmdba,oper oracle
For OEM12c you can create the following groups and users.
groupadd -g 1000 oinstall
groupadd -g 1031 dba
useradd -u 1101 -g oinstall -G dba oracle
3. Make sure that SELINUX and firewall are disabled
chkconfig iptables off
# End of file
[root@oel61 stage]# cat /etc/selinux/config
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing – SELinux security policy is enforced.
# permissive – SELinux prints warnings instead of enforcing.
# disabled – SELinux is fully disabled.
SELINUX=disabled
# SELINUXTYPE= type of policy in use. Possible values are:
# targeted – Only targeted network daemons are protected.
# strict – Full SELinux protection.
SELINUXTYPE=targeted
[root@oel61 stage]#
4. Existing database version requirement See MOS or Oracle OEM

12c documentations.
If you are on 11.2.0.2 or 11.2.0.3 Oracle database, then

no interoperability patching is required.
If you use Oracle Database 11g Release 2 (11.2.0.1), then ensure

that you apply the patches for bugs 10014178 and 8799099.
If you use Oracle Database 11g Release 1 (11.1.0.7), then ensure

that you apply Patch Set Update 2 and the patches for bugs 8644757
and 7525072.
5. Umask value requirement
Make sure that the bash profiles for the oracle and grid users
contain umask 022.
6. Make sure that you use unique host names and static IP addresses. Do
not use Virtual IP or Virtual hostnames or SCANs.
7. Make sure that a physical host name is used and is fully resolvable
Make sure that all nslookup queries resolve to the same name and
associated IP address. For example on node oel61 you should have:
[root@oel61 stage]# nslookup oel61
Server: 192.168.2.11
Address: 192.168.2.11#53
Name: oel61.gj.com
Address: 192.168.2.11
[root@oel61 stage]# nslookup oel61.gj.com
Server: 192.168.2.11
Address: 192.168.2.11#53
Name: oel61.gj.com
Address: 192.168.2.11
[root@oel61 stage]# nslookup 192.168.2.11
Server: 192.168.2.11
Address: 192.168.2.11#53
11.2.168.192.in-addr.arpa name = oel61.gj.com.
[root@oel61 stage]#
8. Make sure that there is no existing OEM Database Control or Grid

Control or Cloud control repository.
Remove an existing OEM DC repository using the following command.
emca -deconfig dbcontrol db -repos drop -cluster -SYS_PWD sys1 -

SYSMAN_PWD sys1
See the Annex 1 for details
Remove anexisting OEM GC or OEM CC repository of a failed

installation using the following command.
/u01/app/oracle/product/11.2.0/em12c/oms/sysman/admin/emdrep/bin/RepManager oel
-cluster 1521 RMANREP1 -action dropall -dbUser sys -dbPassword sys1
9. Create a directory /u01/app/oracle/product/11.2.0/em12c for OEM12c

installation.
drwxr-x—. 16 oracle oinstall 4096 Oct 8 22:17 em12c
10. Unzip the OEM12c binaries in a stage directory.

11. For OEM12c installation modify the tnsnames.ora entry for the RMANREP
service or whatever name you will use to specify the local physical
host (RAC only). Added the red lines as per OUI suggestion.
RMANREP =
(DESCRIPTION =
(LOAD_BALANCE = ON)
(ADDRESS = (PROTOCOL = TCP)(HOST = oel-cluster)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = oel61)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = RMANREP)
12. Make sure that the Repository database is properly configured.
alter system set job_queue_processes=20 scope=both sid=’*’;
alter system set session_cached_cursors=500 scope=spfile sid=’*’;
alter system set processes=500 scope=spfile sid=’*’;
alter system set shared_pool_size=600M scope=spfile sid=’*’;

alter system set sga_target=2G scope=spfile sid=’*’;
alter system set pga_aggregate_target=1G scope=spfile sid=’*’;
After setting the init parameters in spfile bounce the

instance.
13. It is recommended to set the redo log files size to at least 300MB and
to configure at least 3 redo log groups.
14. Do not use a shared file system for Oracle Inventory.
Install OEM 21c
Run the OUI from the staging area by issuing ./runInstaller command.
Deselect the option for receiving security updates and press Next to
continue.
Select Skip and press Next button to continue.

Review the prerequisite checks. The warning is due to missing glibc-
devel-2.5-49.i386.rpm. Instead glibc-devel-2.12-1.25.el6.i686.rpm is
installed. Press Next to continue if this is the only problem.
Specify the installation location for Middleware home as indicated from
Configure OEL 6.1 in step 11. Press Next button to continue.
Specify the password and database connection details. Press Next to
continue.
This is already done in Configure OEL 6.1 step 13. Test the connection
and press OK.
Confirm that test is successful.
Press Yes.
Will leave as it is.
Review the summary of the installation.
Wait until installation completes.
At the end you are prompted to run scripts as root.
Run the scripts as root.
[root@oel61 bin]# cd /u01/app/oracle/product/11.2.0/em12c/oms
[root@oel61 oms]# ls *.sh
allroot.sh root.sh
[root@oel61 oms]# pwd
/u01/app/oracle/product/11.2.0/em12c/oms
[root@oel61 oms]# ./allroot.sh
Starting to execute allroot.sh ………
Starting to execute /u01/app/oracle/product/11.2.0/em12c/oms/root.sh ……

Running Oracle 11g root.sh script…
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/11.2.0/em12c/oms
Enter the full pathname of the local bin directory: [/usr/local/bin]:
The file “dbhome” already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
The file “oraenv” already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
The file “coraenv” already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
/etc exist
Creating /etc/oragchomelist file…
/u01/app/oracle/product/11.2.0/em12c/oms
Finished execution of /u01/app/oracle/product/11.2.0/em12c/oms/root.sh ……
Starting to execute /u01/app/oracle/product/11.2.0/em12c/agent/core/12.1.0.1.0/root.sh
……
Finished product-specific root actions.
/etc exist
Finished execution of
/u01/app/oracle/product/11.2.0/em12c/agent/core/12.1.0.1.0/root.sh ……
[root@oel61 oms]#
Press Close.
Prepare start and stop scripts.
[oracle@oel61 ~]$ cat stopOMS.sh
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
export OMS_HOME=/u01/app/oracle/product/11.2.0/em12c/oms
export AGENT_HOME=/u01/app/oracle/product/11.2.0/em12c/agent/core/12.1.0.1.0
# Start OMS & agent
$OMS_HOME/bin/emctl stop oms -all
$AGENT_HOME/bin/emctl stop agent
[oracle@oel61 ~]$
[oracle@oel61 ~]$ cat startOMS.sh
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
export OMS_HOME=/u01/app/oracle/product/11.2.0/em12c/oms
export AGENT_HOME=/u01/app/oracle/product/11.2.0/em12c/agent/core/12.1.0.1.0
# Start OMS & agent
$OMS_HOME/bin/emctl start oms
$AGENT_HOME/bin/emctl start agent
[oracle@oel61 ~]$
Verify the start and stop scripts. Note that file descriptors need to
modified as per Configure OEL 6.1 step 3.
[oracle@oel61 ~]$ ./startOMS.sh
Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
Starting WebTier…
WebTier Successfully Started
Starting Oracle Management Server…
Oracle Management Server Successfully Started
Oracle Management Server is Up
WARNING: Limit of open file descriptors is found to be 1024.
The OMS has been started but it may run out of descriptors under heavy usage.
For proper functioning of OMS, please set “ulimit -n” to be at least 4096.
Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
Starting agent …………………………………………………………………………………………………………… started but not ready.
[oracle@oel61 ~]$
[oracle@oel61 bin]$ ./emctl status agent
—————————————————————
Agent Version : 12.1.0.1.0
OMS Version : 12.1.0.1.0
Protocol Version : 12.1.0.1.0
Agent Home : /u01/app/oracle/product/11.2.0/em12c/agent/agent_inst
Agent Binaries : /u01/app/oracle/product/11.2.0/em12c/agent/core/12.1.0.1.0
Agent Process ID : 19074
Parent Process ID : 13957
Agent URL : https://oel61.gj.com:3872/emd/main/
Repository URL : https://oel61.gj.com:4904/empbs/upload
Started at : 2011-10-09 01:23:25
Started by user : oracle
Last Reload : (none)
Last successful upload : 2011-10-09 01:26:53
Last attempted upload : 2011-10-09 01:26:56

Total Megabytes of XML files uploaded so far : 0.24
Number of XML files pending upload : 6
Size of XML files pending upload(MB) : 0.15
Available disk space on upload filesystem : 15.18%
Collection Status : Collections enabled
Last attempted heartbeat to OMS : 2011-10-09 01:26:29
Last successful heartbeat to OMS : 2011-10-09 01:26:29
—————————————————————
Agent is Running and Ready
[oracle@oel61 bin]$
[oracle@oel61 bin]$ ./emctl reload agent
—————————————————————
EMD reload complete
Set sudoers access for oracle and grid in /etc/sudoers
oracle ALL=(ALL) ALL
grid ALL=(ALL) ALL
Test the installation
Access from the browser OEM CC URL https://oel61.gj.com:7803/em
Enter sysman and the password that you specified during OEM 12c
installation with OUI.
Acknowledge the license agreement.
Drill down to Enterprise Summary.
Go to the database RMANREP used for OEM CC 12c repository.
Look at Database systems.
Look at the cluster.
Access from the browser Admin Server URL
at https://oel61.gj.com:7103/console
This concludes the OEM 12c Cloud control installation. You looked at
OEL 6.1 configuration in order to meet the prerequisites for OEM CC
12c installation. You installed OEM CC 12c interactively using OUI.
Annex 1
[oracle@oel61 db_1]$ emca -deconfig dbcontrol db -repos drop -cluster -SYS_PWD sys1 -
SYSMAN_PWD sys1
STARTED EMCA at Oct 5, 2011 6:41:13 PM
EM Configuration Assistant, Version 11.2.0.3.0 Production

Copyright (c) 2003, 2011, Oracle. All rights reserved.
Enter the following information:
Database unique name: RMANREP
Service name: RMANREP
Listener port number: 1521
Listener ORACLE_HOME [ /u01/app/11.2.0/grid ]:
———————————————————————-
WARNING : While repository is dropped the database will be put in quiesce mode.
———————————————————————-
Do you wish to continue? [yes(Y)/no(N)]: Y
Oct 5, 2011 6:41:40 PM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at
/u01/app/oracle/cfgtoollogs/emca/RMANREP/emca_2011_10_05_18_41_11.log.
Oct 5, 2011 6:41:46 PM oracle.sysman.emcp.util.GeneralUtil initSQLEngineRemotely
WARNING: Error during db connection : ORA-01017: invalid username/password; logon
denied
Oct 5, 2011 6:41:53 PM oracle.sysman.emcp.util.GeneralUtil initSQLEngineRemotely
WARNING: ORA-01017: invalid username/password; logon denied
Oct 5, 2011 6:41:53 PM oracle.sysman.emcp.ParamsManager checkListenerStatusForDBControl
WARNING: Error initializing SQL connection. SQL operations cannot be performed
Oct 5, 2011 6:41:53 PM oracle.sysman.emcp.EMDBPreConfig performDeconfiguration
WARNING: EM is not configured for this database. No EM-specific actions can
be performed. Some of the possible reasons may be:
1) EM is configured with different hostname then physical host. Set environment
variable ORACLE_HOSTNAME= and re-run EMCA script

2) ORACLE_HOSTNAME is set. Unset it and re-run EMCA script
Oct 5, 2011 6:41:53 PM oracle.sysman.emcp.EMReposConfig invoke
INFO: Dropping the EM repository (this may take a while) …
Oct 5, 2011 6:48:49 PM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully dropped
Enterprise Manager configuration completed successfully
FINISHED EMCA at Oct 5, 2011 6:48:49 PM
[oracle@oel61 db_1]$
[oracle@oel61 bin]$ ./RepManager oel-cluster 1521 RMANREP1 -action dropall -dbUser sys -
dbPassword sys1 -dbRole MGMT_USER -reposName sysman -reposPassword tihomir1974 -
mwHome /u01/app/oracle/product/11.2.0/em12c -
mwOraHome /u01/app/oracle/product/11.2.0/em12c/oms -
oracleHome /u01/app/oracle/product/11.2.0/em12c/oms
processing arguments
compiling arguments for validation
Enter password for: sys
done checking required user credentials…
done creating arguments…
creating logger..
Connection exception in action logger path calculated:
/u01/app/oracle/product/11.2.0/em12c/oms/sysman/log/schemamanager/
action logger path calculated:
action logger path calculated finally:
no action logger file name from previous session

action logger filename after search: emschema.log
action logger filename finally: emschema.log
filename: /u01/app/oracle/product/11.2.0/em12c/oms/sysman/log/schemamanager/emschema.log
newly created:
/u01/app/oracle/product/11.2.0/em12c/oms/sysman/log/schemamanager/emschema.log
Driver: oracle.jdbc.driver.OracleDriver
jdbcUrl = jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(Host=oel-
cluster)(Port=1521)))(CONNECT_DATA=(SID=RMANREP1)))
action to perform is: drop
action is non-transx – RCU based action
logger null: check if repos user exists..
logger null: found connection for DB user
logger null: query DB for repos user existence check
logger null: REPOS_CONN is null in check repos user… creating new one
logger null: connection is found null
Error found: Validation Failure for Action: [DROP]. The reason for failure was: [null repos-
connection found]
Dropping MDS schema…
Enter sys user password : stty: standard input: Invalid argument
stty: standard input: Invalid argument
Verify : stty: standard input: Invalid argument

Common components home from environment is
/u01/app/oracle/product/11.2.0/em12c/oracle_common
Processing command line ….
Repository Creation Utility – Checking Prerequisites
Checking Global Prerequisites
Checking Component Prerequisites
Repository Creation Utility – Drop
Repository Drop in progress.
Percent Complete: 9
Percent Complete: 9
Percent Complete: 46
Repository Creation Utility: Drop – Completion Summary
Database details:
Connect Descriptor : (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(Host=oel-
Connected As : sys
Prefix for (prefixable) Schema Owners : SYSMAN
RCU Logfile : /u01/app/oracle/product/11.2.0/em12c/oms/emmds.log
Component schemas dropped:
Component Status Logfile
Metadata Services Success /u01/app/oracle/product/11.2.0/em12c/oms/mds.log

Repository Creation Utility – Drop : Operation Completed
Dropping OPSS schema…
Database details:
Connected As : sys
RCU Logfile :
/u01/app/oracle/product/11.2.0/em12c/oms/cfgtoollogs/cfgfw/emsecrepmgr.log

Oracle Platform Security
Services Success /u01/app/oracle/product/11.2.0/em12c/oms/cfgtoollogs/cfgfw/opss.l
og
Successfully dropped schema
Dropping APM schema…
Percent Complete: 9
Percent Complete: 9
Database details:
Connected As : sys
RCU Logfile :
/u01/app/oracle/product/11.2.0/em12c/oms/cfgtoollogs/cfgfw/emsecrepmgr.log
Authorization Policy
Manager Success /u01/app/oracle/product/11.2.0/em12c/oms/cfgtoollogs/cfgfw/apm.log
Successfully dropped schema
Dropping BIP schema…
RCU-6013:Specified prefix does not exist. Existing prefixes are: None
RCU-6091:Component name/schema prefix validation failed.
[oracle@oel61 bin]$
[oracle@oel61 bin]$ ./RepManager oel-cluster 1521 RMANREP1 -action dropall -dbUser sys -
dbPassword sys1
processing arguments
compiling arguments for validation
Enter password for: sys

done checking required user credentials…
done creating arguments…
creating logger..
Connection exception in action logger path calculated:
action logger path calculated:
action logger path calculated finally:
no action logger file name from previous session
action logger filename after search: emschema.log
action logger filename finally: emschema.log
filename: /u01/app/oracle/product/11.2.0/em12c/oms/sysman/log/schemamanager/emschema.log
newly created:
/u01/app/oracle/product/11.2.0/em12c/oms/sysman/log/schemamanager/emschema.log
Driver: oracle.jdbc.driver.OracleDriver
action to perform is: drop
action is non-transx – RCU based action
logger null: check if repos user exists..
logger null: found connection for DB user
logger null: query DB for repos user existence check
logger null: REPOS_CONN is null in check repos user… creating new one
logger null: connection is found null
Error found: Validation Failure for Action: [DROP]. The reason for failure was: [null repos-
connection found]
Dropping MDS schema…
Dropping OPSS schema…

Component is already dropped
Dropping APM schema…
Component is already dropped
Dropping BIP schema…
[oracle@oel61 bin]$
Share this:

Cloud 12C

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Cloud 12C

Hochgeladen von

Copyright:

Verfügbare Formate

Install Oracle Enterprise Manager (OEM) Cloud Control 12c on

Select a supported OS and install supported Oracle database for

1. Certified OS for installation

In the article the following software products will be used.

1. Oracle 11gR2 (11.2.0.3) for Linux (x86-64). Patch 10404530.

A complete prerequisite check list can be found here. In the article an

Configure OEL 6.1

I increased the OEL61 RAM to 8GB and restarted. Create a VM or

2. Package, Kernel parameter and library requirements

I did a full OEL6.1 install and additionally added glibc-devel-

The /etc/sysctl.conf for Oracle GI and RAC RDBMS 11.2.0.3 is as

# Controls the maximum number of shared memory segments, in pages

kernel.sem = 250 32000 100 128

net.ipv4.ip_local_port_range = 9000 65500

# Controls the maximum number of shared memory segments, in pages

Value kernel.shmmax = 2074277888 is within the OEM 12c requirements.

1. File descriptor requirements

Modify as root /etc/security/limits.conf to make sure that you set

oracle soft nproc 2047

oracle hard nproc 16384

oracle soft nofile 4096

oracle hard nofile 65536

grid soft nproc 2047

grid hard nproc 16384

grid soft nofile 4096

OMS will complain and display a warning if descriptors are not

2. Create users and groups

Since I am installing it on a RAC node I have oracle user already

groupadd -g 1000 oinstall

groupadd -g 1020 asmadmin

groupadd -g 1021 asmdba

groupadd -g 1031 dba

groupadd -g 1022 asmoper

groupadd -g 1023 oper

useradd -u 1100 -g oinstall -G asmadmin,asmdba,dba,asmoper grid

useradd -u 1101 -g oinstall -G dba,asmdba,oper oracle

groupadd -g 1000 oinstall

groupadd -g 1031 dba

useradd -u 1101 -g oinstall -G dba oracle

3. Make sure that SELINUX and firewall are disabled

chkconfig iptables off

# This file controls the state of SELinux on the system.

# SELINUX= can take one of these three values:

# enforcing – SELinux security policy is enforced.

# permissive – SELinux prints warnings instead of enforcing.

# disabled – SELinux is fully disabled.

# SELINUXTYPE= type of policy in use. Possible values are:

# targeted – Only targeted network daemons are protected.

# strict – Full SELinux protection.

4. Existing database version requirement See MOS or Oracle OEM

If you are on 11.2.0.2 or 11.2.0.3 Oracle database, then

If you use Oracle Database 11g Release 2 (11.2.0.1), then ensure

If you use Oracle Database 11g Release 1 (11.1.0.7), then ensure

5. Umask value requirement

[root@oel61 stage]# nslookup oel61

[root@oel61 stage]# nslookup oel61.gj.com

[root@oel61 stage]# nslookup 192.168.2.11

11.2.168.192.in-addr.arpa name = oel61.gj.com.

8. Make sure that there is no existing OEM Database Control or Grid

Remove an existing OEM DC repository using the following command.

emca -deconfig dbcontrol db -repos drop -cluster -SYS_PWD sys1 -

See the Annex 1 for details

Remove anexisting OEM GC or OEM CC repository of a failed