Upgrade OPatch In OEM 13c Home

Overview
Earlier Opatch utility used unzip to install files in the home. Now the version greater than or equal to 13.6.x it uses the OUI installation method. With this it ensures that installer both executes the file updates and logs the components and file changes to the OUI meta-data. With unzip method the OUI is not aware of these changes.

This procedure is only applicable to Enterprise Manager Cloud Control environment.

In this article I will demonstrate how to upgrade Opatch utility in OEM 13c Agent home. The same procedure is also applicable when upgrading Opatch in OMS home.

Download Opatch utility

 

  

dm01db01-orcldb1 {/u01/app}:cd /u01/app/oracle/software/
dm01db01-orcldb1 {/u01/app/oracle/software}:ls -l p6880880_139000_Generic.zip
-rw-r--r-- 1 oracle oinstall 41188149 Jan  9 05:55 p6880880_139000_Generic.zip

dm01db01-orcldb1 {/u01/app/oracle/software}:unzip p6880880_139000_Generic.zip
Archive:  p6880880_139000_Generic.zip
   creating: 6880880/
  inflating: 6880880/README.txt
  inflating: 6880880/opatch_generic.jar
  inflating: 6880880/version.txt

dm01db01-orcldb1 {/u01/app/oracle/software}: cd 6880880/
dm01db01-orcldb1 {/u01/app/oracle/software/6880880}:ls -ltr
total 40424
-rw-r--r-- 1 oracle oinstall       10 Nov 21 12:17 version.txt
-rw-r--r-- 1 oracle oinstall 41338422 Nov 21 12:17 opatch_generic.jar
-rw-rw-r-- 1 oracle oinstall     3084 Dec  9 17:04 README.txt

dm01db01-orcldb1 {/u01/app/oracle/software/6880880}:view README.txt

dm01db01-orcldb1 {/u01/app/oracle/software/6880880}:export

ORACLE_HOME=/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0

dm01db01-orcldb1 {/u01/app/oracle/software/6880880}:echo $ORACLE_HOME
/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0

Here my current opatch version is 13.8 which is greater than 13.6. So I must use the new approach to upgrade my opatch utility.

dm01db02-orcldb2 {/u01/app/oracle/software/6880880}:cd $ORACLE_HOME/OPatch

dm01db02-orcldb2 {/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0/OPatch}:./opatch version
OPatch Version: 13.8.0.0.0

OPatch succeeded.

• Backup your <ORACLE_HOME>

dm01db02-orcldb2 {/home/oracle}:cd $ORACLE_HOME

dm01db02-orcldb2 {/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0}:pwd
/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0

dm01db02-orcldb2 {/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0}:tar -zxvf /u01/app/oracle/product/Agent13c/agent13.2.tgz .

• Verify Java

dm01db02-orcldb2 {/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0/OPatch}:which java
/usr/bin/java

dm01db02-orcldb2 {/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0/OPatch}:java -version
java version "1.7.0_91"
Java(TM) SE Runtime Environment (build 1.7.0_91-b32)
Java HotSpot(TM) 64-Bit Server VM (build 24.91-b03, mixed mode)

• Install the Opatch software using java:

 dm01db02-orcldb2 {/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0/OPatch}:java -jar

/u01/app/oracle/software/6880880/opatch_generic.jar -silent

oracle_home=/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0
Launcher log file is /tmp/OraInstall2017-02-01_05-15-22AM/launcher2017-02-01_05-15-22AM.log.
Extracting the installer . . . . Done
Checking if CPU speed is above 300 MHz.   Actual 2526.856 MHz    Passed
Checking swap space: must be greater than 512 MB.   Actual 16378 MB    Passed
Checking if this platform requires a 64-bit JVM.   Actual 64    Passed (64-bit not required)
Checking temp space: must be greater than 300 MB.   Actual 37114 MB    Passed

Preparing to launch the Oracle Universal Installer from /tmp/OraInstall2017-02-01_05-15-22AM
Installation Summary

Disk Space : Required 6 MB, Available 87,486 MB
Feature Sets to Install:
        Next Generation Install Core 13.9.1.0.0
        OPatch 13.9.1.0.0
        OPatch Auto OPlan 13.9.1.0.0
Session log file is /tmp/OraInstall2017-02-01_05-15-22AM/install2017-02-01_05-15-22AM.log

Loading products list. Please wait.
 1%
 40%

Loading products. Please wait.
 43%
 46%
 49%
 51%
 54%
 57%
 60%
 62%
 65%
 68%
 71%
 74%
 77%
 80%
 82%
 85%
 88%
 91%
 94%
 97%
 99%
Updating Libraries

