Apply PSU to OEM 12cR4
Below are the steps I followed for patching OMS for OEM 12c R4. I came across an issue with creating my property file. I give an example of what it should look like upon completion.
Creating the property file :
1. Run the following script to create the WebLogic encrypted configuration and key files.
Creating the property file :
1. Run the following script to create the WebLogic encrypted configuration and key files.
mkdir /app/oracle/Middleware/oms/oms_encr
<OMS_HOME>/OPatch/wlskeys/createkeys.sh –oh <full path of platform OMS Oracle Home> -location <location to put the encrypted files>
e.g. $OMS_HOME/OPatch/wlskeys/createkeys.sh -oh $OMS_HOME -location /app/oracle/Middleware/oms/oms_encr
Please enter weblogic admin server username: weblogic Please enter weblogic admin server password: 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: /app/oracle/Middleware/oms/oms_encr/config User key file created: /app/oracle/Middleware/oms/oms_encr/key 'createKeys' succeeded.
2. Create the property file with the following entries:
To retrieve the WebLogic Administrator Server URL details, run the following commands on the OMS home that you are patching: On Unix:$ $ORACLE_HOME/bin/emctl status oms -details
On Windows:%ORACLE_HOME%\bin\emctl.bat status oms -detailsThe output displayed contains the WebLogic Adminstrator Server details. Here is an example on how to construct the URL with these output details. Example:WLS Domain Information Domain Name : GCDomain Admin Server Host : oem12cr3.idc.oracle.com Admin Server HTTPS Port: 7103 To construct the Administrator Server URL, use the following syntax: t3s://<admin server host>:<port> In this example, the URL translates as follows: t3s://oem12cr3.idc.oracle.com:7103
Property file should look similar to the following once completed:
mkdir /app/oracle/Middleware/oms/filesvi property_file.txt cat property_file.txt
AdminServerURL=t3s://oemserver1.artisdba.com:7102 AdminConfigFile=/app/oracle/Middleware/oms/oms_encr/config AdminKeyFile=/app/oracle/Middleware/oms/oms_encr/key
Applying the PSU: 1. Run the following command on each OMS instance home to ensure that you do not have any issues with configuration and binary prerequisite checks: Please note: the OMS should be online when you do this step only.export ORACLE_HOME=$OMS_HOMEexport PATH=$ORACLE_HOME/OPatch:$ORACLE_HOME/bin:$PATH:cd <PATCH_TOP_DIR>/19218456 While Installing the System patch $ opatchauto apply -analyze [–property_file <location of property file>]e.g. opatchauto apply -analyze -property_file "/app/oracle/Middleware/oms/files/property_file.txt"
2. If this comes back without any issues, proceed with applying the PSU. If not, address the errors, then proceed with next steps.
cd <PATCH_TOP_DIR>/19218456/
emctl stop oms
Oracle Enterprise Manager Cloud Control 12c Release 4 Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved. Stopping WebTier... WebTier Successfully Stopped Stopping Oracle Management Server... Oracle Management Server Successfully Stopped Oracle Management Server is Down
opatchauto apply -property_file "/app/oracle/Middleware/oms/files/property_file.txt"
OPatch Automation Tool
Copyright (c) 2014, Oracle Corporation. All rights reserved.
OPatchauto version : 11.1.0.12.3
OUI version : 11.1.0.12.0
Running from : /app/oracle/Middleware/oms
Log file location : /app/oracle/Middleware/oms/cfgtoollogs/opatch/opatch2015-01-16_16-05-10PM_1.log
OPatchauto log file: /app/oracle/Middleware/oms/cfgtoollogs/opatchauto/19218456/opatch_oms_2015-01-16_16-05-11PM_deploy.log
Configuration Validation: Success
Running apply prerequisite checks for sub-patch(es) "19218456" and Oracle Home "/app/oracle/Middleware/oms"...
Please monitor OPatch log file: /app/oracle/Middleware/oms/cfgtoollogs/opatch/19218456_Jan_16_2015_16_05_10/ApplyPrereq2015-01-16_16-09-57PM_2.log
Sub-patch(es) "19218456" are successfully analyzed for Oracle Home "/app/oracle/Middleware/oms"
To continue, OPatchauto will do the following:
[Patch and deploy artifacts] : Apply sub-patch(es) [ 19218456 ] to Oracle Home "/app/oracle/Middleware/oms";
Apply RCU artifact with patch "/app/oracle/Middleware/oms/.patch_storage/19218456_Oct_14_2014_03_22_39/original_patch"
Do you want to proceed? [y|n]
y
User Responded with: Y
Applying sub-patch "19218456" to Oracle Home "/app/oracle/Middleware/oms"...
Please monitor OPatch log file: /app/oracle/Middleware/oms/cfgtoollogs/opatch/19218456_Jan_16_2015_16_05_10/apply2015-01-16_16-13-27PM_4.log
Updating repository with RCU reference file "/app/oracle/Middleware/oms/.patch_storage/19218456_Oct_14_2014_03_22_39/original_patch"
Complete Summary
================
All log file names referenced below can be accessed from the directory "/app/oracle/Middleware/oms/cfgtoollogs/opatch/2015-01-16_16-05-10PM_SystemPatch_19218456_1"
Patching summary:
-----------------
Binaries of the following sub-patch(es) have been applied successfully:
Oracle Home Name Sub-patches Log file
---------------- ----------- --------
oms12c1 19218456 19218456_apply2015-01-16_16-13-27PM_4.log
Deployment summary:
-------------------
The following artifact(s) have been successfully deployed:
Artifacts Log file
--------- --------
SQL rcu_applypatch_original_patch_2015-01-16_16-14-33PM.log
Log file location: /app/oracle/Middleware/oms/cfgtoollogs/opatchauto/19218456/opatch_oms_2015-01-16_16-05-11PM_deploy.log
OPatchauto succeeded.
emctl start oms
Oracle Enterprise Manager Cloud Control 12c Release 4 Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved. Starting Oracle Management Server... Starting WebTier... WebTier Successfully Started Oracle Management Server Successfully Started Oracle Management Server is Up
Comments