Friday, July 15, 2016

Install Oracle Enterprise Manager 13c Cloud control

6:38 AM Posted by Dilli Raj Maharjan No comments

OEM(Oracle Enterprise Manager) is pictorial representation of system, its status, downtime impact with lot of features to enhance the usability of Database. OEM 13c maximize support integration for Oracle Engineered Machine Exadata. OEM makes daily jobs easier and faster.



Few Features are listed below: 

  1. Compliance framework for OS, Database and Middleware.
  2. SLA Metering.
  3. Nerve center of IT operations among thousands of enterprises.
  4. Tracks unplanned and planned downtime windows. 
  5. Has monitoring capabilities with Always On features. Which can keep on monitoring in the case of OEM is down itself.
  6. Notification blackouts.
  7. Hardware and software stack management. It helps drill down into the infrastructure problems easily. Ref: https://www.youtube.com/watch?v=Olxq5MMvU0s
  8. The patching application offers the facility to run the pre-flight checks and monitor the logs from a single place (imagine having to manually monitor the patch execution logs for grid infrastructure, operating system, storage for all the compute and storage cells in a rack).
  9. Integration of Exacheck into the Compliance framework of Enterprise Manager that generate automated notifications and reports for any violation in their Exadata configurations.
  10. Engineered Systems patching.
  11. Continuous data refresh between production and test databases.

Installation Type:
Simple Installation
Advanced Installation


Supported Management Agents for Oracle Management Service 13c

  1. Oracle Management Agent 12c Release 3 (12.1.0.3)
  2. Oracle Management Agent 12c Release 4 (12.1.0.4)
  3. Oracle Management Agent 12c Release 5 (12.1.0.5)
  4. Oracle Management Agent 13c

Restrictions:

  1. Do not install on a symlink. Installing in such a location may impact life cycle operations such as patching and scaling out. Also, it will impact the functioning of your additional OMS.
  2. You must not set the ORACLE_HOME and ORACLE_SID environment variables. You must ensure that the Oracle directories do NOT appear in the PATH.
  3. The Enterprise Manager Cloud Control Installation Wizard installs Java Development Kit (JDK) 1.7.0_80 and Oracle WebLogic Server 12c Release 1 (12.1.3.0) by default. A preinstalled JDK or Oracle WebLogic Server is not supported from 13c Release 1 onwards.
  4. You must ensure that the Oracle WebLogic Server 12c Release 1 (12.1.3.0) installed by the Enterprise Manager Cloud Control Installation Wizard is dedicated for Enterprise Manager Cloud Control. You must not have any other Oracle Fusion Middleware product installed in that Middleware home.
  5. Enterprise Manager Cloud Control cannot coexist with any Oracle Fusion Middleware product in the same Middleware home because the ORACLE_COMMON property is used by both the products.
  6. As a prerequisite, you must have an existing Oracle Database to configure the Management Repository.
  7. If you install the OMS and the Oracle Database, which houses the Management Repository, on the same host, then when you reboot the host, the OMS and the Management Agent installed with it will not automatically start up. You will have to manually start them.
  8. You can optionally use the database templates offered by Oracle to create a database instance with a preconfigured Management Repository.
  9. In addition to the mandatory plug-ins, you can optionally install other plug-ins available in the software kit (DVD, downloaded software). The installer offers a screen where you can select the optional plug-ins and install them. However, if you want to install some plug-ins that are not available in the software kit (DVD, downloaded software), then refer to Section 5.5.1
  10. If you are installing on an NFS-mounted drive and creating the OMS instance base directory (gc_inst) on that NFS-mounted drive, then after you install, move the lock files from the NFS-mounted drive to a local file system location. Modify the lock file location in the httpd.conf file to map to a location on a local file system.

Prerequisites for Installing an Enterprise Manager System


Hardware Requirements


ConfigurationSmallMediumLarge
CPU4612
RAM10GB12GB24GB
HDD24GB24GB24GB

Operating System Requirements

  1. Linux x86_64 SELS 12
  2. Linux x86_64 SELS 11
  3. Linux x86_64 Red Hat Enterprise Linux 7
  4. Linux x86_64 Red Hat Enterprise Linux 6
  5. Linux x86_64 Oracle Linux 7
  6. Linux x86_64 Oracle Linux 6
Redhat Linux prior to 6 is not supported.

