This week I had the opportunity to patch Oracle Enterprise Manager (EM) 13c with Release 4, Update 6: RU6 (13.4.0.6). I won’t lie, this post is more for me than anything else, to document the handy the steps I followed.
One of the things I did prior to starting this exercise was to update the OMSpatcher, but I won’t go into details on how to to do it, you can find the information in MOS Doc ID 2646080.1.
First, I found the details of my OMS (Oracle Enterprise Manager Management Service ).
[[email protected] ~]$ export ORACLE_HOME=/u01/app/oracle/middleware
[[email protected] ~]$ echo $ORACLE_HOME
/u01/app/oracle/middleware
[[email protected] ~]$ $ORACLE_HOME/bin/emctl status oms -details
Oracle Enterprise Manager Cloud Control 13c Release 4
Copyright (c) 1996, 2020 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
Console Server Host : oracleenterprisemanager
HTTP Console Port : 7788
HTTPS Console Port : 7803
HTTP Upload Port : 4889
HTTPS Upload Port : 4903
EM Instance Home : /u01/app/oracle/gc_inst/em/EMGC_OMS1
OMS Log Directory Location : /u01/app/oracle/gc_inst/em/EMGC_OMS1/sysman/log
OMS is not configured with SLB or virtual hostname
Agent Upload is locked.
OMS Console is locked.
Active CA ID: 1
Console URL: https://oracleenterprisemanager:7803/em
Upload URL: https://oracleenterprisemanager:4903/empbs/upload
WLS Domain Information
Domain Name : GCDomain
Admin Server Host : oracleenterprisemanager
Admin Server HTTPS Port: 7102
Admin Server is RUNNING
Oracle Management Server Information
Managed Server Instance Name: EMGC_OMS1
Oracle Management Server Instance Host: oracleenterprisemanager
WebTier is Up
Oracle Management Server is Up
JVMD Engine is Up
BI Publisher Server Information
BI Publisher Managed Server Name: BIP
BI Publisher Server is Up
BI Publisher HTTP Managed Server Port : 9701
BI Publisher HTTPS Managed Server Port : 9803
BI Publisher HTTP OHS Port : 9788
BI Publisher HTTPS OHS Port : 9851
BI Publisher is locked.
BI Publisher Server named 'BIP' running at URL: https://oracleenterprisemanager:9851/xmlpserver/servlet/home
BI Publisher Server Logs: /u01/app/oracle/gc_inst/user_projects/domains/GCDomain/servers/BIP/logs/
BI Publisher Log : /u01/app/oracle/gc_inst/user_projects/domains/GCDomain/servers/BIP/logs/bipublisher/bipublisher.log
Next, I built the WebLogic encrypted configuration and key files. For this I need my WebLogic password.
[[email protected] ~]$ cd $ORACLE_HOME
[[email protected] ~]$ ./createkeys.sh -oh $ORACLE_HOME -location $HOME/working/antunez/em_keys
The oraclehome passed is valid.
Please enter weblogic admin server username: weblogic
Please enter weblogic admin server password:
Trying to get configuration and key files for the given inputs...
This operation will take some time. Please wait for updates...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> connect('weblogic','WEBLOGIC_PASSWORD','t3s://oracleenterprisemanager:7102')
Connecting to t3s://oracleenterprisemanager:7102 with userid weblogic ...
<Sep 28, 2020 12:49:51 PM MST> <Info> <Security> <BEA-090905> <Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.>
<Sep 28, 2020 12:49:51 PM MST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to HMACDRBG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.>
<Sep 28, 2020 12:49:51 PM MST> <Info> <Security> <BEA-090908> <Using the default WebLogic SSL Hostname Verifier implementation.>
Successfully connected to Admin Server "EMGC_ADMINSERVER" that belongs to domain "GCDomain".
wls:/GCDomain/serverConfig/> storeUserConfig('/home/oracle/working/antunez/em_keys/config','/home/oracle/working/antunez/em_keys/key')
Creating the key file can reduce the security of your system if it is not kept in a secured location after it is created. Creating new key...
The username and password that were used for this WebLogic Server connection are stored in /home/oracle/working/antunez/keys/config and /home/oracle/working/antunez/em_keys/key.
wls:/GCDomain/serverConfig/>
'createkeys' succeeded.
Once I had done this, I created a property file to be used during the patching activities so I wouldn’t have to input the Weblogic information over and over.
[[email protected] ~]$ cat $HOME/working/antunez/PropertyFile.txt
AdminServerURL=t3s://oracleenterprisemanager:7102
AdminConfigFile=/home/oracle/working/antunez/em_keys/config
AdminKeyFile=/home/oracle/working/antunez/em_keys/key
The next step was to analyze whether this patch was applicable to my OMS home. Because I was copy-pasting from a VI file, the hyphen for the “analyze” command was not read correctly. I tried again, typing the hyphen manually, and was able to proceed.
[[email protected] ~]$ cd /u01/working/software/13.4.0.6/31767864
[[email protected] ~]$ export ORACLE_HOME=/u01/app/oracle/middleware
[[email protected] ~]$ export omspatcher=$ORACLE_HOME/OMSPATCHER/omspatcher
[[email protected] ~]$ export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OMSPatcher:$PATH
[[email protected] ~]$ omspatcher apply -analyze -property_file $HOME/working/antunez/PropertyFile.txt
OMSPatcher Automation Tool
Copyright (c) 2017, Oracle Corporation. All rights reserved.
OMSPatcher version : 13.9.4.2.0
OUI version : 13.9.4.0.0
Running from : /u01/app/oracle/middleware
Log file location : /u01/app/oracle/middleware/cfgtoollogs/omspatcher/opatch2020-09-28_11-19-10AM_1.log
OMSPatcher log file: /u01/app/oracle/middleware/cfgtoollogs/omspatcher/31767864/omspatcher_2020-09-28_11-19-25AM_analyze.log
...
Configuration Validation: Success
Running apply prerequisite checks for sub-patch(es) "31661020,31661036,31812958,31661157,31661194,31661066" and Oracle Home "/u01/app/oracle/middleware"...
Sub-patch(es) "31661020,31661036,31812958,31661157,31661194,31661066" are successfully analyzed for Oracle Home "/u01/app/oracle/middleware"
Complete Summary
================
All log file names referenced below can be accessed from the directory "/u01/app/oracle/middleware/cfgtoollogs/omspatcher/2020-09-28_11-19-10AM_SystemPatch_31767864_1"
Prerequisites analysis summary:
-------------------------------
The following sub-patch(es) are applicable:
Featureset Sub-patches Log file
---------- ----------- --------
oracle.sysman.top.oms 31661020,31661036,31812958,31661157,31661194,31661066 31661020,31661036,31812958,31661157,31661194,31661066_opatch2020-09-28_11-19-24AM_1.log
The following sub-patches are incompatible with components installed in the OMS system:
31661186,31661124,31661089,30851102,31187567,31661173,31661078
....
7) Could not apply the patch "31661078" because the "oracle.sysman.emfa.oms.plugin with version 13.4.1.0.0" core component of the OMS or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
--------------------------------------------------------------------------------
OMSPatcher Session completed with warnings.
Log file location: /u01/app/oracle/middleware/cfgtoollogs/omspatcher/31767864/omspatcher_2020-09-28_11-19-25AM_analyze.log
OMSPatcher completed with warnings.
I received a couple of warnings regarding a few plugins that couldn’t be applied, but that’s ok. The next step was to shutdown the OMS:
[[email protected] ~]$ emctl stop oms
Oracle Enterprise Manager Cloud Control 13c Release 4
Copyright (c) 1996, 2020 Oracle Corporation. All rights reserved.
Stopping Oracle Management Server...
Oracle Management Server Successfully Stopped
Oracle Management Server is Down
JVMD Engine is Down
Finally I was ready to apply the patch (I have trimmed down the log below):
[[email protected] ~]$ omspatcher apply -property_file $HOME/working/antunez/PropertyFile.txt
OMSPatcher Automation Tool
Copyright (c) 2017, Oracle Corporation. All rights reserved.
OMSPatcher version : 13.9.4.2.0
OUI version : 13.9.4.0.0
Running from : /u01/app/oracle/middleware
Log file location : /u01/app/oracle/middleware/cfgtoollogs/omspatcher/opatch2020-09-28_11-29-51AM_1.log
OMSPatcher log file: /u01/app/oracle/middleware/cfgtoollogs/omspatcher/31767864/omspatcher_2020-09-28_11-29-58AM_deploy.log
...
Configuration Validation: Success
Running apply prerequisite checks for sub-patch(es) "31661020,31661036,31812958,31661157,31661194,31661066" and Oracle Home "/u01/app/oracle/middleware"...
Sub-patch(es) "31661020,31661036,31812958,31661157,31661194,31661066" are successfully analyzed for Oracle Home "/u01/app/oracle/middleware"
To continue, OMSPatcher will do the following:
[Patch and deploy artifacts] : Apply sub-patch(es) [ 31661020 31661036 31661066 31661157 31661194 31812958 ]
Apply RCU artifact with patch "/u01/app/oracle/middleware/.omspatcher_storage/31661020_Sep_8_2020_04_05_17/original_patch";
Apply RCU artifact with patch "/u01/app/oracle/middleware/.omspatcher_storage/31661036_Sep_8_2020_04_34_39/original_patch";
Apply RCU artifact with patch "/u01/app/oracle/middleware/.omspatcher_storage/31661157_Sep_8_2020_04_34_53/original_patch";
Apply RCU artifact with patch "/u01/app/oracle/middleware/.omspatcher_storage/31661194_Sep_8_2020_04_35_23/original_patch";
Apply RCU artifact with patch "/u01/app/oracle/middleware/.omspatcher_storage/31661066_Sep_8_2020_04_36_14/original_patch";
Apply RCU artifact with patch "/u01/app/oracle/middleware/.omspatcher_storage/31812958_Sep_8_2020_04_35_38/original_patch";
Register MRS artifact "commands";
Register MRS artifact "procedures";
Register MRS artifact "swlib";
Register MRS artifact "targetType";
Register MRS artifact "storeTargetType";
Register MRS artifact "default_collection";
Register MRS artifact "omsPropertyDef";
Register MRS artifact "jobTypes";
Register MRS artifact "systemStencil";
Register MRS artifact "gccompliance";
Register MRS artifact "discovery";
Register MRS artifact "CredstoreMetadata"
Do you want to proceed? [y|n]
y
User Responded with: Y
Applying sub-patch(es) "31661020,31661036,31661066,31661157,31661194,31812958"
Please monitor log file: /u01/app/oracle/middleware/cfgtoollogs/opatch/opatch2020-09-28_11-29-57AM_1.log
Updating repository with RCU reference file "/u01/app/oracle/middleware/.omspatcher_storage/31661020_Sep_8_2020_04_05_17/original_patch"
Updating repository with RCU reference file "/u01/app/oracle/middleware/.omspatcher_storage/31661036_Sep_8_2020_04_34_39/original_patch" for plugin home "/u01/app/oracle/middleware/plugins/oracle.sysman.emas.oms.plugin_13.4.1.0.0"
...
Complete Summary
================
All log file names referenced below can be accessed from the directory "/u01/app/oracle/middleware/cfgtoollogs/omspatcher/2020-09-28_11-29-51AM_SystemPatch_31767864_1"
Patching summary:
-----------------
Binaries of the following sub-patch(es) have been applied successfully:
Featureset Sub-patches Log file
---------- ----------- --------
oracle.sysman.top.oms_13.4.0.0.0 31661020,31661036,31661066,31661157,31661194,31812958 31661020,31661036,31661066,31661157,31661194,31812958_opatch2020-09-28_11-29-57AM_1.log
The following sub-patches are incompatible with components installed in the OMS system:
31661186,31661124,31661089,30851102,31187567,31661173,31661078
Deployment summary:
-------------------
The following artifact(s) have been successfully deployed:
Artifacts Log file
--------- --------
SQL rcu_applypatch_original_patch_2020-09-28_11-37-47AM.log
SQL rcu_applypatch_original_patch_2020-09-28_11-43-52AM.log
SQL rcu_applypatch_original_patch_2020-09-28_11-44-07AM.log
SQL rcu_applypatch_original_patch_2020-09-28_11-44-29AM.log
SQL rcu_applypatch_original_patch_2020-09-28_11-44-47AM.log
SQL rcu_applypatch_original_patch_2020-09-28_11-45-15AM.log
MRS-commands emctl_register_commands_2020-09-28_11-45-30AM.log
MRS-commands emctl_register_commands_2020-09-28_11-45-37AM.log
MRS-procedures emctl_register_procedures_2020-09-28_11-45-43AM.log
MRS-procedures emctl_register_procedures_2020-09-28_11-45-49AM.log
MRS-procedures emctl_register_procedures_2020-09-28_11-45-55AM.log
MRS-swlib emctl_register_swlib_2020-09-28_11-46-10AM.log
MRS-swlib emctl_register_swlib_2020-09-28_11-46-27AM.log
MRS-targetType emctl_register_targetType_2020-09-28_11-46-50AM.log
MRS-targetType emctl_register_targetType_2020-09-28_11-47-45AM.log
MRS-targetType emctl_register_targetType_2020-09-28_11-48-09AM.log
MRS-targetType emctl_register_targetType_2020-09-28_11-48-26AM.log
MRS-targetType emctl_register_targetType_2020-09-28_11-49-14AM.log
MRS-targetType emctl_register_targetType_2020-09-28_11-50-17AM.log
MRS-storeTargetType emctl_register_storeTargetType_2020-09-28_11-55-17AM.log
MRS-storeTargetType emctl_register_storeTargetType_2020-09-28_11-55-25AM.log
MRS-storeTargetType emctl_register_storeTargetType_2020-09-28_11-55-31AM.log
MRS-storeTargetType emctl_register_storeTargetType_2020-09-28_11-55-38AM.log
MRS-storeTargetType emctl_register_storeTargetType_2020-09-28_11-55-52AM.log
MRS-default_collection emctl_register_default_collection_2020-09-28_11-56-07AM.log
MRS-default_collection emctl_register_default_collection_2020-09-28_11-56-34AM.log
MRS-default_collection emctl_register_default_collection_2020-09-28_11-56-45AM.log
MRS-default_collection emctl_register_default_collection_2020-09-28_11-56-53AM.log
MRS-default_collection emctl_register_default_collection_2020-09-28_11-57-57AM.log
MRS-omsPropertyDef emctl_register_omsPropertyDef_2020-09-28_11-59-04AM.log
MRS-omsPropertyDef emctl_register_omsPropertyDef_2020-09-28_11-59-10AM.log
MRS-omsPropertyDef emctl_register_omsPropertyDef_2020-09-28_11-59-16AM.log
MRS-jobTypes emctl_register_jobTypes_2020-09-28_11-59-21AM.log
MRS-jobTypes emctl_register_jobTypes_2020-09-28_11-59-30AM.log
MRS-jobTypes emctl_register_jobTypes_2020-09-28_11-59-36AM.log
MRS-systemStencil emctl_register_systemStencil_2020-09-28_11-59-46AM.log
MRS-systemStencil emctl_register_systemStencil_2020-09-28_11-59-51AM.log
MRS-systemStencil emctl_register_systemStencil_2020-09-28_11-59-56AM.log
MRS-gccompliance emctl_register_gccompliance_2020-09-28_12-00-02PM.log
MRS-discovery emctl_register_discovery_2020-09-28_12-00-50PM.log
MRS-CredstoreMetadata emctl_register_CredstoreMetadata_2020-09-28_12-00-56PM.log
--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
...
7) Could not apply the patch "31661078" because the "oracle.sysman.emfa.oms.plugin with version 13.4.1.0.0" core component of the OMS or the plug-in for which the patch is intended is either not deployed or deployed with another version in your Enterprise Manager system.
--------------------------------------------------------------------------------
OMSPatcher Session completed with warnings.
Log file location: /u01/app/oracle/middleware/cfgtoollogs/omspatcher/31767864/omspatcher_2020-09-28_11-29-58AM_deploy.log
OMSPatcher completed with warnings.
Since I saw no errors in my log, I proceeded to start the OMS:
[[email protected] ~]$ emctl start oms
Oracle Enterprise Manager Cloud Control 13c Release 4
Copyright (c) 1996, 2020 Oracle Corporation. All rights reserved.
Starting Oracle Management Server...
WebTier Successfully Started
Oracle Management Server Successfully Started
Oracle Management Server is Up
JVMD Engine is Up
Starting BI Publisher Server ...
BI Publisher Server Already Started
BI Publisher Server is Up
Now that the OMS is up, I am running the 13.4.0.6 version of EM. I hope this simple blog post will help if you’re patching EM.
Note: This was originally published on rene-ace.com.
No comments