Patching OEM 13c Cloud Control Release 2
Some days ago, Oracle released a new bundle for Oracle Enterprise Manager 13.2 (Patch# 25990918). This was the reason for me to update my local test and play OEM system on my local Linux system.
Installing patches for OEM became much easier when Oracle introduced the tool “OMSPatcher”. OMSPatcher is based on OPatch. Before installing the bundle patch for OEM we have to upgrade both OMSPatcher on OPatch to the current release.
So we need 3 patches:
- Patch 25990918: enterprise manager for oms plugins 13.2.2.0.170531
- Patch 19999993: OMSPatcher patch of version 13.8.0.0.2 for Enterprise Manager Cloud Control 13.2.0.0.0
- Patch 6880880: OPatch version 13.9.1.3.0 (Reuploaded with fix for -silent mode) for Oracle Homes with OUI version 13.6.x and higher
oracle@tvdserver:/u00/app/oracle/stage/oempatch/ [EMREP] ll total 389372 drwxr-xr-x. 2 oracle oinstall 4096 Jun 15 14:52 . drwxrwxr-x. 6 grid oinstall 4096 Jun 15 14:52 .. -rw-r--r--. 1 oracle oinstall 731343 Jun 15 14:46 p19999993_132000_Generic.zip -rw-r--r--. 1 oracle oinstall 354118513 Jun 15 14:46 p25990918_132000_Generic.zip -rw-r--r--. 1 oracle oinstall 43854527 Jun 15 14:46 p6880880_139000_Generic.zip
There’s an additional patch for the agent which was released on the same date, but the installation of this patch is not covered in this post:
- Patch 25924717: EM-AGENT Bundle Patch 13.2.0.0.170531
Step 0: Backup the current OEM installation
Step 1: Update OPatch
We’ll update OPatch in the OMS home and the agent home (OK, updating OPatch in the agent home is not required for installing the OMS patch, but it’s a good opportunity to update this component, too).
oracle@tvdserver:/u00/app/oracle/stage/oempatch/ [emagent13c] cd 6880880/ /u00/app/oracle/stage/oempatch/6880880 oracle@tvdserver:/u00/app/oracle/stage/oempatch/6880880/ [emagent13c] echo $ORACLE_HOME /u00/app/oracle/product/agent13cr2/agent_13.2.0.0.0 oracle@tvdserver:/u00/app/oracle/stage/oempatch/6880880/ [emagent13c] $ORACLE_HOME/jdk/bin/java -jar opatch_generic.jar -silent oracle_home=$ORACLE_HOME
Updating OPatch in the agent home did not work for me in the first attempt. There was an error message:
WARNING:This install was unsuccessful because: java.io.FileNotFoundException: The file specified did not exist /u00/app/oracle/product/agent13cr2/agent_13.2.0.0.0/inventory/Components/oracle.eons.client/11.2.0.2.0/compDef.xml Would you like to end this session now? The operation has been resumed.
You’ll find the reason in MOS note 2247800.1, which contains a workaround:
- Download oracle.eons.client.zip from this Document attachment.
- On the agent host Extract it under <AGENT_BASE_DIR>/agent_13.2.0.0.0/inventory/Components/
- Ensure you have drwxr—– permissions for oracle.eons.client directory.
- Restart the agent
- Retry the plugin deploy or opatch operations, which should now work fine.
So:
- Download oracle.eons.client.zip & transfer the file to your OEM server
- Unzip
oracle@tvdserver:/u00/app/oracle/stage/oempatch/ [emagent13c] cd $ORACLE_HOME oracle@tvdserver:/u00/app/oracle/product/agent13cr2/agent_13.2.0.0.0/ [emagent13c] cd inventory/Components/ /u00/app/oracle/product/agent13cr2/agent_13.2.0.0.0/inventory/Components oracle@tvdserver:/u00/app/oracle/product/agent13cr2/agent_13.2.0.0.0/inventory/Components/ [emagent13c] unzip /u00/app/oracle/stage/oempatch/oracle.eons.client.zip Archive: /u00/app/oracle/stage/oempatch/oracle.eons.client.zip creating: oracle.eons.client/ creating: oracle.eons.client/11.2.0.2.0/ inflating: oracle.eons.client/11.2.0.2.0/compDef.xml creating: oracle.eons.client/11.2.0.2.0/resources/ inflating: oracle.eons.client/11.2.0.2.0/resources/CompID.properties
Try the update of OPatch in the agent home again:
oracle@tvdserver:/u00/app/oracle/stage/oempatch/6880880/ [emagent13c] echo $ORACLE_HOME /u00/app/oracle/product/agent13cr2/agent_13.2.0.0.0 oracle@tvdserver:/u00/app/oracle/stage/oempatch/6880880/ [emagent13c] $ORACLE_HOME/jdk/bin/java -jar opatch_generic.jar -silent oracle_home=$ORACLE_HOME Launcher log file is /tmp/OraInstall2017-06-15_03-09-08PM/launcher2017-06-15_03-09-08PM.log. Extracting the installer . . . . Done Checking if CPU speed is above 300 MHz. Actual 933.000 MHz Passed Checking swap space: must be greater than 512 MB. Actual 36859 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 41678 MB Passed Preparing to launch the Oracle Universal Installer from /tmp/OraInstall2017-06-15_03-09-08PM All of feature sets selected for installation and their components have already been installed for the distribution OPatch 13.9.1.3.0 in the home directory /u00/app/oracle/product/agent13cr2/agent_13.2.0.0.0 The log(s) can be found here: /tmp/OraInstall2017-06-15_03-09-08PM.
Update OPatch in the OMS home afterwards (without any issues):
oracle@tvdserver:/u00/app/oracle/stage/oempatch/6880880/ [oms13c] $ORACLE_HOME/oracle_common/jdk/bin/java -jar opatch_generic.jar -silent oracle_home=$ORACLE_HOMEoracle@tvdserver:/u00/app/oracle/stage/oempatch/6880880/ [oms13c] $ORACLE_HOME/oracle_common/jdk/bin/java -jar opatch_generic.jar -silent oracle_home=$ORACLE_HOMELauncher log file is /tmp/OraInstall2017-06-15_03-12-09PM/launcher2017-06-15_03-12-09PM.log.Extracting the installer . . . . DoneChecking if CPU speed is above 300 MHz. Actual 1466.000 MHz PassedChecking swap space: must be greater than 512 MB. Actual 36859 MB PassedChecking 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 41603 MB Passed Preparing to launch the Oracle Universal Installer from /tmp/OraInstall2017-06-15_03-12-09PMInstallation Summary Disk Space : Required 26 MB, Available 282,823 MBFeature Sets to Install: Next Generation Install Core 13.9.1.0.1 OPatch 13.9.1.3.0 OPatch Auto OPlan 13.9.1.0.0Session log file is /tmp/OraInstall2017-06-15_03-12-09PM/install2017-06-15_03-12-09PM.log Loading products list. Please wait. 1%[..]Setup successful Save inventory pending Saving inventory[..] S_COMP_INPROGRESS_SAVE_INVENTORYLogs successfully copied to /oracle/u00/app/oraInventory/logs.
Step 2: Update OMSPatcher
oracle@tvdserver:/u00/app/oracle/product/em13cr2/middleware/ [oms13c] mv OMSPatcher OMSPatcher.Backup.20170615 oracle@tvdserver:/u00/app/oracle/product/em13cr2/middleware/ [oms13c] unzip /u00/app/oracle/stage/oempatch/p19999993_132000_Generic.zip Archive: /u00/app/oracle/stage/oempatch/p19999993_132000_Generic.zip creating: OMSPatcher/ inflating: OMSPatcher/omspatcher.bat creating: OMSPatcher/jlib/ inflating: OMSPatcher/jlib/omspatcher.jar inflating: OMSPatcher/jlib/oracle.omspatcher.classpath.jar inflating: OMSPatcher/jlib/oracle.omspatcher.classpath.unix.jar inflating: OMSPatcher/jlib/oracle.omspatcher.classpath.windows.jar creating: OMSPatcher/scripts/ creating: OMSPatcher/scripts/oms/ creating: OMSPatcher/scripts/oms/oms_child_scripts/ inflating: OMSPatcher/scripts/oms/oms_child_scripts/omspatcher_jvm_discovery inflating: OMSPatcher/scripts/oms/oms_child_scripts/omspatcher_jvm_discovery.bat inflating: OMSPatcher/scripts/oms/oms_child_scripts/omspatcher_wls inflating: OMSPatcher/scripts/oms/oms_child_scripts/omspatcher_wls.bat inflating: OMSPatcher/scripts/oms/omspatcher inflating: OMSPatcher/scripts/oms/omspatcher.bat creating: OMSPatcher/wlskeys/ inflating: OMSPatcher/wlskeys/createkeys.cmd inflating: OMSPatcher/wlskeys/createkeys.sh creating: OMSPatcher/oms/ inflating: OMSPatcher/oms/generateMultiOMSPatchingScripts.pl inflating: OMSPatcher/omspatcher replace readme.txt? [y]es, [n]o, [A]ll, [N]one, [r]ename: A inflating: readme.txt inflating: PatchSearch.xml
Unzip writes two files, readme.txt and PatchSearch.xml into the Oracle-Home directory. From my point of view, we can remove these files:
oracle@tvdserver:/u00/app/oracle/product/em13cr2/middleware/ [oms13c] rm readme.txt oracle@tvdserver:/u00/app/oracle/product/em13cr2/middleware/ [oms13c] rm PatchSearch.xml
Step 3: Update OMS with the bundle patch 25990918
Preparation:
- Create keys:
oracle@tvdserver:/u00/app/oracle/stage/oempatch/ [oms13c] $ORACLE_HOME/OMSPatcher/wlskeys/createkeys.sh -oh $ORACLE_HOME -location /u00/app/oracle/stage/oempatch/ Please enter weblogic admin server username: weblogic Please enter weblogic admin server password: Warning: weblogic.Admin is deprecated and will be removed in a future release. WLST should be used instead of weblogic.Admin. 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... Trying to get configuration and key files for the given inputs... This operation will take some time. Please wait for updates... User configuration file created: /u00/app/oracle/stage/oempatch/config User key file created: /u00/app/oracle/stage/oempatch/key 'createkeys' succeeded.
2. Create property file
AdminServerURL=t3s://<host address from where admin server is running>:<port of the admin server> AdminConfigFile=<'config' file location> AdminKeyFile=<'key' file location>
In my case the file looks like:
oracle@tvdserver:/u00/app/oracle/stage/oempatch/ [oms13c] cat property.txt AdminServerURL=t3s://tvdserver:7102 AdminConfigFile=/u00/app/oracle/stage/oempatch/config AdminKeyFile=/u00/app/oracle/stage/oempatch/key
3. Unzip the patch
oracle@tvdserver:/u00/app/oracle/stage/oempatch/ [oms13c] unzip p25990918_132000_Generic.zip
4. Stop OMS
oracle@tvdserver:/u00/app/oracle/stage/oempatch/ [oms13c] emctl stop oms Oracle Enterprise Manager Cloud Control 13c Release 2 Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved. Stopping Oracle Management Server... Oracle Management Server Successfully Stopped Oracle Management Server is Down JVMD Engine is Down
5. Install the patch
oracle@tvdserver:/u00/app/oracle/stage/oempatch/ [oms13c] cd 25990918/ /u00/app/oracle/stage/oempatch/25990918 $ORACLE_HOME/OMSPatcher/omspatcher apply -property_file /u00/app/oracle/stage/oempatch/property.txt
OMSPatcher Automation Tool Copyright (c) 2017, Oracle Corporation. All rights reserved. OMSPatcher version : 13.8.0.0.2 OUI version : 13.9.1.0.0 Running from : /u00/app/oracle/product/em13cr2/middleware Log file location : /u00/app/oracle/product/em13cr2/middleware/cfgtoollogs/omspatcher/opatch2017-06-15_15-38-37PM_1.log OMSPatcher log file: /u00/app/oracle/product/em13cr2/middleware/cfgtoollogs/omspatcher/25990918/omspatcher_2017-06-15_15-38-51PM_deploy.log WARNING: Could not apply the patch "25897138" because the "oracle.sysman.xa.oms.plugin with version 13.2.2.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. WARNING: Could not apply the patch "25897243" because the "oracle.sysman.csm.oms.plugin with version 13.2.2.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. WARNING: Could not apply the patch "25897182" because the "oracle.sysman.emas.oms.plugin with version 13.2.2.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. WARNING: Could not apply the patch "25897233" because the "oracle.sysman.ssa.oms.plugin with version 13.2.2.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. WARNING: Could not apply the patch "25931767" because the "oracle.sysman.empa.oms.plugin with version 13.2.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. WARNING: Could not apply the patch "25897169" because the "oracle.sysman.vi.oms.plugin with version 13.2.2.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. WARNING: Could not apply the patch "25897123" because the "oracle.sysman.emfa.oms.plugin with version 13.2.2.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. Configuration Validation: Success Running apply prerequisite checks for sub-patch(es) "25897221,25897259" and Oracle Home "/u00/app/oracle/product/em13cr2/middleware"... Sub-patch(es) "25897221,25897259" are successfully analyzed for Oracle Home "/u00/app/oracle/product/em13cr2/middleware" To continue, OMSPatcher will do the following: [Patch and deploy artifacts] : Apply sub-patch(es) [ 25897221 25897259 ] Apply RCU artifact with patch "/u00/app/oracle/product/em13cr2/middleware/.omspatcher_storage/25897221_Jun_6_2017_02_56_40/original_patch"; Register MRS artifact "default_collection"; Register MRS artifact "targetType"; Register MRS artifact "storeTargetType"; Register MRS artifact "systemStencil"; Register MRS artifact "omsPropertyDef" Do you want to proceed? [y|n] y User Responded with: Y Applying sub-patch(es) "25897221,25897259" Please monitor log file: /u00/app/oracle/product/em13cr2/middleware/cfgtoollogs/opatch/opatch2017-06-15_15-38-50PM_1.log [..] Registering service "omsPropertyDef" with register file "/u00/app/oracle/product/em13cr2/middleware/plugins/oracle.sysman.db.oms.plugin_13.2.2.0.0/metadata/omsProperties/definition/DBPropDefinition.xml" for plugin id as "oracle.sysman.db"... Please monitor log file: /u00/app/oracle/product/em13cr2/middleware/cfgtoollogs/omspatcher/2017-06-15_15-38-37PM_SystemPatch_25990918_1/emctl_register_omsPropertyDef_2017-06-15_15-55-56PM.log Complete Summary ================ All log file names referenced below can be accessed from the directory "/u00/app/oracle/product/em13cr2/middleware/cfgtoollogs/omspatcher/2017-06-15_15-38-37PM_SystemPatch_25990918_1" Patching summary: ----------------- Binaries of the following sub-patch(es) have been applied successfully: Featureset Sub-patches Log file ---------- ----------- -------- oracle.sysman.top.oms_13.2.0.0.0 25897221,25897259 25897221,25897259_opatch2017-06-15_15-38-50PM_1.log The following sub-patches are incompatible with components installed in the OMS system: 25897138,25897243,25897182,25897233,25931767,25897169,25897123 Deployment summary: ------------------- The following artifact(s) have been successfully deployed: Artifacts Log file --------- -------- SQL rcu_applypatch_original_patch_2017-06-15_15-42-23PM.log MRS-default_collection emctl_register_default_collection_2017-06-15_15-42-39PM.log MRS-default_collection emctl_register_default_collection_2017-06-15_15-43-07PM.log MRS-default_collection emctl_register_default_collection_2017-06-15_15-43-34PM.log MRS-default_collection emctl_register_default_collection_2017-06-15_15-43-51PM.log MRS-default_collection emctl_register_default_collection_2017-06-15_15-44-03PM.log MRS-default_collection emctl_register_default_collection_2017-06-15_15-44-19PM.log MRS-targetType emctl_register_targetType_2017-06-15_15-44-35PM.log MRS-targetType emctl_register_targetType_2017-06-15_15-46-53PM.log MRS-targetType emctl_register_targetType_2017-06-15_15-48-29PM.log MRS-targetType emctl_register_targetType_2017-06-15_15-50-22PM.log MRS-targetType emctl_register_targetType_2017-06-15_15-51-44PM.log MRS-targetType emctl_register_targetType_2017-06-15_15-52-40PM.log MRS-storeTargetType emctl_register_storeTargetType_2017-06-15_15-53-51PM.log MRS-storeTargetType emctl_register_storeTargetType_2017-06-15_15-54-05PM.log MRS-storeTargetType emctl_register_storeTargetType_2017-06-15_15-54-23PM.log MRS-storeTargetType emctl_register_storeTargetType_2017-06-15_15-54-42PM.log MRS-storeTargetType emctl_register_storeTargetType_2017-06-15_15-54-58PM.log MRS-storeTargetType emctl_register_storeTargetType_2017-06-15_15-55-12PM.log MRS-systemStencil emctl_register_systemStencil_2017-06-15_15-55-27PM.log MRS-systemStencil emctl_register_systemStencil_2017-06-15_15-55-37PM.log MRS-systemStencil emctl_register_systemStencil_2017-06-15_15-55-46PM.log MRS-omsPropertyDef emctl_register_omsPropertyDef_2017-06-15_15-55-56PM.log -------------------------------------------------------------------------------- The following warnings have occurred during OPatch execution: 1) Could not apply the patch "25897138" because the "oracle.sysman.xa.oms.plugin with version 13.2.2.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. 2) Could not apply the patch "25897243" because the "oracle.sysman.csm.oms.plugin with version 13.2.2.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. 3) Could not apply the patch "25897182" because the "oracle.sysman.emas.oms.plugin with version 13.2.2.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. 4) Could not apply the patch "25897233" because the "oracle.sysman.ssa.oms.plugin with version 13.2.2.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. 5) Could not apply the patch "25931767" because the "oracle.sysman.empa.oms.plugin with version 13.2.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. 6) Could not apply the patch "25897169" because the "oracle.sysman.vi.oms.plugin with version 13.2.2.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. 7) Could not apply the patch "25897123" because the "oracle.sysman.emfa.oms.plugin with version 13.2.2.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: /u00/app/oracle/product/em13cr2/middleware/cfgtoollogs/omspatcher/25990918/omspatcher_2017-06-15_15-38-51PM_deploy.log OMSPatcher completed with warnings.
According to MOS note 2197224.1 you can ignore the warnings.
6. Restart OMS
oracle@tvdserver:/u00/app/oracle/stage/oempatch/25990918/ [oms13c] emctl start oms Oracle Enterprise Manager Cloud Control 13c Release 2 Copyright (c) 1996, 2016 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 oracle@tvdserver:/u00/app/oracle/stage/oempatch/25990918/ [oms13c]
That’s it.
Required Patches and Files:
- Patch 25990918: enterprise manager for oms plugins 13.2.2.0.170531
- Patch 19999993: OMSPatcher patch of version 13.8.0.0.2 for Enterprise Manager Cloud Control 13.2.0.0.0
- Patch 6880880: OPatch version 13.9.1.3.0 (Reuploaded with fix for -silent mode) for Oracle Homes with OUI version 13.6.x and higher
- Zip-file from MOS note 2247800.1
Helpful Support-Notes
- Enterprise Manager 13.2 Master Bundle Patch List (Doc ID 2219797.1)
- How to upgrade the Enterprise Manager 13.2 Cloud Control OMSPatcher to the Latest Version (Doc ID 2203007.1)
- Deploying plug-in or opatch opeerations on 13.2 Agent reports java.io.FileNotFoundException: The file specified did not exist ../agent_13.2.0.0.0/inventory/Components/oracle.eons.client/11.2.0.2.0/compDef.xml (Doc ID 2247800.1)
- EM 13c: Enterprise Manager 13c Cloud Control Patch Warning: 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 (Doc ID 2197224.1)
Links:
Ad (Amazon Link):