July 2016 ~ Dilli's Oracle/MySQL Linux Blog

Thursday, July 21, 2016

Upgrade OEM 12c to OEM 13c Cloud control

8:23 AM Posted by Dilli Raj Maharjan 1 comment

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.
If we have Enterprise Manager Cloud Control 12c Release 5 (12.1.0.5), 12c Release 4 (12.1.0.4) or 12c Release 3 (12.1.0.3) then Oracle recommends that you upgrade it to 13c Release 1 to benefit from all the new features.

Supported environment for upgrading to OEM 13c Cloud control:

12c Release 5 (12.1.0.5)
12c Release 4 (12.1.0.4)
12c Release 3 (12.1.0.3) without BI Publisher. If BI publisher is configured then we need to upgrade to 12c Release 4 or 5

Supported OMR database version

Oracle 12.1.0.2.0

Supported Managed Targets

Oracle 12.1.0.2.0
Oracle 12.1.0.1.0
Oracle 11.2.0.4.0
Oracle 11.2.0.3.0
Oracle 11.2.0.2.0
Oracle 11.2.0.1.0
Oracle 11.1.0.7.0
Oracle 10.2.0.5.0
Oracle 10.2.0.4.0
Oracle 10.2.0.5.0
Oracle 10.2.0.4.0
Oracle 10.1.0.5.0

Supported Agent version

Agent 13.1.0.0.0
Agent 12.1.0.5.0
Agent 12.1.0.4.0
Agent 12.1.0.3.0

Restriction

Pre-installed JDK or Oracle Weblogic is not supported from 13c Release 1 onward.
Dedicated Oracle Weblogic Server 12c Release 1 is required.
The central agent (in other words, the Management Agent installed with the OMS) is not upgraded by default. You must upgrade it using the Agent Upgrade Console available in the Enterprise Manager Cloud Control Console after upgrading the OMS.
After upgrading the OMS, you must upgrade the Management Agent separately using the Agent Upgrade Console. Agent Upgrade Console is a GUI console that you see in the Enterprise Manager Cloud Control Console after you upgrade the OMS.
To access the Agent Upgrade Console, from the Setup menu, click Manage Cloud Control, then select Upgrade Agents.

Upgrading OMR note

Ensure that you stop the OMS instances of the earlier release that are connected to the database

emctl stop oms -all

Ensure that you do not have any login or logoff triggers set in the Oracle Database that houses the Oracle Management Repository
SELECT COUNT (trigger_name) FROM sys.dba_triggers WHERE TRIGGERING_EVENT LIKE 'LOGIN%' AND status='ENABLED';
SELECT COUNT (trigger_name) FROM sys.dba_triggers WHERE TRIGGERING_EVENT LIKE 'LOGOFF%' AND status='ENABLED';

Disable if logon or logoff triggers exists

alter trigger disable;
alter trigger enable;

Upgrade the database to 12.1.0.2

Disable the optimizer adaptive feature by setting the optimizer_adaptive_features to false and set compatible to 12.1.0.2.0

alter system set optimizer_adaptive_features=false scope=both;

ALTER SYSTEM SET COMPATIBLE='12.1.0.2.0' SCOPE=SPFILE;

Restart the OMR database.

Copy emkey

$/bin/emctl config emkey -copy_to_repos [-sysman_pwd ]

Verify with the following command

$/bin/emctl status emkey

If the emkey is copied, then you will see the following message:

The EMKey is configured properly, but is not secure.
Secure the EMKey by running "emctl config emkey -remove_from_repos".

Restart OMS service.

$/bin/emctl stop oms -all
$/bin/emctl start oms

Create new Middleware home and BI Config and cluster directory should be outside of the Middleware home.

mkdir -p /ssd/oracle/Middleware_1
mkdir -p /ssd/oracle/bi_config
mkdir -p /ssd/oracle/bi_cluster
chown -R oracle:oinstall /ssd/oracle/Middleware_1
chown -R oracle:oinstall /ssd/oracle/bi_config
chown -R oracle:oinstall /ssd/oracle/bi_cluster

To run em pre-requisite check before performing upgrade. Execute following command

./em13100_linux64.bin EMPREREQ_KIT=true EMPREREQKIT_PROPERTY_FILE=

Sample property file
installerMode=emprereqkit
connectString=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=core.localdomain)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=testoem)))
dbPassword=dill1o@
dbRole=sysdba
dbUser=SYS
executionType=install
logLoc=/u01/software/em13c/prerequisiteResults/log
prereqResultLoc=/u01/software/em13c/prerequisiteResults
reposUser=SYSMAN
runPrerequisites=true

Stop the JVMD and ADP engines explicitly:

$/bin/emctl extended oms jvmd stop -all
$/bin/emctl extended oms adp stop –all