Starting Installations
 1%
 2%
 3%
 4%
 5%
 6%
 7%
 8%
 9%
 10%
 11%
 12%
 13%
 14%
 15%
 16%
 17%
 18%
 19%
 20%
 21%
 22%
 23%
 24%
 25%
 26%
 27%
 28%
 29%
 30%
 31%
 32%
 33%
 34%
 35%
 36%
 37%
 38%
 39%
 40%
 41%
 42%
 43%
 44%
 45%
 46%
 47%
 48%
 49%
 50%
 51%
 52%
 53%
 54%
 55%
 56%
 57%
 58%
 59%
 60%
 61%
 62%
 63%
 64%
 65%
 66%
 67%
 68%
 69%
 70%
 71%
 72%
 73%
 74%
 75%
 76%
 77%
 78%
 79%
 80%
 81%
 82%
 83%
 84%
 85%
 86%
 87%
 88%
 89%
 90%
 91%
 92%

Install pending
Installation in progress

 Component : oracle.swd.opatch 13.9.1.0.0
Copying files for 'oracle.swd.opatch 13.9.1.0.0 '
 Component : oracle.glcm.osys.core 13.9.1.0.0
Copying files for 'oracle.glcm.osys.core 13.9.1.0.0 '
 Component : oracle.glcm.oplan.core 13.9.1.0.0
Copying files for 'oracle.glcm.oplan.core 13.9.1.0.0 '
 Component : oracle.glcm.opatch.common.api 13.9.1.0.0
Copying files for 'oracle.glcm.opatch.common.api 13.9.1.0.0 '
 Component : oracle.glcm.opatchauto.core 13.9.1.0.0
Copying files for 'oracle.glcm.opatchauto.core 13.9.1.0.0 '
 
Install successful

Post feature install pending
Post Feature installing
 Feature Set : oracle.glcm.osys.core.classpath
 Feature Set : apache_commons_cli_lib
 Feature Set : oracle.glcm.oplan.core.classpath
Post Feature installing 'apache_commons_cli_lib'
Post Feature installing 'oracle.glcm.oplan.core.classpath'
 Feature Set : oracle.glcm.opatch.common.api.classpath
 Feature Set : oracle.glcm.opatchauto.core.binary.classpath
 Feature Set : apache_commons_compress_lib
 Feature Set : oracle.glcm.opatchauto.core.wallet.classpath
 Feature Set : oracle.glcm.opatchauto.core.classpath
 
Post Feature installing 'oracle.glcm.opatchauto.core.wallet.classpath'
Post Feature installing 'apache_commons_compress_lib'
Post Feature installing 'oracle.glcm.opatchauto.core.binary.classpath'
 Feature Set : oracle.glcm.opatchauto.core.actions.classpath
Post Feature installing 'oracle.glcm.opatch.common.api.classpath'
Post Feature installing 'oracle.glcm.opatchauto.core.actions.classpath'
Post Feature installing 'oracle.glcm.osys.core.classpath'
Post Feature installing 'oracle.glcm.opatchauto.core.classpath'
Post feature install complete
String substitutions pending
String substituting
 Component : oracle.swd.opatch 13.9.1.0.0
String substituting 'oracle.swd.opatch 13.9.1.0.0 '
 Component : oracle.glcm.osys.core 13.9.1.0.0
String substituting 'oracle.glcm.osys.core 13.9.1.0.0 '
 Component : oracle.glcm.oplan.core 13.9.1.0.0
String substituting 'oracle.glcm.oplan.core 13.9.1.0.0 '
 Component : oracle.glcm.opatch.common.api 13.9.1.0.0
String substituting 'oracle.glcm.opatch.common.api 13.9.1.0.0 '
 Component : oracle.glcm.opatchauto.core 13.9.1.0.0
String substituting 'oracle.glcm.opatchauto.core 13.9.1.0.0 '
String substitutions complete
Link pending
Linking in progress
 Component : oracle.swd.opatch 13.9.1.0.0
Linking 'oracle.swd.opatch 13.9.1.0.0 '
 Component : oracle.glcm.osys.core 13.9.1.0.0
Linking 'oracle.glcm.osys.core 13.9.1.0.0 '
 Component : oracle.glcm.oplan.core 13.9.1.0.0
Linking 'oracle.glcm.oplan.core 13.9.1.0.0 '
 Component : oracle.glcm.opatch.common.api 13.9.1.0.0
Linking 'oracle.glcm.opatch.common.api 13.9.1.0.0 '
 Component : oracle.glcm.opatchauto.core 13.9.1.0.0
Linking 'oracle.glcm.opatchauto.core 13.9.1.0.0 '
Linking in progress

