facebook twitter youtube facebook facebook facebook

E-Mail : info@askmlabs.com

Phone : +1.215.353.8306

Latest Post

Cloud Control OEM 12c Installation

Written By askMLabs on Saturday, April 28, 2012 | 6:30 PM

OEM 12C CLOUD CONTROL INSTALLATION
  1. Software
  2. OS installation
  3. Database Installation
  4. Oem 12c Prerequisites
    1. Hardware Requirements
    2. Operating System Requirements
    3. Package Requirements
    4. Kernel Parameter Requirements
    5. Library Requirements
    6. Operating System Groups and Users Requirements
    7. Unique Host Name and Static IP Address Requirements
    8. Temporary Directory Space Requirements
    9. Central Inventory Requirements
    10. UMASK Value Requirements
    11. File Descriptor Requirements
    12. Existing Database Version Requirements
    13. Host File Requirements
    14. Port Requirements
    15. Internet Connection Requirements
  5. 5.Oem 12c Installation Procedure
  6. 6.Verification Checks
  7. 7.Starting and Stopping oem 12c Services


 1. Software
The required software for the oem 12c cloud control are :
  • Oracle Linux 6.1 (x86_64)  Download
  • Oracle Database 11gR2 (x86_64)  Download
  • Enterprise Manager Cloud Control 12c (12.1.0.1) (x86_64) with BP1 patch Download
2. OS installation :
Oracle Linux 6.1 (x86_64) installation :

3. Database Installation :
Oracle Database 11gR2 installation :
Below links help to install database
4. Oem 12c Prerequisites :
4.1. Hardware Requirements :
CPU, RAM, Heap Size, and Hard Disk Space requirements vary depending on the type of installation we are choosing. Please review the here to know the exact hardware requirements.

4.2. Operating System Requirements :
Ensure that you install Enterprise Manger Cloud Control only on certified operating system as mentioned in the Enterprise Manager Certification Matrix.

4.3. Package Requirements :
make-3.81binutils-2.17.50.0.6gcc -4.1.1libaio-0.3.106glibc-common-2.3.4libstdc++ -4.1.1setarch-1.6sysstat-5.0.5rng-utils-2.0libXtst-1.0.1-3.1(x86_64)xorg-x11-utils (This package is required only for GUI-based interactive installation, and not for silent installation)

In addition, install the 32-bit version as well as the 64-bit version of glibc-devel-2.5-49 to avoid any linking errors while installing the OMS. The installer checks for this package, so if this package is not installed, the installer displays an error.

4.4 Kernel Parameter Requirements:
For installing an OMS or a Management Agent on Unix operating systems (32-bit or 64-bit), set the kernel.shmmax parameter to a value 1 byte less than 4 GB or 4294967295.

To verify the value assigned to kernel.shmmax parameter, run the following command:
cat /proc/sys/kernel/shmmax
 To set the value for kernel.shmmax parameter, run the following command:
sysctl -w kernel.shmmax=<new value>

4.5.       Library Requirements :
Install glibc-2.5.12 package

4.6 Operating System Groups and Users Requirements:
# /usr/sbin/groupadd oinstall# /usr/sbin/useradd -g oinstall oracle# passwd oracle
4.7. Unique Host Name and Static IP Address Requirements :
Ensure that you check the network configuration to verify that the host on which you are installing resolves to a unique host name and a static IP address that is visible to other hosts in the network.
You must use a static IP address. If you use a dynamic IP address, the installation might fail.
Ensure that the host name specified in /etc/hosts file is unique, and that it maps to the correct IP address. Following is the recommended format of the /etc/hosts file:
<ip address> <fully_qualified_host_name> <short_host_name>

If the DNS server is configured, then it should resolve the host name for the OMS machine correctly. For example, all these command must return the same output:
nslookup host1nslookup host1.foo.comnslookup 141.81.5.71
4.8. Temporary Directory Space Requirements :
Ensure that you allocate 400 MB of space for a temporary directory where the executables can be copied.

4.9. Central Inventory Requirements :
Ensure that you allocate 100 MB of space for the central inventory directory.
 Also ensure that the central inventory directory is not on a shared file system. If it is already on a shared file system, then switch over to a non-shared file system by following the instructions outlined in My Oracle Support note 1092645.1.
To determine whether the Oracle Inventory group exists, enter the following command:
     $ more /etc/oraInst.loc     If the oraInst.loc file exists, then the output from this command looks like:     inventory_loc=/u01/app/oracle/oraInventory     inst_group=oinstall
4.10.UMASK Value Requirements:
Ensure that you set the default file mode creation mask (umask) to 022 in the shell startup file.

4.11.File Descriptor Requirements :
If the current value is less than 4096, then as root user, update the /etc/security/limits.conf file as shown below:
         <UID> soft nofile 4096         <UID> hard nofile 4096
4.12. Existing Database Version Requirements :
Ensure that the database is patched with all the Patch Set Updates (PSU) or Critical Patch Updates (CPU) released for that release. Also ensure that you apply the patches.
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.
The database can also have the Automatic Memory Management (AMM) feature enabled.

4.13. Host File Requirements :
Ensure that the host name specified in the /etc/hosts file is unique, and ensure that it maps to the correct IP address of that host. Otherwise, the installation can fail on the product-specific prerequisite check page.
The following is the recommended format of the /etc/hosts file:
<ip> <fully_qualified_host_name> <short_host_name>

4.14. Port Requirements :
Ensure that the ports you assign (within the given range) to the following components are free and available:

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

To verify if a port is free, run the following command:
      On Unix:
      netstat -anp | grep <port no>

4.15. Internet Connection Requirements :
Oracle recommends that the host from where you are running the installer have a connection to the Internet so that the configuration information can be automatically collected and uploaded to My Oracle Support.

5. Oem 12c Installation Procedure :




6.Verification Checks : 
Access the following URL with sysman user and navigate to different pages to verify everything looks good.
https://<hostname with FQDN>:7803/em

7. Starting and Stopping oem 12c services : 
Use the following commands to start all components :
$ export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
$ export OMS_HOME=/u01/app/oracle/Middleware/oms
$ export AGENT_HOME=/u01/app/oracle/Middleware/agent/core/12.1.0.1.0
# Start everything
$ $ORACLE_HOME/bin/sqlplus '/as sysdba'
SQL> startup
$lsnrctl start listener
$ $OMS_HOME/bin/emctl start oms
$ $AGENT_HOME/bin/emctl start agent
Use the following commands to stop all components :
$ export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
$ export OMS_HOME=/u01/app/oracle/Middleware/oms
$ export AGENT_HOME=/u01/app/oracle/Middleware/agent/core/12.1.0.1.0
# Stop everything
$  $OMS_HOME/bin/emctl stop oms -all
$  $AGENT_HOME/bin/emctl stop agent
$ $ORACLE_HOME/bin/sqlplus '/as sysdba'
SQL> shut immediate
$ $lsnrctl stop listener

 Hope it helps
SRI

 
Support :
Copyright © 2013. askMLabs - All Rights Reserved
Proudly powered by Blogger