Skip to main content

How to Patch Oracle RAC Clusterware and Database Using opatch auto


<<Back to Oracle RAC Main Page

Step by Step Instruction to Patch Oracle RAC Cluster Version 11.2.0.4

Step0: download and read the readme.txt for the patch. The installation instruction and rollback instruction is provided in readme file.

Here is the extract and simplified version of Oracle  RAC patching procedure

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=/ora_app/product/11.2.0.4/dbhome_1
$export PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/OPatch
$opatch version
OPatch Version: 11.2.0.3.6
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/ora_app/stage)
  • $unzip /u01/ora_app/stage/p6880880_112000_Linux-x86-64.zip
  • $mv $ORACLE_HOME/OPatch $ORACLE_HOME/OPatch_Backup
  • $ cp /u01/ora_app/stage/OPatch $ORACLE_HOME/
  • $ opatch versionOPatch Version: 11.2.0.3.21
          OPatch succeeded.

Step2: Perform Complete Cluster Stack HealthCheck: Strongly Recommended

  • Download latest ORACheck utility, install it and run it to perform the 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/11.2.0.4/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: Patch One node after another in Rolling fashion
  • 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
  • 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

  • Verify and Ensure that there is no Active Session and Transactions Running on Node1

$ sqlplus "/as sysdba"
SQL> select SID,USERNAME,STATUS from v$session where username not in ('SYS','DBSNMP');
no rows selected

SQL>col machine for a30
SQL>col username for a30
SQL>col program for a30 trun
SQL>col sid for 99999
SQL>set lines 300
SQL>select sid,USED_UBLK,username,program,machine,systimestamp
SQL>from v$transaction t, v$session s
SQL>where SES_ADDR = s.saddr order by 1;
no rows selected

SQL>select sid,USED_UBLK,username,program,machine,systimestamp
SQL>from gv$transaction t, gv$session s
SQL>where SES_ADDR = s.saddr order by 1;
no rows selected

Step4: Create OCM response file

$ORACLE_HOME/OPatch/ocm/bin/emocmrsp -no_banner -output
/u01/ora_app/stage/ocm/ocm.rsp
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name:
You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:  y
The OCM configuration response file (/u01/ora_app/stage/ocm/ocm.rsp) was successfully created.



Step5: Run Opatch lsinventory for All homes and for All Patches

$opatch lsinventory -detail -oh /u01/grid/product/11.2.0.4/gi > /u01/ora_app/stage/CRS_HOME_Opatch_detail
$opatch lsinventory -detail -oh /ora_app/product/11.2.0.4/dbhome_1 > /u01/ora_app/stage/DB_HOME_Opatch_detail



Step6: Download and transfer the PSU to the server and unzip the patch file

Step7: Verify and resolve the Patch Conflicts 

$opatch prereq CheckConflictAgainstOHWithDetail -oh  /u01/grid/product/11.2.0.4/gi -ph ./
Oracle Interim Patch Installer version 11.2.0.3.21
Copyright (c) 2019, Oracle Corporation.  All rights reserved.
PREREQ session
Oracle Home       : /u01/grid/product/11.2.0.4/gi
Central Inventory : /u01/oraInventory
   from           : /u01/grid/product/11.2.0.4/gi/oraInst.loc
OPatch version    : 11.2.0.3.21
OUI version       : 11.2.0.4.0
Log file location : /u01/grid/product/11.2.0.4/gi/cfgtoollogs/opatch/opatch2019-08-22_09-43-17AM_1.log
Invoking prereq "checkconflictagainstohwithdetail"
Prereq "checkConflictAgainstOHWithDetail" passed.
OPatch succeeded.


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


Step8: As root user, execute the following command on node1

for GI Home
#opatch auto  /u01/ora_app/stage/29698727 -och /u01/grid/product/11.2.0.4/gi -ocmrf /u01/ora_app/stage/ocm/ocm.rsp
For DB Home
#opatch auto  /u01/ora_app/stage/29698727 -oh /ora_app/product/11.2.0.4/dbhome_1 -ocmrf /u01/ora_app/stage/ocm/ocm.rsp

NOTE: I prefer patching each OH separately to avoid any issue. You can patch all the homes in one go using command
#opatch auto /u01/ora_app/stage/29698727 -ocmrf /ora_work/patch/ocm/ocm.rsp

Step9: Repeat step 3 to 8 for node2.
Note: ensure to adjust the node name and other node specific details accordingly

Step10: Load modified SQL files into the database
Once all the nodes are patched, follow the steps to load modified SQL files into the database. For an Oracle RAC environment, perform these steps on only one node.


$cd $ORACLE_HOME/rdbms/admin
sqlplus "/as sysdba"
SQL>@catbundle.sql psu apply
SQL>@utlrp.sql

SQL>set line 200
SQL>col ACTION_TIME for a30
SQL>col COMMENTS for a30
SQL>col ACTION for a15
SQL>select name from v$database;
SQL>select * from dba_registry_history;

SQL>col COMP_NAME for a50 ;
SQL>col STATUS for a20
SQL>select COMP_NAME,VERSION,STATUS,MODIFIED from dba_registry order by MODIFIED;



Comments

  1. UnknownSeptember 8, 2020 at 8:12 PM

    Hi Sir,

    Thank you for sharing this. just a newbie question here, I noticed that you did not stop the database and listener and the grid infrastructure on the node to be patched. Is it automatically done by the opatch auto? Can you please also confirm that the other node is not affected and still open for users? Thank you very much

    ReplyDelete
    Replies
    1. Anand TiwariSeptember 9, 2020 at 2:22 AM

      If using opatchauto shutdown and start is taken care by opatch auto utility itself . Clusterware stack must be up and running to use opatch auto. by default the local node is affected. So its the server where you execute the opatch auto

      Delete

Post a Comment

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the server to be powered on, run the
Post a Comment
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco
7 comments
Read more

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)
Post a Comment
Read more

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.
Post a Comment
Read more

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container
Post a Comment
Read more

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.
Post a Comment
Read more

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry for database (ORCL
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02             EXPORT               FULL       EXECUTING OR You can also find the job name for export/import in logfile in beginning itself. Step2>Attach to the Job and check status One you get the Export/Import Job Name attach the job and check its status. You can attach or det
7 comments
Read more

ORA-15040: diskgroup is incomplete

<<Back to Oracle ASM Main Page ORA-15040: diskgroup is incomplete SQL> startup ORA-00099: warning: no parameter file specified for ASM instance ASM instance started Total System Global Area 1140850688 bytes Fixed Size                  8629704 bytes Variable Size            1107055160 bytes ASM Cache                  25165824 bytes ORA-15110: no diskgroups mounted Reason: The reason of this error is simply the ASM is not able to find the some or all the disks. Solution: Investigate and make all the disks available to ASM to mount the disk group. Make sure the disks has proper permissions. If you are using AFD check following services are online oracleacfs oracleadvm oracleoks  oracleafd   Source of Problem : Issue started after restart of the server After restarting the server when I tried to start the ASM instance its started throwing error.  ORA-15110: no diskgroups mounted Investigation in my Case Step1> ASM Logfile Scanning  Looked i
2 comments
Read more