Shutdown OMS

$/bin/emctl stop oms -all

Management Agent Shutdown requirement

$/gc_inst/bin/emctl stop agent

For error emkey has not been copied

/bin/emctl config emkey -copy_to_repos_from_file -repos_host -repos_port -repos_sid -repos_user SYSMAN [-repos_pwd ] [-admin_pwd ] -emkey_file /sysman/config/emkey.ora

TMP directory required at least 10G space, if we do not have sufficient space we can create new temp directory for installation.

mkdir -p /data/tmp/
chown -R oracle:oinstall /data/tmp/

If you are using redhat-6.8 or centos 6.8 modify the parameter to 6.7 because 6.8 is not certified yet.

You may encounter the error below:
Expected result: One of enterprise-6.7,enterprise-6.6,enterprise-6.5,enterprise-6.4,enterprise-6.3,enterprise-6.2,enterprise-6.1,enterprise-6.0,oracle-7.1,oracle-7,redhat-7.1,redhat-7,oracle-8,redhat-6.7,redhat-6.6,redhat-6.5,redhat-6.4,redhat-6.3,redhat-6.2,redhat-6.1,redhat-6.0,SuSE-11,SuSE-12
Actual Result: redhat-6.8

Make source file executable

chown 755 em13100_linux64.bin

Execute em13100_linux64.bin with the command below. Note in my case I have used new temp directory due to un sufficient space on /tmp

./em13100_linux64.bin -J-Djava.io.tmpdir=/data/tmp

Once you execute the em13100_linux64.bin binary this is the landing page.

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

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

Select Skip and Click on Next to continue.

All Prerequisite checks should be succeeded before beginning the installation. Click on Next to continue.

Select Upgrade and existing Enterprise Manager system Click on Next to continue.

Select new Middleware home Click on Next to continue.

Provide the Repository database details. Select Confirm that you have backed up Management Repository and Disable DDMP jobs Click on Next to continue.

Repository database related prerequisite checks in progress.

Patch related information will be displayed. Click on OK once you applied minimal patches required for repository database.

If Management agent is not closed then this message will pop up. Stop the agent and click on OK to continue.

Some fixable configuration requirements error will be displayed. Click on Yes to fix it automatically.

Few warning message regarding the requirements. Click on OK to fix it and continue.

Plugin details will be displayed. Click on Next to continue.

We can choose additional plugins in the case we required. Click on Next to continue.

Type extended weblog server domain Click on Next to continue.

Type BI Publisher Config Volume and Cluster Volume. Click on Next to continue.

BI Publisher port details will be displayed Click on Next to continue.

Summary will be displayed Click on Upgrade to begin upgrade.

Upgrade on progress ##########.

Upgrade on progress ####################.

Upgrade on progress ##############################.

Upgrade on progress ########################################.

Execute listed allroot.sh script file as user root. Once execution completes Click on OK to continue.

Information regarding OEM upgrade complete will be displayed. Click on Close to complete upgrade.

Now we can login OEM 13c with the same details as of OEM 12c. Same URL and same user credentials.

Click I accept on the License Agreement.

OEM 13c is ready to use.

Friday, July 15, 2016

Install Oracle Enterprise Manager 13c Cloud control

6:38 AM Posted by Dilli Raj Maharjan Oracle Installation No comments

Few Features are listed below:

Compliance framework for OS, Database and Middleware.
SLA Metering.
Nerve center of IT operations among thousands of enterprises.
Tracks unplanned and planned downtime windows.
Has monitoring capabilities with Always On features. Which can keep on monitoring in the case of OEM is down itself.
Notification blackouts.
Hardware and software stack management. It helps drill down into the infrastructure problems easily. Ref: https://www.youtube.com/watch?v=Olxq5MMvU0s
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).
Integration of Exacheck into the Compliance framework of Enterprise Manager that generate automated notifications and reports for any violation in their Exadata configurations.
Engineered Systems patching.
Continuous data refresh between production and test databases.

Installation Type:
Simple Installation
Advanced Installation

Supported Management Agents for Oracle Management Service 13c

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

Restrictions:

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.
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.
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.
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.
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.
As a prerequisite, you must have an existing Oracle Database to configure the Management Repository.
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.
You can optionally use the database templates offered by Oracle to create a database instance with a preconfigured Management Repository.
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
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

Configuration	Small	Medium	Large
CPU	4	6	12
RAM	10GB	12GB	24GB
HDD	24GB	24GB	24GB

Operating System Requirements

Linux x86_64 SELS 12
Linux x86_64 SELS 11
Linux x86_64 Red Hat Enterprise Linux 7
Linux x86_64 Red Hat Enterprise Linux 6
Linux x86_64 Oracle Linux 7
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.