NOTE: Beginning with this PSU, the fifth
digit version number has changed to a new format YYMMDD. For more information,
see My Oracle Support Note 2061926.1 - "Oracle Database, Enterprise
Manager and Middleware - Change to Patch Numbering from Nov 2015 on wards"
OMS : Standalone server on RHEL 7
Make sure we set the PATH
environment variables and I downloaded patch to directory /opt/oracle/CB/PSU_JULY_OMS/23134365
[oracle@OMSHOST6 OPatch]$ echo
$OMS_HOME
/opt/oracle/product/middleware/oms
[oracle@OMSHOST6 ~]$ export
ORACLE_HOME=/opt/oracle/product/middleware/oms
[oracle@OMSHOST6 ~]$ export PATH=$ORACLE_HOME/OMSPatcher:$PATH
[oracle@OMSHOST6 ~]$ export PATH=$ORACLE_HOME/bin:$PATH
OMSPatcher is a new feature of EM 13c to apply patches to OMS home.
To use the OMSPatcher functionality, you must set the WebLogic
Administration Server credential access. If you do not want to set the
credentials every time you are prompted while patching the OMS, you can update
the property file
Applying patch to OMS can be done in two ways:
1. Applying patch
without using property file
2. Applying patch using
property file (I’m using this option)
Creating property file:
[oracle@OMSHOST6 ]$ mkdir -p /opt/oracle/product/middleware/oms/OMSPatcher/property_file
[oracle@OMSHOST6 ]$ cd $OMS_HOME/OMSPatcher/wlskeys
[oracle@OMSHOST6 wlskeys]$ ./createkeys.sh –oh /opt/oracle/product/middleware/oms -location
/opt/oracle/product/middleware/oms/OMSPatcher/property_file
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:
/opt/oracle/product/middleware/oms/OMSPatcher/property_file/config
User key file created:
/opt/oracle/product/middleware/oms/OMSPatcher/property_file/key
'createkeys'
succeeded.
[oracle@OMSHOST6 wlskeys]$ cd
/opt/oracle/product/middleware/oms/OMSPatcher/property_file
[oracle@OMSHOST6 property_file]$ ll
total 8
-rw-r--r--. 1 oracle dba 227 Oct
6 15:38 config
-rw-r--r--. 1 oracle dba 64
Oct 6 15:37 key
[oracle@OMSHOST6 ~]$ cd /opt/oracle/CB/PSU_JULY_OMS/23134365
[oracle@OMSHOST6 23134365]$ omspatcher
apply –analyze –property_file
/opt/oracle/product/middleware/oms/OMSPatcher/property_file
OMSPatcher Automation Tool
Copyright (c) 2015, Oracle Corporation.
All rights reserved.
Syntax Error...
Unrecognized Option for Apply
Please refer 'omspatcher apply -help' for details
OMSPatcher failed with error code 14
[oracle@OMSHOST6 23134365]$ omspatcher apply –property_file /opt/oracle/product/middleware/oms/OMSPatcher/property_file –analyze
OMSPatcher Automation Tool
Copyright (c) 2015, Oracle Corporation.
All rights reserved.
Syntax Error...
Unrecognized Option for Apply
Please refer 'omspatcher apply -help' for details
OMSPatcher failed with error code 14
Tried
many different ways…………but still same error then I thought that this is the
command copied from oracle support read me file so instead of that I typed the entire
command manually then it worked…! Damn….
never copy as is from oracle DOC (Lesson learned J)
[oracle@OMSHOST6 23134365]$ omspatcher
apply -analyze -property_file
/opt/oracle/product/middleware/oms/OMSPatcher/property_file
OMSPatcher Automation Tool
Copyright (c) 2015, Oracle Corporation.
All rights reserved.
OMSPatcher version : 13.6.0.0.1
OUI version : 13.6.0.0.0
Running from :
/opt/oracle/product/middleware/oms
Log file location :
/opt/oracle/product/middleware/oms/cfgtoollogs/omspatcher/opatch2016-10-06_16-03-24PM_1.log
OMSPatcher log file: /opt/oracle/product/middleware/oms/cfgtoollogs/omspatcher/23134365/omspatcher_2016-10-06_16-03-30PM_analyze.log
Please enter OMS weblogic admin server URL(t3s://OMSHOST6.domain.com:7102):>
enter
Please enter OMS weblogic admin server username(weblogic):> enter
Please enter OMS weblogic admin server password:>
Configuration Validation: Success
Running apply prerequisite checks for sub-patch(es) "23134365"
and Oracle Home "/opt/oracle/product/middleware/oms"...
Sub-patch(es) "23134365" are successfully analyzed for Oracle
Home "/opt/oracle/product/middleware/oms"
Complete Summary
================
All log file names referenced below can be accessed from the directory
"/opt/oracle/product/middleware/oms/cfgtoollogs/omspatcher/2016-10-06_16-03-24PM_SystemPatch_23134365_1"
Prerequisites analysis summary:
-------------------------------
The following sub-patch(es) are applicable:
Featureset Sub-patches Log
file
---------- -----------
--------
oracle.sysman.top.oms 23134365
23134365_ApplyPrereq2016-10-06_16-04-12PM_2.log
Log file location:
/opt/oracle/product/middleware/oms/cfgtoollogs/omspatcher/23134365/omspatcher_2016-10-06_16-03-30PM_analyze.log
OMSPatcher succeeded.
[oracle@OMSHOST6 23134365]$ cd /opt/oracle/product/middleware/oms/bin
[oracle@OMSHOST6 bin]$ ./emctl
status oms
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
WebTier is Up
Oracle Management Server is Up
JVMD Engine is Up
BI Publisher Server is Up
[oracle@OMSHOST6 bin]$ ./emctl
stop oms
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
Stopping Oracle Management Server...
Oracle Management Server Successfully Stopped
Oracle Management Server is Down
JVMD Engine is Down
[oracle@OMSHOST6 bin]$ ./emctl
status oms
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
WebTier is Up
Oracle Management
Server is Down
JVMD Engine is Down
BI Publisher Server is Up
[oracle@OMSHOST6
23134365]$ omspatcher apply
-property_file /opt/oracle/product/middleware/oms/OMSPatcher/property_file
OMSPatcher
Automation Tool
Copyright (c)
2015, Oracle Corporation. All rights
reserved.
OMSPatcher version
: 13.6.0.0.1
OUI version : 13.6.0.0.0
Running from : /opt/oracle/product/middleware/oms
Log file
location :
/opt/oracle/product/middleware/oms/cfgtoollogs/omspatcher/opatch2016-10-06_16-10-56PM_1.log
OMSPatcher log
file: /opt/oracle/product/middleware/oms/cfgtoollogs/omspatcher/23134365/omspatcher_2016-10-06_16-11-02PM_deploy.log
Please enter OMS
weblogic admin server URL(t3s://OMSHOST6.domain.com:7102):>
Please enter OMS
weblogic admin server username(weblogic):>
Please enter OMS
weblogic admin server password:>
Configuration Validation:
Success
Running apply
prerequisite checks for sub-patch(es) "23134365" and Oracle Home
"/opt/oracle/product/middleware/oms"...
Sub-patch(es)
"23134365" are successfully analyzed for Oracle Home
"/opt/oracle/product/middleware/oms"
To continue, OMSPatcher
will do the following:
[Patch and deploy
artifacts] : Apply sub-patch(es) [
23134365 ] to component "oracle.sysman.top.oms" and version
"13.1.0.0.0";
Apply RCU
artifact with patch "/opt/oracle/product/middleware/oms/.omspatcher_storage/23134365_Jul_4_2016_05_05_46/original_patch";
Register MRS
artifact "targetType";
Register MRS
artifact "storeTargetType";
Register MRS
artifact "default_collection"
Do you want to
proceed? [y|n]
y
User Responded
with: Y
Applying sub-patch
"23134365 " to component "oracle.sysman.top.oms" and
version "13.1.0.0.0"...
Updating
repository with RCU reference file
"/opt/oracle/product/middleware/oms/.omspatcher_storage/23134365_Jul_4_2016_05_05_46/original_patch"
Registering
service "targetType" with register file
"/opt/oracle/product/middleware/oms/sysman/metadata/targetType/oldVersions/host/12.1.0.5/host.xml"...
Registering
service "storeTargetType" with register file
"/opt/oracle/product/middleware/oms/sysman/metadata/targetType/oldVersions/host/12.1.0.5/host.xml"...
Registering
service "default_collection" with register file
"/opt/oracle/product/middleware/oms/sysman/metadata/default_collection/oldVersions/host/12.1.0.5/host.xml"...
Complete Summary
================
All log file names
referenced below can be accessed from the directory
"/opt/oracle/product/middleware/oms/cfgtoollogs/omspatcher/2016-10-06_16-10-56PM_SystemPatch_23134365_1"
Patching summary:
-----------------
Binaries of the
following sub-patch(es) have been applied successfully:
Featureset Sub-patches Log file
---------- ----------- --------
oracle.sysman.top.oms_13.1.0.0.0 23134365
23134365_opatch2016-10-06_16-11-35PM_3.log
Deployment
summary:
-------------------
The following
artifact(s) have been successfully deployed:
Artifacts
Log file
---------
--------
SQL
rcu_applypatch_original_patch_2016-10-06_16-12-39PM.log
MRS-targetType
emctl_register_targetType_2016-10-06_16-21-39PM.log
MRS-storeTargetType
emctl_register_storeTargetType_2016-10-06_16-22-12PM.log
MRS-default_collection
emctl_register_default_collection_2016-10-06_16-22-21PM.log
Log file location:
/opt/oracle/product/middleware/oms/cfgtoollogs/omspatcher/23134365/omspatcher_2016-10-06_16-11-02PM_deploy.log
OMSPatcher succeeded.
[oracle@OMSHOST6 bin]$ ./emctl start
oms
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 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
[oracle@OMSHOST6 bin]$ ./emctl
status oms
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
WebTier is Up
Oracle Management Server is Up
JVMD Engine is Up
BI Publisher Server is Up
Refer Oracle doc:
Patch Set Update 13.1.0.0.160719 for Oracle
Management Service (Doc ID 2158215.1)
0 comments:
Post a Comment