& Configuration on Database 12.1.0.2
Oracle Enterprise Manager is Oracle's
integrated enterprise information technology (IT) management product line,
which provides the industry's only complete, integrated, and business-driven
enterprise cloud management solution. Oracle Enterprise Manager creates
business value for IT by leveraging the built-in management capabilities of the
Oracle stack for traditional and cloud environments, enabling customers to
achieve unprecedented efficiency gains while dramatically increasing service
levels.
Compatibility Between OMS and Management Agents
Across 13c and 12c Releases
|
|
Oracle Management
Agent 12c Release 3 (12.1.0.3)
|
Oracle Management
Agent 12c Release 4 (12.1.0.4)
|
Oracle Management
Agent 12c Release 5 (12.1.0.5)
|
Oracle Management
Agent 13c
|
|
Oracle Management
Service 13c
|
Yes
|
Yes
|
Yes
|
Yes
|
Starting with 13c (13.1.0.0.0), as part of the Oracle Fusion
Middleware Plug-in deployment, one JVMD Engine is installed and configured by
default on the OMS. For every additional OMS you deploy, you receive one JVMD
Engine by default with that OMS.
Hybrid Cloud Management
With Hybrid Cloud Management, Enterprise Manager
Cloud Control provides you with a "single pane of glass" for
monitoring and managing on-premise as well as Oracle Cloud deployments, all
from the same management console. By deploying Hybrid Cloud Agents onto the
Oracle Cloud virtual hosts serving your Oracle Cloud services, you are able to
manage Oracle Cloud targets just as you would any other. The communication between
Management Agents and your on-premise Oracle Management Service instances is
secure from external interference. In addition to a hardened architecture of
its own, Enterprise Manager supports the use of additional external HTTP
proxies that support tunneling, which can be configured to connect to the
Oracle Cloud.
Lifecycle Management
Lifecycle Management is a comprehensive solution
that helps database, system, and application administrators automate the
processes required to manage the lifecycle of Oracle technology. It eliminates
manual and time-consuming tasks related to discovery, initial provisioning,
patching, configuration management, and ongoing change management. In addition,
the solution provides compliance frameworks for reporting and managing industry
and regulatory compliance standards. Finally, all of the on-premise
instrumentation can be connected in real-time to My Oracle Support for complete
communication between Oracle and customers.
Application Performance Management
Enterprise Manager 13c provides a complete Application Performance
Management (APM) solution for custom applications and Oracle applications
(including E-Business Suite, Siebel, PeopleSoft, JD Edwards, and Fusion
Applications). The APM solution is designed for both cloud and enterprise data
center deployments and is supported on Oracle and non-Oracle platforms.
Pre-installation Requirements for Enterprise
Manager Cloud Control 13c Release 1
Hardware Requirement :
Installation : Simple (1 OMS, <100 Targets,
<10 Agents, <3 )
RAM : 10GB
Hard Disk : 30GB (min)
OS : OEL 6.5 - x64
Package, Kernel Parameter, and Library Requirements
For 32-bit system, you should see
something similar to the following:
glibc-devel-2.3.4-2.43(i386)
glibc-headers-2.3.4-2.43(i386)
glibc-2.3.4-2.43(i686)
compat-glibc-headers-2.3.2-95.30(i386)
glibc-profile-2.3.4-2.43(i386)
glibc-utils-2.3.4-2.43(i386)
glibc-kernheaders-2.4-9.1.103.EL(i386)
glibc-common-2.3.4-2.43(i386)
compat-glibc-2.3.2-95.30(i386)
For 64-bit system, you should see
something similar to the following:
glibc-common-2.3.4-2.43(x86_64)
glibc-devel-2.3.4-2.43(x86_64)
glibc-profile-2.3.4-2.43(x86_64)
glibc-headers-2.3.4-2.43(x86_64)
glibc-utils-2.3.4-2.43(x86_64)
glibc-2.3.4-2.43(x86_64)
rpm -qa | grep glibc-common
rpm -qa | grep glibc-devel
rpm -qa | grep glibc-profile
rpm -qa | grep glibc-headers
rpm -qa | grep glibc-utils
rpm -qa | grep glibc
[root@oem250
~]# yum install -y glibc-common glibc-devel glibc-profile glibc-headers glibc-utils glibc
Loaded
plugins: refresh-packagekit, security
Setting
up Install Process
Package
glibc-common-2.12-1.132.el6.x86_64 already installed and latest version
Package
glibc-devel-2.12-1.132.el6.x86_64 already installed and latest version
No
package glibc-profile available.
Package
glibc-headers-2.12-1.132.el6.x86_64 already installed and latest version
Package
glibc-2.12-1.132.el6.x86_64 already installed and latest version
Resolving
Dependencies
-->
Running transaction check
--->
Package glibc-utils.x86_64 0:2.12-1.132.el6 will be installed
-->
Processing Dependency: libgd.so.2()(64bit) for package:
glibc-utils-2.12-1.132.el6.x86_64
-->
Running transaction check
--->
Package gd.x86_64 0:2.0.35-11.el6 will be installed
-->
Finished Dependency Resolution
Dependencies
Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
glibc-utils x86_64 2.12-1.132.el6 OL64
163 k
Installing
for dependencies:
gd x86_64 2.0.35-11.el6 OL64
141 k
Transaction
Summary
================================================================================
Install 2 Package(s)
Total
download size: 304 k
Installed
size: 581 k
Downloading
Packages:
-------------------------------------------------------------------------------------------------
Total
3.9 MB/s | 304 kB 00:00
Running
rpm_check_debug
Running
Transaction Test
Transaction
Test Succeeded
Running
Transaction
Installing : gd-2.0.35-11.el6.x86_64
1/2
Installing :
glibc-utils-2.12-1.132.el6.x86_64 2/2
Verifying
: glibc-utils-2.12-1.132.el6.x86_64
1/2
Verifying
: gd-2.0.35-11.el6.x86_64
2/2
Installed:
glibc-utils.x86_64 0:2.12-1.132.el6
Dependency
Installed:
gd.x86_64 0:2.0.35-11.el6
Complete!
[root@oem250
~]# rpm -qa | grep glibc
glibc-common-2.12-1.132.el6.x86_64
glibc-devel-2.12-1.132.el6.x86_64
glibc-2.12-1.132.el6.x86_64
glibc-2.12-1.132.el6.i686
glibc-utils-2.12-1.132.el6.x86_64
glibc-headers-2.12-1.132.el6.x86_64
glibc-devel-2.12-1.132.el6.i686
Required Library before installation
|
Platform
|
32-Bit Packages for 32-Bit Platform
|
64-Bit Packages for 64-Bit Platform
|
|
Oracle Linux 7.x
Red Hat
Enterprise Linux 7
Here, x refers to the version of the Oracle Linux release. For
example, Oracle Linux 7.2, where 7 is the release number and 2 is the version
number.
|
Not Supported
|
|
|
Oracle Linux 6.x
Red Hat Enterprise
Linux 6
Here, x refers to the version of the Oracle Linux release. For
example, Oracle Linux 6.2, where 6 is the release number and 2 is the version
number.
|
Not Supported
|
|
|
SUSE Linux
Enterprise 12
|
Not Supported
|
|
|
SUSE Linux
Enterprise 11
|
Not Supported
|
|
|
Solaris SPARC
5.11
|
Not Supported
|
|
|
Solaris SPARC
5.10
Also supported on Solaris Local Container
|
Not Supported
|
SUNWbtool
|
|
Solaris x86-64
5.11
|
Not Supported
|
|
|
Solaris x86-64
5.10
|
Not Supported
|
|
|
IBM AIX 7.1
Note: All maintenance
levels are supported.
Check the
maintenance level using the following command:
oslevel -r
|
Not Supported
|
|
|
IBM AIX 6.1
Note: All maintenance
levels are supported.
Check the
maintenance level using the following command:
oslevel -r
|
Not Supported
|
|
|
HP-UX Itanium 11.31
|
Not Supported
|
|
Package Requirements for Oracle Management Agent
|
Platform
|
32-Bit Packages for 32-Bit Platform
|
64-Bit Packages for 64-Bit Platform
|
|
Oracle Linux 7.x
Red Hat
Enterprise Linux 7
Here, x refers to the version of the Oracle Linux release. For
example, Oracle Linux 7.2, where 7 is the release number and 2 is the version
number.
|
Default Packages Are Sufficient
|
|
|
Oracle Linux 6.x
Here, x refers to the version of the Oracle Linux release. For
example, Oracle Linux 6.2, where 6 is the release number and 2 is the version
number.
|
|
|
|
Red Hat
Enterprise Linux 6
|
|
|
|
SUSE Linux
Enterprise 12
|
Not Supported
|
|
|
SUSE Linux
Enterprise 11
|
|
|
|
Solaris SPARC
5.11
|
Not Supported
|
|
|
Solaris SPARC
5.10
Also supported on Solaris Local Container
|
Not Supported
|
SUNWbtool
|
|
Solaris x86-64
5.11
|
Not Supported
|
|
|
Solaris x86-64
5.10
|
Not Supported
|
|
|
IBM AIX 7.1
Note: All maintenance
levels are supported.
Check the
maintenance level using the following command:
oslevel -r
|
Not Supported
|
|
|
IBM AIX 6.1
Note: All maintenance
levels are supported.
Check the
maintenance level using the following command:
oslevel -r
|
Not Supported
|
|
|
HP-UX Itanium
11.31
|
Not Supported
|
OS-Core(B.11.31)
|
Check your current range for ephemeral ports:
# echo 11000
65500 > /proc/sys/net/ipv4/ip_local_port_range
Make these settings permanent.
Add below in /etc/sysctl.conf and restart network services
net.ipv4.ip_local_port_range = 11000 65000
oem250 # sysctl -p
Setting Up kernel.shmmax Kernel Parameter
If OMS and Management Repository
Are on Different Hosts
If you are installing OMS and Management Repository (database)
on different hosts, which are running on Linux operating systems (32-bit or
64-bit), then on the OMS host, set the
kernel.shmmax parameter to a value 1 byte less than 4 GB or 4294967295.
Oracle recommends this value to avoid
lack of memory issues for other applications and to enable a complete and
successful core file generation under any and all circumstances.
·
To verify the value assigned to the
kernel.shmmax parameter, run the following command:cat /proc/sys/kernel/shmmax
·
To set the value for
kernel.shmmax parameter, do the following:
1.
Log in as root.
2.
Open the
/etc/sysctl.conf file.
3.
Set the
kernel.shmmax parameter to 4294967295.
By setting the value in the
/etc/sysctl.conf file, the value persists even when
you restart the system. On SUSE Linux Enterprise Server systems, run the
following command to ensure that the system reads the /etc/sysctl.conf file when it restarts:# /sbin/chkconfig boot.sysctl on
4.
Run the following command to change
the current values of the kernel parameters. Review the output and verify that
the values are correct. If the values are incorrect, edit the
/etc/sysctl.conf file, then run this command again.# /sbin/sysctl -p
5.
Enter the command
/sbin/sysctl -a to confirm that the values are set
correctly.
6.
After updating the values of the
kernel parameters in the
/etc/sysctl.conf file, either restart the host, or run the command sysctl -p to make the changes in the /etc/sysctl.conf file available in the active kernel
memory.
If OMS and Management Repository
Are on the Same Host
If you are installing OMS and
Management Repository (database) on the same host, which is running on a Linux
operating system (32-bit or 64-bit), then set the kernel.shmmax parameter
to a value prescribed in the Oracle Database Installation Guide that
is published for the intended database release and platform.
Library Requirements for Oracle Management Service
|
Platform
|
32-Bit Libraries for 32-Bit
Platform
|
64-Bit Libraries for 64-Bit
Platform
|
|
Oracle Linux 7.x
Red Hat Enterprise Linux 7.x
Here, x refers to the version of the Oracle Linux release. For
example, Oracle Linux 7.2, where 7 is the release number and 2 is the version
number.
|
Not Supported
|
glibc-2.17
|
|
Oracle Linux 6.x
Red Hat Enterprise Linux 6.x
Here, x refers to the version of the Oracle Linux release. For
example, Oracle Linux 6.2, where 6 is the release number and 2 is the version
number.
|
Not Supported
|
glibc-2.12
|
|
SUSE Linux Enterprise 10 (Service Pack 4)
|
Not Supported
|
glibc-2.2.4
|
|
SUSE Linux Enterprise 11
|
Not Supported
|
glibc-2.11
|
Creating the Operating System Groups and Users Required
To determine whether the Oracle
Inventory group exists, enter the following command:
If the oraInst.loc file exists, then the output from
this command looks like:
inventory_loc=/u01/app/oracle/oraInventory
inst_group=oinstall
The inst_group parameter
shows the name of the Oracle Inventory group, oinstall. Else create group and user
# /usr/sbin/groupadd oinstall
# /usr/sbin/useradd -g oinstall oracle
[root@oem250
~]# uname -a
Linux oem250.ora.com 3.8.13-16.2.1.el6uek.x86_64 #1 SMP
Thu Nov 7 17:01:44 PST 2013 x86_64 x86_64 x86_64 GNU/Linux
[root@oem250
~]# id oracle
uid=54321(oracle) gid=54321(oinstall)
groups=54321(oinstall),54322(dba)
Installing Cygwin
and Starting the SSH Daemon on Microsoft Windows hosts. This is applicable only
when you want to install a Management Agent on a Microsoft Windows host, using
the Add Host Targets Wizard or EM CLI.
Click here for more details
Installing Oracle Enterprise Manager Cloud Control
Simple Installation Means for demonstration or evaluation purposes,
and small deployments, and when you do not want to worry about the granular
control of the installer and want to install the Enterprise Manager system
quickly, with less memory, and for monitoring fewer targets in their
environment
Advanced Installation Means for
small, medium, and large deployments, and when you want to customize your installation
with custom locations, directory names, and passwords.
Prerequisites for Installing an Enterprise Manager
System
|
Database Patch Requirements
|
Ensure that you apply the latest
PSU on the supported database.
|
|
Database
Optimizer Adaptive Feature Requirement
|
Ensure that you
disable the optimizer adaptive feature (optimizer_adaptive_features=FALSE) in
the Oracle Database that houses the Management Repository. To do so, follow
these steps:
1. Disable the optimizer adaptive feature by setting theoptimizer_adaptive_features parameter
to FALSE. To do so, run the following SQL command:
alter system set
optimizer_adaptive_features=false scope=both sid='*';
2. Restart the database.
3. Verify that the changes have taken effect. To do so, run the
following SQL command:
show parameter
adaptive;
You should see the
following output:
NAME
TYPE VALUE
---------------------------------------------------
optimizer_adaptive_features
boolean FALSE
|
Ensure that your DB repository is having latest PSU
applied. In my case I have applied
APR-2015 (20299023)
SQL> select patch_id, patch_uid, version, status, description
from dba_registry_sqlpatch
where bundle_series = 'PSU'
;
PATCH_ID PATCH_UID VERSION STATUS
DESCRIPTION
--------- ---------- -------- -------
-------------------------------------------------
20299023 18703022 12.1.0.2 SUCCESS Database Patch Set
Update : 12.1.0.2.3 (20299023)
PATCH_ID
PATCH_UID DESCRIPTION APPLIED_DATE SQL_PATC
ROLLBACK
---------- ---------
------------------------------------------------- ------------------------ -------
--------
20299023
18703022 Database Patch Set Update : 12.1.0.2.3 (20299023) 2015-12-21T21:58:58+05:30 true
true
19769480
18350083 Database Patch Set Update : 12.1.0.2.2 (19769480) 2015-12-21T21:58:33+05:30 true
true
To verify if a port is free, run the following command:
On Unix:
netstat -an | grep <port no>
On Microsoft Windows:
netstat -an|findstr <port_no>
Invoke the Enterprise Manager Cloud Control
Installation Wizard.
for Linux platform
Note : For OEM13c installation you don't
need to unzip any software in software directory.
oem250 $
/SOFT/OEM13c/em13100_linux64.bin
The installer requires about 10 GB of
hard disk space in the temporary directory. If your temporary directory does
not have this space, then pass the -J-Djava.io.tmpdir parameter and provide an alternative
directory where there is 10 GB of space.
oem250 $ ./em13100_linux64.bin -J-Djava.io.tmpdir=/SOFT/em13c/stage/
FOR Microsoft Windows
run setup_em_win64.exe.
Note:
Ensure that there are no white spaces in the name of the
directory where you download and run the Enterprise Manager Cloud Control
software.
Click Next
Click Next
Ensure that all prerequisite has ran successfully then, Click Next
Choose Simple Installation as I am going to install Single OMS Installation.
Click Next
Select Middleware home and Agent base directory, Click Next
Enter the detail of 12c Database to installed management repository data, then Click Next
Its recommended that management repository character set is AL32UTF8, which supports of virtually all language of the world, then Click Next
Some prerequisites were failed which will fixed by installer on his own, then Click Next
Also set the session cached cursor parameters at DB level and restart. This can be fixed prior to installation.
Click Next
Verify the configuration you entered then Click on Install button
Run allroot.sh as privileges user and Click OK
Finally Installation has done successfully, Please copy and save the below details for your future reference.
Failure Installation or Rollback Plan
If you have run the installation wizard and let the installation
wizard take corrective actions to correct the repository settings, and if you
have exited the wizard without completing the installation process, then
remember that the repository settings might not reset to their original values
because you abruptly ended the installation. In this case, before invoking the
installation wizard again, run the EM Prerequisite Kit to manually reset the values.
To do so, run the following command and pass a response file that captures the
details for the EM Prerequisite Kit:
./em13100_linux64.bin EMPREREQ_KIT=true
EMPREREQKIT_PROPERTY_FILE=<absolute_path_to_reponse_file>
The response file should contain the following:
installerMode=emprereqkit
executionType=install
prerequisiteXMLRootDir=<prereq_xmlrootdir_location>
connectString=<connect_string>
dbUser=SYS
dbPassword=password
reposUser=sysman
dbRole=sysdba
runPrerequisites=true
runPostCorrectiveActions=true
Verify
the Installation
After successfully installed OEM 13c R1, Need to login on OEM 13c Web Console on your web browser.
Set the home page
Validate the version
This part of installation has been done.
Hope this will help....:)
Prefect.
ReplyDelete