Link successful

Setup pending
Setup in progress
 Component : oracle.swd.opatch 13.9.1.0.0
Setting up 'oracle.swd.opatch 13.9.1.0.0 '
 Component : oracle.glcm.osys.core 13.9.1.0.0
Setting up 'oracle.glcm.osys.core 13.9.1.0.0 '
 Component : oracle.glcm.oplan.core 13.9.1.0.0
Setting up 'oracle.glcm.oplan.core 13.9.1.0.0 '
 Component : oracle.glcm.opatch.common.api 13.9.1.0.0
Setting up 'oracle.glcm.opatch.common.api 13.9.1.0.0 '
 Component : oracle.glcm.opatchauto.core 13.9.1.0.0
Setting up 'oracle.glcm.opatchauto.core 13.9.1.0.0 '
 
Setup successful

Save inventory pending
Saving inventory
 93%
Saving inventory complete
 94%
Configuration complete
Logs successfully copied to /u01/app/oraInventory/logs.
dm01db02-orcldb2 {/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0/OPatch}:

• Verify Opatch software is upgraded

dm01db02-orcldb2 {/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0/OPatch}:./opatch version
OPatch Version: 13.9.1.0.0

OPatch succeeded.

• Test new Opatch software

dm01db02-orcldb2 {/u01/app/oracle/product/Agent13c/agent_13.2.0.0.0/OPatch}:./opatch lspatches
24470104;

OPatch succeeded.



Conclusion
In this article we have learned to how to upgrade the Opatch utility in OEM 13c agent home using OUI. Opatch 13.6 and above uses a new method to upgrade Opatch.

Note: There is no way to revert only OPatch to an older version. To revert OPatch, restore the backup for your ORACLE_HOME.

Discover Exadata Database Machine in OEM 13c

Overview

To manage and monitor Exadata Database Machine you must discover it in Oracle Enterprise Manager. Before you discover Exadata DBM you first Install EM Agent on all Exadata Compute nodes. The Guided Discovery Process of OEM helps you discover all the Exadata Components easily.

The following Exadata components can be monitored and managed by OEM:

• Compute Nodes
• Storage Cells
• Infiniband Switches
• Cisco Switches
• Power Distribution Units
• KVM

In this article I will demonstrate how to discover an Exadata Database Machine in OEM 13c. Discover Exadata in OEM 13c is no different than OEM 12c except couple of changes. The graphics part of the OEM 13c looks very coolJ

Before we starting with the Discovery process make sure that OEM 13c Agent is installed on Compute nodes. You can find the article to install EM Agent at:

http://netsoftmate.blogspot.in/2017/01/install-em-agent-on-exadata-using.html

Before you start make sure

• OEM 13c server is Installed and Configured
• OEM 13c Agent is installed on all Exadata Compute Nodes
• SYSMAN User password
• Oracle user password
• Root user password for Compute nodes, Storage Cells and Infiniband Switches

Procedure to Discover Exadata Database Machine in OEM 13c

Enter the OEM 13c address in the web browser

Enter the SYSMAN user and password or any other user with admin privileges.

This is our OEM 13c home page

From the home, click Setup --> Add Target --> Add Targets Manually

Click on "Add Using Guided Process"

Select "Oracle Exadata Database Machine" and click Add button.

Select "Discover a new Database Machine and its hardware components and targets", "13c target type with enhanced hardware monitoring, requiring additional credentials" and Click "Discover Targets"

On this page, search or enter the EM agent URL for compute node 1 and, Click Add buton and add the compute node 1 and enter the oracle user credentials.
Note: Make databasemachine.xml exist and Oracle user have necessary permissions to read it.

Select Compute node 1 and click select.

Click Next

On this page, enter the first Infiniband Switch name and root credentials and test connection. Click Next

Click Next

All the Exadata Components are Discovered and shown on this page. Click Next

This Page shows the Exadata Components monitored by different Agents. Click Next

On this page Enter the Credentials for Agent Host, Compute Node ILOM, Storage Cell, IB Switch, PDU, Cisco Switch and test connection for each of them. Click Next

Review the Summary Page and Click Next 

The Target Promotion in progress 

Click Done on the final page (Not shown here). Make sure no errors are reported.

Click Launch Database Machine will bring you to the following page 

This is the Photo realistic image of Exadata Database machine.

We have discovered Exadata Database Machine successfully in OEM 13c

Conclusion

In this article we have seen how to discover an Exadata Database Machine in Oracle Enterprise Manager 13c using simple Guided discovery process. Oracle Enterprise manager 13c considered ideal for managing and monitoring Exadata Database Machine.