Here are some of my notes on Installing 12c Cloud Control on a Linux x86_64 platform.
In a previous note I described the process of upgrading 10.2.0.5 Grid Control to 12c Cloud Control.
If you have installed 11g Grid Contro;l, then the process is quite similar. The real difference is the screen related to selecting Plug-ins which is something new in 12c. Plug-ins and Connectors are extensions to Grid Control to enable management of non-Oracle products and the complete ‘cloud’ stack which includes databases, middleware and even virtual servers.
We have plug-ins for Oracle like Oracle Database, Oracle Exadata, My Oracle Support, Oracle Fusion Middleware, Oracle Virtualisation and also a number of no-Oracle plug-ins like IBM DB2, Sybase etc
- gcc -4.1.1
- libstdc++ -4.1.1
In addition, install the 32-bit version as well as the 64-bit version of glibc-devel-2.5-49
•Admin Server HTTP SSL Port = 7101 – 7200
•Enterprise Manager Upload HTTP Port = 4889 – 4898
•Enterprise Manager Upload HTTP SSL Port = 1159, 4899 – 4908
•Enterprise Manager Central Console HTTP Port = 7788 – 7798
•Enterprise Manager Central Console HTTP SSL Port = 7799 – 7809
•Oracle Management Agent Port = 3872, 1830 – 1849
Repository Database requirements
10.2.0.5 database can be used as repository for cloud control
If you use Oracle Database 11g Release 2 (18.104.22.168), then ensure that you apply the patches for bugs 10014178 and 8799099
For fresh installs, database should not have SYSMAN schema. If Database Control exists in the dtaabase chosen for the OMS repository, then we need to use the emca -deconfig dbcontrol db -repos drop command to deconfigure Database Control first.
open_cursors needs to be 300 to 400
processes should be greater than 300
session_cached_cursors between 200 and 500
job_queue_interval needs to be at least 20
shared pool size minimum 600 MB
Redo log file sizes minimum 300 MB
UNDO tablespace has a minimum space of 200 MB
stop the Gather Statistics job
For 10g use :
For 11g use :
execute dbms_auto_task_admin.disable(‘auto optimizer stats collection’,null,null);
Use the Enterprise Manager Prerequisite Kit utility (emprereqkit)
The emprereqkit utlity is available in the 12c software under the directory location install/requisites/bin/emprereqkit. After installation also, it can be run if say we want to upgrade to the next higher version and now need to check if the repository meets the minimum requirements.
It will be located under the OMS_HOME at /install/requisites/bin
It is a command line utility which we can run to test if our repoitory database for the 12c OMS meets all the requirements before we start the installation.
An example of running this is shown here:
$ ./emprereqkit -executionType install -prerequisiteXMLLoc $ORACLE_HOME/install/requisites/list -dbHost oem-prod -dbPort 1521 -dbSid oem12c -dbUser SYS -dbPassword syspwd -dbRole sysdba -showPrereqs
Ensure the directory selected for the Middleware Home Location does not contain any files or subdirectories
If not already present, Oracle WebLogic Server 11g Release 1 (10.3.5) and JDK 1.6 v24 are installed in the Middleware home
A WebLogic domain called GCDomain is created