<<Back to Oracle RAC Main Page
Step by Step Instruction to Patch Oracle RAC Cluster Version 12.1.0.2
Step0: download the PSU and read the readme.txt for the patch. The installation instruction and rollback instruction is provided in readme file.
Transfer the PSU on each node of the RAC cluster.
Here is the extract and simplified version of Oracle RAC patching procedure for release version 12.1.0.2 using opatchauto
Step1: Ensure the Latest OPatch utility is Available
Check Current OPatch Utility Version
Verify if the required OPatch utility as mentioned in readme.txt is available.
$export ORACLE_HOME=/u01/product/12.1.0.2/dbhome1
$export PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/OPatch
$opatch version
OPatch Version: 12.2.0.1.3
OPatch succeeded.
$export PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/OPatch
$opatch version
OPatch Version: 12.2.0.1.3
OPatch succeeded.
Upgrade OPatch Utility to The Latest Version
Download the latest OPatch utility version as mentioned in readme.txt. Ensure to upgrade the OPatch utility in all OH homes and GI home on all nodes. Latest OPatch utility for your version is available for Download from My Oracle Support patch 6880880.
To Upgrade the OPatch follow below steps for each OH and GI homes
- Download and transfer the OPatch utility file to all the server (I copied it in /u01/stage)
- $unzip /u01/stage/p28199085_12102190716_Linux-x86-64.zip
- #mv $ORACLE_HOME/OPatch $ORACLE_HOME/OPatch_Backup
- # cp /u01/stage/OPatch $ORACLE_HOME/
- #chown -R oracle:dba $ORACLE_HOME/OPatch
- #chmod -R 755 $ORACLE_HOME/OPatch
- #opatch version
OPatch Version: 12.2.0.1.17
OPatch succeeded.
Step2: Perform Complete Cluster Stack Health Check: Strongly Recommended
Download latest ORACheck utility install it and run it to perform the cluster health check. You can find the instruction guide, download package etc at MOS Note 1268927.2
If you have latest version of TFA installed and configured ORACheck is part of TFA and already installed in your environment.You can run racheck directly from tfa CLI interface as below
$tfactl
tfactl> orachk
CRS stack is running and CRS_HOME is not set. Do you want to set CRS_HOME to /u01/grid/product/12.1.0.2/gi?[y/n][y]
Follow the screen instruction to and wait for completion of ORACheck execution.
Analyze the output file and fix any possible errors before proceeding to next step
If you have latest version of TFA installed and configured ORACheck is part of TFA and already installed in your environment.You can run racheck directly from tfa CLI interface as below
$tfactl
tfactl> orachk
CRS stack is running and CRS_HOME is not set. Do you want to set CRS_HOME to /u01/grid/product/12.1.0.2/gi?[y/n][y]
Follow the screen instruction to and wait for completion of ORACheck execution.
Analyze the output file and fix any possible errors before proceeding to next step
Step3: Prepare the Node for Patching
NOTE: Since the patching is done in rolling mode to avoid any outage for application, ensure the database and services is always available from available node in the cluster
Verify the Database Services Running on Node1
$srvctl status service -d DB1
Service srv1 is running on instance(s) DB11,DB12
$srvctl status service -d DB2
Service srv2 is running on instance(s) DB21,DB22
$srvctl status service -d DB1
Service srv1 is running on instance(s) DB11,DB12
$srvctl status service -d DB2
Service srv2 is running on instance(s) DB21,DB22
Stop or relocate the services from the node1 to node2
NOTE: In production environment run this step at least few hours before starting the patching to ensure that all the sessions are properly gone from node1. In my case, since the services are running on all the nodes I will simply stop them on node1 (the node which I am going to patch first)
$srvctl stop service -d DB1 -s srv1 -n node1
$srvctl stop service -d DB2 -s srv2 -n node1
Verify and Confirm that All the Services are now running on 2nd node and no service is running on node1
$srvctl status service -d DB1
Service srv1 is running on instance(s) DB21
$srvctl status service -d DB2
Service srv2 is running on instance(s) DB22
$srvctl status service -d DB1
Service srv1 is running on instance(s) DB21
$srvctl status service -d DB2
Service srv2 is running on instance(s) DB22
Verify and Ensure that there is no Active Session and Transactions Running on Node1
$ sqlplus "/as sysdba"
select SID,USERNAME,STATUS from v$session where username not in ('SYS','DBSNMP');
select SID,USERNAME,STATUS from v$session where username not in ('SYS','DBSNMP');
no rows selected
col machine for a30
col username for a30
col program for a30 trun
col sid for 99999
set lines 300select sid,USED_UBLK,username,program,machine,systimestamp
col username for a30
col program for a30 trun
col sid for 99999
set lines 300select sid,USED_UBLK,username,program,machine,systimestamp
from v$transaction t, v$session s
where SES_ADDR = s.saddr order by 1;
no rows selected
select sid,USED_UBLK,username,program,machine,systimestamp
from gv$transaction t, gv$session s
where SES_ADDR = s.saddr order by 1;
from gv$transaction t, gv$session s
where SES_ADDR = s.saddr order by 1;
no rows selected
NOTE: if you are using OPatch utility 12.2.0.1.5 or later you do not need OCM(Oracle Configuration Manager) response file any more
Step4: Validate Patch Inventory for all homes
$opatch lsinventory -detail -oh /u01/grid/product/12.1.0.2/gi > /u01/stage/GI_OH_INV
$opatch lsinventory -detail -oh /u01/product/12.1.0.2/dbhome1 > /u01/stage/DB_OH_INV
$opatch lsinventory -detail -oh /u01/product/12.1.0.2/dbhome1 > /u01/stage/DB_OH_INV
Step5: Verify and resolve the Patch Conflicts
as root user
# opatchauto apply /u01/stage/29698592 -analyze
to see the sample output of analyze command scroll down
Step6: Run opatch auto to patch node1
NOTE: The Patching Steps are only valid for systems where GI Home and the Database Homes are not shared and ACFS file system is not configured
As root user, execute the following command on node1
#export ORACLE_HOME=/u01/grid/product/12.1.0.2/gi
#export PATH=$PATH:$ORACLE_HOME/OPatch:$ORACLE_HOME/bin
#export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
#opatchauto apply /u01/stage/29698592
#export PATH=$PATH:$ORACLE_HOME/OPatch:$ORACLE_HOME/bin
#export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
#opatchauto apply /u01/stage/29698592
Step7: Repeat step 3 to 6 for node2.
Step8: Verify the patch Installation
$opatch lsinventory -oh /u01/grid/product/12.1.0.2/gi |grep -e 'patch_id1' -e 'patch_id2' -e 'patch_id3'
SQL> set serverout on;
SQL> exec dbms_qopatch.get_sqlpatch_status;
SQL> exec dbms_qopatch.get_sqlpatch_status;
Patch Id : 25171037
Action : APPLY
Action Time : 13-MAR-2018 11:54:14
Description : DATABASE PATCH SET UPDATE 12.1.0.2.170418
Logfile :
/u01/cfgtoollogs/sqlpatch/25171037/21099266/25171037_apply_DBD_2018Mar13
_11_51_42.log
Status : SUCCESS
Action : APPLY
Action Time : 13-MAR-2018 11:54:14
Description : DATABASE PATCH SET UPDATE 12.1.0.2.170418
Logfile :
/u01/cfgtoollogs/sqlpatch/25171037/21099266/25171037_apply_DBD_2018Mar13
_11_51_42.log
Status : SUCCESS
Patch Id : 28259833
Action : APPLY
Action Time : 03-NOV-2018 17:14:39
Description : DATABASE PATCH SET UPDATE 12.1.0.2.181016
Logfile :
/u01/cfgtoollogs/sqlpatch/28259833/22488632/28259833_apply_DBD_2018Nov03
_17_13_55.log
Status : SUCCESS
Action : APPLY
Action Time : 03-NOV-2018 17:14:39
Description : DATABASE PATCH SET UPDATE 12.1.0.2.181016
Logfile :
/u01/cfgtoollogs/sqlpatch/28259833/22488632/28259833_apply_DBD_2018Nov03
_17_13_55.log
Status : SUCCESS
Patch Id : 29494060
Action : APPLY
Action Time : 19-SEP-2019 11:36:21
Description : DATABASE PATCH SET UPDATE 12.1.0.2.190716
Logfile :
/u01/cfgtoollogs/sqlpatch/29494060/22993235/29494060_apply_DBD_2019Sep19
_11_35_55.log
Status : SUCCESS
Action : APPLY
Action Time : 19-SEP-2019 11:36:21
Description : DATABASE PATCH SET UPDATE 12.1.0.2.190716
Logfile :
/u01/cfgtoollogs/sqlpatch/29494060/22993235/29494060_apply_DBD_2019Sep19
_11_35_55.log
Status : SUCCESS
PL/SQL procedure successfully completed.
OR
SQL> select xmltransform(dbms_qopatch.is_patch_installed('29494060'), dbms_qopatch.get_opatch_xslt) "Patch installed?" from dual;
Patch installed?
--------------------------------------------------------------------------------
Patch Information:
29494060: applied on 2019-09-19T11:00:56+02:00
29494060: applied on 2019-09-19T11:00:56+02:00
NOTE: The step "Loading Modified SQL Files into the Database" has been automated with opatch auto starting from 12c. opatchauto automatically performs the load of the modified SQL files into the Database.
opatchauto apply <PatchID> -analyze Output
========================================================================================================================================
OPatchauto session is initiated at Tue Sep 17 17:05:18 2019
OPatchauto session is initiated at Tue Sep 17 17:05:18 2019
System initialization log file is /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchautodb/systemconfig2019-09-17_05-05-20PM.log.
Session log file is /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/opatchauto2019-09-17_05-06-52PM.log
The id for this session is 5CHZ
The id for this session is 5CHZ
Executing OPatch prereq operations to verify patch applicability on home //u01/product/12.1.0.2/dbhome1
Executing OPatch prereq operations to verify patch applicability on home /u01/grid/product/12.1.0.2/gi
Executing OPatch prereq operations to verify patch applicability on home //u01/product/12.1.0.2/dbhome3
Patch applicability verified successfully on home /u01/grid/product/12.1.0.2/gi
Patch applicability verified successfully on home /u01/grid/product/12.1.0.2/gi
Patch applicability verified successfully on home //u01/product/12.1.0.2/dbhome3
Patch applicability verified successfully on home //u01/product/12.1.0.2/dbhome1
Verifying SQL patch applicability on home //u01/product/12.1.0.2/dbhome3
Verifying SQL patch applicability on home //u01/product/12.1.0.2/dbhome1
SQL patch applicability verified successfully on home //u01/product/12.1.0.2/dbhome3
SQL patch applicability verified successfully on home //u01/product/12.1.0.2/dbhome3
SQL patch applicability verified successfully on home //u01/product/12.1.0.2/dbhome1
OPatchAuto successful.
--------------------------------Summary--------------------------------
Analysis for applying patches has completed successfully:
Host:node1
CRS Home:/u01/grid/product/12.1.0.2/gi
Version:12.1.0.2.0
CRS Home:/u01/grid/product/12.1.0.2/gi
Version:12.1.0.2.0
==Following patches were SKIPPED:
Patch: /u01/stage/29698592/26983807
Reason: This patch is already been applied, so not going to apply again.
Reason: This patch is already been applied, so not going to apply again.
==Following patches were SUCCESSFULLY analyzed to be applied:
Patch: /u01/stage/29698592/29423125
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-06PM_1.log
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-06PM_1.log
Patch: /u01/stage/29698592/29494060
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-06PM_1.log
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-06PM_1.log
Patch: /u01/stage/29698592/29509318
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-06PM_1.log
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-06PM_1.log
Host:node1
RAC Home://u01/product/12.1.0.2/dbhome3
Version:12.1.0.2.0
==Following patches were SKIPPED:
Patch: /u01/stage/29698592/26983807
Reason: This patch is not applicable to this specified target type - "rac_database"
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/stage/29698592/29423125
Reason: This patch is not applicable to this specified target type - "rac_database"
Reason: This patch is not applicable to this specified target type - "rac_database"
==Following patches were SUCCESSFULLY analyzed to be applied:
Patch: /u01/stage/29698592/29494060
Log: //u01/product/12.1.0.2/dbhome3/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-07PM_1.log
Log: //u01/product/12.1.0.2/dbhome3/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-07PM_1.log
Patch: /u01/stage/29698592/29509318
Log: //u01/product/12.1.0.2/dbhome3/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-07PM_1.log
Log: //u01/product/12.1.0.2/dbhome3/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-07PM_1.log
Host:node1
RAC Home://u01/product/12.1.0.2/dbhome1
Version:12.1.0.2.0
==Following patches were SKIPPED:
Patch: /u01/stage/29698592/26983807
Reason: This patch is not applicable to this specified target type - "rac_database"
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/stage/29698592/29423125
Reason: This patch is not applicable to this specified target type - "rac_database"
Reason: This patch is not applicable to this specified target type - "rac_database"
==Following patches were SUCCESSFULLY analyzed to be applied:
Patch: /u01/stage/29698592/29494060
Log: //u01/product/12.1.0.2/dbhome1/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-07PM_1.log
Log: //u01/product/12.1.0.2/dbhome1/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-07PM_1.log
Patch: /u01/stage/29698592/29509318
Log: //u01/product/12.1.0.2/dbhome1/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-07PM_1.log
Log: //u01/product/12.1.0.2/dbhome1/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-17_17-07-07PM_1.log
Following homes are skipped during patching as patches are not applicable:
//u01/product/11.2.0.4/dbhome1
OPatchauto session completed at Tue Sep 17 17:13:17 2019
Time taken to complete the session 8 minutes, 0 second
You have new mail in /var/spool/mail/root
========================================================================================================================================
Time taken to complete the session 8 minutes, 0 second
You have new mail in /var/spool/mail/root
========================================================================================================================================
opatch auto apply <PATCH ID> Output
========================================================================================================================================
OPatchauto session is initiated at Wed Sep 18 10:59:31 2019
========================================================================================================================================
OPatchauto session is initiated at Wed Sep 18 10:59:31 2019
System initialization log file is /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchautodb/systemconfig2019-09-18_10-59-33AM.log.
Session log file is /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/opatchauto2019-09-18_11-01-03AM.log
The id for this session is WD53
The id for this session is WD53
Executing OPatch prereq operations to verify patch applicability on home /u01/product/12.1.0.2/dbhome1
Executing OPatch prereq operations to verify patch applicability on home /u01/grid/product/12.1.0.2/gi
Executing OPatch prereq operations to verify patch applicability on home /u01/product/12.1.0.2/dbhome3
Patch applicability verified successfully on home /u01/grid/product/12.1.0.2/gi
Patch applicability verified successfully on home /u01/grid/product/12.1.0.2/gi
Patch applicability verified successfully on home /u01/product/12.1.0.2/dbhome3
Patch applicability verified successfully on home /u01/product/12.1.0.2/dbhome1
Verifying SQL patch applicability on home /u01/product/12.1.0.2/dbhome3
Verifying SQL patch applicability on home /u01/product/12.1.0.2/dbhome1
SQL patch applicability verified successfully on home /u01/product/12.1.0.2/dbhome3
SQL patch applicability verified successfully on home /u01/product/12.1.0.2/dbhome3
com.oracle.glcm.patch.auto.db.product.driver.crs.CrsProductDrivercom.oracle.glcm.patch.auto.db.product.driver.crs.CrsProductDrivercom.oracle.glcm.patch.auto.db.product.driver.crs.CrsProductDrivercom.oracle. glcm.patch.auto.db.product.driver.crs.CrsProductDriverSQL patch applicability verified successfully on home /u01/product/12.1.0.2/dbhome1
Preparing to bring down database service on home /u01/product/12.1.0.2/dbhome1
Successfully prepared home /u01/product/12.1.0.2/dbhome1 to bring down database service
Preparing to bring down database service on home /u01/product/12.1.0.2/dbhome3
Successfully prepared home /u01/product/12.1.0.2/dbhome3 to bring down database service
Bringing down CRS service on home /u01/grid/product/12.1.0.2/gi
Prepatch operation log file location: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/crsconfig/crspatch_node1_2019-09-18_11-08-08AM.log
CRS service brought down successfully on home /u01/grid/product/12.1.0.2/gi
Performing prepatch operation on home /u01/product/12.1.0.2/dbhome1
Perpatch operation completed successfully on home /u01/product/12.1.0.2/dbhome1
Performing prepatch operation on home /u01/product/12.1.0.2/dbhome3
Perpatch operation completed successfully on home /u01/product/12.1.0.2/dbhome3
Start applying binary patch on home /u01/product/12.1.0.2/dbhome1
Binary patch applied successfully on home /u01/product/12.1.0.2/dbhome1
Start applying binary patch on home /u01/product/12.1.0.2/dbhome3
Binary patch applied successfully on home /u01/product/12.1.0.2/dbhome3
Performing postpatch operation on home /u01/product/12.1.0.2/dbhome1
Postpatch operation completed successfully on home /u01/product/12.1.0.2/dbhome1
Performing postpatch operation on home /u01/product/12.1.0.2/dbhome3
Postpatch operation completed successfully on home /u01/product/12.1.0.2/dbhome3
Start applying binary patch on home /u01/grid/product/12.1.0.2/gi
Binary patch applied successfully on home /u01/grid/product/12.1.0.2/gi
Starting CRS service on home /u01/grid/product/12.1.0.2/gi
Postpatch operation log file location: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/crsconfig/crspatch_node1_2019-09-18_11-20-52AM.log
CRS service started successfully on home /u01/grid/product/12.1.0.2/gi
Preparing home /u01/product/12.1.0.2/dbhome1 after database service restarted
No step execution required.........
Preparing home /u01/product/12.1.0.2/dbhome3 after database service restarted
No step execution required.........
Trying to apply SQL patch on home /u01/product/12.1.0.2/dbhome1
SQL patch applied successfully on home /u01/product/12.1.0.2/dbhome1
Trying to apply SQL patch on home /u01/product/12.1.0.2/dbhome3
SQL patch applied successfully on home /u01/product/12.1.0.2/dbhome3
OPatchAuto successful.
--------------------------------Summary--------------------------------
Patching is completed successfully. Please find the summary as follows:
Host:node1
RAC Home:/u01/product/12.1.0.2/dbhome1
Version:12.1.0.2.0
Summary:
RAC Home:/u01/product/12.1.0.2/dbhome1
Version:12.1.0.2.0
Summary:
==Following patches were SKIPPED:
Patch: /u01/stage/29698592/26983807
Reason: This patch is not applicable to this specified target type - "rac_database"
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/stage/29698592/29423125
Reason: This patch is not applicable to this specified target type - "rac_database"
Reason: This patch is not applicable to this specified target type - "rac_database"
==Following patches were SUCCESSFULLY applied:
Patch: /u01/stage/29698592/29494060
Log: /u01/product/12.1.0.2/dbhome1/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-09-24AM_1.log
Log: /u01/product/12.1.0.2/dbhome1/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-09-24AM_1.log
Patch: /u01/stage/29698592/29509318
Log: /u01/product/12.1.0.2/dbhome1/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-09-24AM_1.log
Log: /u01/product/12.1.0.2/dbhome1/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-09-24AM_1.log
Host:node1
RAC Home:/u01/product/12.1.0.2/dbhome3
Version:12.1.0.2.0
Summary:
==Following patches were SKIPPED:
Patch: /u01/stage/29698592/26983807
Reason: This patch is not applicable to this specified target type - "rac_database"
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/stage/29698592/29423125
Reason: This patch is not applicable to this specified target type - "rac_database"
Reason: This patch is not applicable to this specified target type - "rac_database"
==Following patches were SUCCESSFULLY applied:
Patch: /u01/stage/29698592/29494060
Log: /u01/product/12.1.0.2/dbhome3/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-12-08AM_1.log
Log: /u01/product/12.1.0.2/dbhome3/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-12-08AM_1.log
Patch: /u01/stage/29698592/29509318
Log: /u01/product/12.1.0.2/dbhome3/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-12-08AM_1.log
Log: /u01/product/12.1.0.2/dbhome3/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-12-08AM_1.log
Host:node1
CRS Home:/u01/grid/product/12.1.0.2/gi
Version:12.1.0.2.0
Summary:
==Following patches were SKIPPED:
Patch: /u01/stage/29698592/26983807
Reason: This patch is already been applied, so not going to apply again.
Reason: This patch is already been applied, so not going to apply again.
==Following patches were SUCCESSFULLY applied:
Patch: /u01/stage/29698592/29423125
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-13-44AM_1.log
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-13-44AM_1.log
Patch: /u01/stage/29698592/29494060
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-13-44AM_1.log
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-13-44AM_1.log
Patch: /u01/stage/29698592/29509318
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-13-44AM_1.log
Log: /u01/grid/product/12.1.0.2/gi/cfgtoollogs/opatchauto/core/opatch/opatch2019-09-18_11-13-44AM_1.log
Patching session reported following warning(s):
_________________________________________________
[WARNING] The database instance 'DCDB' from '/u01/product/12.1.0.2/dbhome1', in host'node1' is not running. SQL changes, if any, will not be applied.
To apply. the SQL changes, bring up the database instance and run the command manually from any one node (run as oracle).
Refer to the readme to get the correct steps for applying the sql changes.
To apply. the SQL changes, bring up the database instance and run the command manually from any one node (run as oracle).
Refer to the readme to get the correct steps for applying the sql changes.
Following homes are skipped during patching as patches are not applicable:
/u01/product/11.2.0.4/dbhome1
OPatchauto session completed at Wed Sep 18 11:38:58 2019
Time taken to complete the session 39 minutes, 28 seconds
Time taken to complete the session 39 minutes, 28 seconds
========================================================================================================================================
Well written article . Thank you for sharing this with all ..
ReplyDelete