Package requirment for Linux 7 (Server)
  • make-3.82-21
  • binutils-2.23
  • gcc-4.8.2-16
  • libaio-0.3.109-12
  • glibc-common-2.17-55
  • libstdc++-4.8.2-16
  • sysstat-10.1.5-4
  • glibc-devel 2.17-55.i686 (This is a 32-bit package)
  • glibc-devel 2.17-55.x86_64 (This is a 64-bit package)
  • libXtst-1.2.2-2.x86_64
  • glibc-2.17

Package requirment for Linux 7 (Agent)
  • make-3.82-21
  • binutils-2.23
  • gcc-4.8.2-16
  • libaio-0.3.109-12
  • glibc-common-2.17-55
  • libstdc++-4.8.2-16
  • sysstat-10.1.5-4

Package requirement for Linux 6
  • make-3.81
  • binutils-2.20
  • gcc-4.4.4
  • libaio-0.3.107
  • glibc-common-2.12-1
  • libstdc++-4.4.4
  • libXtst-1.0.99 (x86_64)
  • sysstat-9.0.4
  • glibc-devel-2.12-1.7 (i686) (This is a 32-bit package)
  • glibc-devel-2.12-1.7 (x86_64) (This is a 64-bit package) 
  • glibc-2.12-1.47.0.2 (i686) (Applicable only for Oracle Linux 6.2, which includes RH6.2 and UEK 6.2)

Package requirment for Linux 6 (Agent)
  • make-3.81
  • binutils-2.20
  • gcc-4.4.4
  • libaio-0.3.107
  • glibc-common-2.12-1.7
  • libstdc++-4.4.4
  • sysstat-9.0.4

Kernel Parameter requirements

net.ipv4.ip_local_port_range = 11000 65500
kernel.shmmax = 4294967295 (OMS and OMR in different server)
or
kernel.shmmax = 8208017408 (OMS and OMR on same server)

User requirement

The Oracle Inventory Group (typically, oinstall)
The Oracle Software Owner User (typically, oracle)

/usr/sbin/groupadd oinstall
/usr/sbin/useradd -g oinstall oracle
passwd oracle

OMR database requirement

Oracle Database (Repository) 12.1.0.2.0.

Ensure that you apply the latest PSU on the supported database, disable the optimizer adaptive feature and set compatible to 12.1.0.2.0.

To check the parameters execute SQL command below:
show parameter optimizer_adaptive_features;
show parameter compatible;













To modify parameter value
alter system set optimizer_adaptive_features=FALSE scope=both;
alter system set compatible="12.1.0.2.0" scope=spfile;











Once parameter is changed restart the database.


Create oracle middleware home directory, Software library and BI CONF and BI CLUSTER directory.

mkdir -p /u02/app/oracle/product/13.1.0.0/Middleware
cd /u02/app/oracle/product/13.1.0.0/
mkdir agent BI_CLUS BI_CONF swlib
chown -R oracle:oinstall /u02/app







Change directory to OEM source and make em13100_linux64.bin executable.








Invoke the Enterprise Manager Cloud Control Installation Wizard
./em13100_linux64.bin








Installation begins.


















































This is the Initial page once binary file em13100_linux64.bin get executed.































Uncheck "I wish to receive security updates via My Oracle Support." option and Click on Next to continue.


Warning message will be displayed. Click on Yes to continue.


Select skip option and Click on Next to continue.































Make sure all prerequisite have been succeed. In my case I do not have sufficient memory on my machine so I need to ignore this warning. Click on Ignore button and Click on Next.


Warning message will be displayed Click on Yes to continue. 
Select Simple option and Click on Next to continue.


Select Middleware Home Location, Agent Base directory and Click on Next to continue.


Select Administrator Password and type OMR(Oracle Management Repository) database details. For installation of Oracle Enterprise Manager Cloud Control we need to install backend Oracle database to store repository. We are providing the same details over here.


Enter the location for Software Library, BI Publisher Config Volume, BI Publisher Cluster Volume. Click on Next to continue.


Summary Will be displayed. Click on Install to begin installation.



Installation on progress. ##########



Installation on progress. ####################



On Terminal Window execute mentioned script as user root. Click on OK once the script execution completes.

Once installation completes, Click on Close to exit installation. Now we can loging with the URL below:

https://192.168.1.61:7802/em






0 comments:

Post a Comment