Patch: 39036936 (Oracle Grid Infrastructure 19.31 RU)
Document Information
| Item | Value |
|---|---|
| Document | Oracle 19c RU Patching SOP |
| Oracle Version | 19c |
| Patch Number | 39036936 |
| Patch Type | Release Update (RU) |
| Environment | Production |
| Downtime | Planned Maintenance |
| Prepared By | Oracle DBA Team |
Purpose
This document describes the standard operating procedure for applying Oracle Database 19c Release Update (RU) in a production environment, including pre-checks, patch installation, validation, rollback considerations, and post-patch verification.
Patch Details
| Item | Value |
|---|---|
| Oracle Version | 19c |
| RU Version | 19.31 |
| Patch Number | 39036936 |
| Patch Type | Release Update |
| Installation Tool | OPatch / OPatchAuto |
| Datapatch Required | Yes |
| Downtime | Required |
Prerequisites
Oracle Support credentials
Patch downloaded from My Oracle Support
Latest OPatch utility installed
Root access (for GI patching)
Sufficient free space in Oracle Home
RMAN backup completed
Guaranteed Restore Point (recommended)
Maintenance window approved
Pre-Patching Checklist
Verify Oracle Home.
Verify Grid Home.
Check database status.
Check listener status.
Check Clusterware status.
Verify ASM disk groups.
Confirm RMAN backup success.
Review alert logs.
Validate Data Guard synchronization (if applicable).
Example commands:
crsctl stat res -t
srvctl status database -d PRODDBNAMEDB
srvctl status service -d DBNAME
srvctl status listener
asmcmd lsdg
Verify OPatch Version
$ORACLE_HOME/OPatch/opatch version
OPatch Version: 12.2.0.1.43
OPatch succeeded.
$ORACLE_HOME/OPatch/opatch lspatches
35643107;Database Release Update : 19.21.0.0.231017 (35643107)
29585399;OCW RELEASE UPDATE 19.3.0.0.0 (29585399)
OPatch succeeded.
$ORACLE_HOME/OPatch/opatch lsinventory
Stop Database Services
RAC:
srvctl stop instance -d DBNAME -i INSTANCENAME
Conflict Check
As the Grid home user:
$ORACLE_HOME/OPatch/opatch prereq CheckMinimumOPatchVersion-phBaseDir /u01/patch/39036936/39034528
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /u01/patch/39036936/39034528
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /u01/patch/39036936/39039430
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /u01/patch/39036936/39055473
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /u01/patch/39036936/39107855
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /u01/patch/39036936/39107825
For Oracle home, as home user:
$ORACLE_HOME/OPatch/opatch prereq CheckMinimumOPatchVersion-phBaseDir /u01/patch/39036936/39034528
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /u01/patch/39036936/39034528
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /u01/patch/39036936/39039430
Expected:
Prereq check passed.
Analyze Patch
cd /u01/app/19.3.0/grid/OPatch
/u01/app/19.3.0/grid/OPatch/ opatchauto apply /u01/patches/39036936 -analyze
OPatchauto session is initiated at Tue Jul 14 13:44:08 2026
System initialization log file is /u01/app/19.3.0/grid/ cfgtoollogs/opatchautodb/ systemconfig2026-07-14_01-44- 12PM.log.
Session log file is /u01/app/19.3.0/grid/ cfgtoollogs/opatchauto/ opatchauto2026-07-14_01-44- 31PM.log
The id for this session is E8Y5
Executing OPatch prereq operations to verify patch applicability on home /u01/app/19.3.0/grid
Patch applicability verified successfully on home /u01/app/19.3.0/grid
Executing OPatch prereq operations to verify patch applicability on home /u01/app/oracle/product/19.3. 0/dbhome_1
Patch applicability verified successfully on home /u01/app/oracle/product/19.3. 0/dbhome_1
Executing patch validation checks on home /u01/app/19.3.0/grid
Patch validation checks successfully completed on home /u01/app/19.3.0/grid
Executing patch validation checks on home /u01/app/oracle/product/19.3. 0/dbhome_1
Patch validation checks successfully completed on home /u01/app/oracle/product/19.3. 0/dbhome_1
Verifying SQL patch applicability on home /u01/app/oracle/product/19.3. 0/dbhome_1
SQL patch applicability verified successfully on home /u01/app/oracle/product/19.3. 0/dbhome_1
OPatchAuto successful.
------------------------------ --Summary--------------------- -----------
Analysis for applying patches has completed successfully:
Host:oldv44t
CRS Home:/u01/app/19.3.0/grid
Version:19.0.0.0.0
==Following patches were SUCCESSFULLY analyzed to be applied:
Patch: /u01/patches/39036936/39039430
Log: /u01/app/19.3.0/grid/ cfgtoollogs/opatchauto/core/ opatch/opatch2026-07-14_13-44- 46PM_1.log
Patch: /u01/patches/39036936/39055473
Log: /u01/app/19.3.0/grid/ cfgtoollogs/opatchauto/core/ opatch/opatch2026-07-14_13-44- 46PM_1.log
Patch: /u01/patches/39036936/39107825
Log: /u01/app/19.3.0/grid/ cfgtoollogs/opatchauto/core/ opatch/opatch2026-07-14_13-44- 46PM_1.log
Patch: /u01/patches/39036936/39107855
Log: /u01/app/19.3.0/grid/ cfgtoollogs/opatchauto/core/ opatch/opatch2026-07-14_13-44- 46PM_1.log
Patch: /u01/patches/39036936/39034528
Log: /u01/app/19.3.0/grid/ cfgtoollogs/opatchauto/core/ opatch/opatch2026-07-14_13-44- 46PM_1.log
Host:oldv44t
RAC Home:/u01/app/oracle/product/ 19.3.0/dbhome_1
Version:19.0.0.0.0
==Following patches were SKIPPED:
Patch: /u01/patches/39036936/39055473
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/patches/39036936/39107825
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/patches/39036936/39107855
Reason: This patch is not applicable to this specified target type - "rac_database"
==Following patches were SUCCESSFULLY analyzed to be applied:
Patch: /u01/patches/39036936/39039430
Log: /u01/app/oracle/product/19.3. 0/dbhome_1/cfgtoollogs/ opatchauto/core/opatch/ opatch2026-07-14_13-47-07PM_1. log
Patch: /u01/patches/39036936/39034528
Log: /u01/app/oracle/product/19.3. 0/dbhome_1/cfgtoollogs/ opatchauto/core/opatch/ opatch2026-07-14_13-47-07PM_1. log
OPatchauto session completed at Tue Jul 14 13:50:57 2026
Time taken to complete the session 6 minutes, 45 seconds
[root@oldv44t OPatch]#
Apply Patch
/u01/app/19.3.0/grid/OPatch/
OPatchauto session is initiated at Wed Jul 15 01:10:48 2026
System initialization log file is /u01/app/19.3.0/grid/
Session log file is /u01/app/19.3.0/grid/
The id for this session is 6Y14
Executing OPatch prereq operations to verify patch applicability on home /u01/app/19.3.0/grid
Patch applicability verified successfully on home /u01/app/19.3.0/grid
Executing OPatch prereq operations to verify patch applicability on home /u01/app/oracle/product/19.3.
Patch applicability verified successfully on home /u01/app/oracle/product/19.3.
Executing patch validation checks on home /u01/app/19.3.0/grid
Patch validation checks successfully completed on home /u01/app/19.3.0/grid
Executing patch validation checks on home /u01/app/oracle/product/19.3.
Patch validation checks successfully completed on home /u01/app/oracle/product/19.3.
Verifying SQL patch applicability on home /u01/app/oracle/product/19.3.
SQL patch applicability verified successfully on home /u01/app/oracle/product/19.3.
Preparing to bring down database service on home /u01/app/oracle/product/19.3.
No step execution required.........
Performing prepatch operations on CRS - bringing down CRS service on home /u01/app/19.3.0/grid
Prepatch operation log file location: /u01/app/grid/crsdata/oldv44t/
CRS service brought down successfully on home /u01/app/19.3.0/grid
Performing prepatch operation on home /u01/app/oracle/product/19.3.
Prepatch operation completed successfully on home /u01/app/oracle/product/19.3.
Start applying binary patch on home /u01/app/oracle/product/19.3.
Binary patch applied successfully on home /u01/app/oracle/product/19.3.
Running rootadd_rdbms.sh on home /u01/app/oracle/product/19.3.
Successfully executed rootadd_rdbms.sh on home /u01/app/oracle/product/19.3.
Performing postpatch operation on home /u01/app/oracle/product/19.3.
Postpatch operation completed successfully on home /u01/app/oracle/product/19.3.
Start applying binary patch on home /u01/app/19.3.0/grid
Binary patch applied successfully on home /u01/app/19.3.0/grid
Running rootadd_rdbms.sh on home /u01/app/19.3.0/grid
Successfully executed rootadd_rdbms.sh on home /u01/app/19.3.0/grid
Performing postpatch operations on CRS - starting CRS service on home /u01/app/19.3.0/grid
Postpatch operation log file location: /u01/app/grid/crsdata/oldv44t/
CRS service started successfully on home /u01/app/19.3.0/grid
Preparing home /u01/app/oracle/product/19.3.
No step execution required.........
Trying to apply SQL patch on home /u01/app/oracle/product/19.3.
SQL patch applied successfully on home /u01/app/oracle/product/19.3.
OPatchAuto successful.
------------------------------
Patching is completed successfully. Please find the summary as follows:
Host:oldv44t
RAC Home:/u01/app/oracle/product/
Version:19.0.0.0.0
Summary:
==Following patches were SKIPPED:
Patch: /u01/patches/39036936/39055473
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/patches/39036936/39107825
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/patches/39036936/39107855
Reason: This patch is not applicable to this specified target type - "rac_database"
==Following patches were SUCCESSFULLY applied:
Patch: /u01/patches/39036936/39034528
Log: /u01/app/oracle/product/19.3.
Patch: /u01/patches/39036936/39039430
Log: /u01/app/oracle/product/19.3.
Host:oldv44t
CRS Home:/u01/app/19.3.0/grid
Version:19.0.0.0.0
Summary:
==Following patches were SUCCESSFULLY applied:
Patch: /u01/patches/39036936/39034528
Log: /u01/app/19.3.0/grid/
Patch: /u01/patches/39036936/39039430
Log: /u01/app/19.3.0/grid/
Patch: /u01/patches/39036936/39055473
Log: /u01/app/19.3.0/grid/
Patch: /u01/patches/39036936/39107825
Log: /u01/app/19.3.0/grid/
Patch: /u01/patches/39036936/39107855
Log: /u01/app/19.3.0/grid/
OPatchauto session completed at Wed Jul 15 01:44:07 2026
Time taken to complete the session 33 minutes, 15 seconds
OPatch succeeded.
Repeat this on all nodesStart Services
crsctl start cluster -all
srvctl start asm
srvctl start listener
srvctl start database -d PRODDB
Execute Datapatch
cd $ORACLE_HOME/OPatch
./datapatch -verbose
Verify:
SQL Patching tool complete.
Post-Patching Validation
Database
ACTION_TIME ACTION NAMESPACE VERSION ID COMMENTS BUNDLE_SER
------------------------------ -- --------------- ---------- ---------------------- ---------- ------------------------------ ----------
22-DEC-22 09.38.15.371287 AM RU_APPLY SERVER 19.0.0.0.0 Patch applied from 19.3.0.0.0
to 19.15.0.0.0: Release_Update
- 220331125408
21-JAN-23 01.16.07.522015 AM RU_APPLY SERVER 19.0.0.0.0 Patch applied from 19.15.0.0.0
to 19.17.0.0.0: Release_Updat
e - 220924224051
15-DEC-23 09.00.02.923597 PM RU_APPLY SERVER 19.0.0.0.0 Patch applied from 19.17.0.0.0
to 19.21.0.0.0: Release_Updat
e - 230930151951
26-SEP-24 10.39.15.082006 PM RU_APPLY SERVER 19.0.0.0.0 Patch applied from 19.21.0.0.0
to 19.24.0.0.0: Release_Updat
e - 240627235157
10-MAR-25 11.41.58.200462 PM RU_APPLY SERVER 19.0.0.0.0 Patch applied from 19.24.0.0.0
to 19.26.0.0.0: Release_Updat
e - 250118124854
10-JUL-25 12.04.10.912398 AM RU_APPLY SERVER 19.0.0.0.0 Patch applied from 19.26.0.0.0
to 19.27.0.0.0: Release_Updat
e - 250406131139
22-JAN-26 03.02.24.271925 AM RU_APPLY SERVER 19.0.0.0.0 Patch applied from 19.27.0.0.0
to 19.29.0.0.0: Release_Updat
e - 251002005342
21-FEB-26 01.36.42.117186 AM RU_ROLLBACK SERVER 19.0.0.0.0 Patch rolled back from 19.29.0
.0.0 to 19.27.0.0.0: Release_U
pdate - 250406131139
15-JUL-26 01.40.49.914347 AM RU_APPLY SERVER 19.0.0.0.0 Patch applied from 19.27.0.0.0
to 19.31.0.0.0: Release_Updat
e - 260514003012
BOOTSTRAP DATAPATCH 19 RDBMS_19.31.0.0.0DBRU_LINUX.X6
4_260424.2
10 rows selected.
PATCH_ID PATCH_UID SOURCE_VERSION STATUS ACTION_TIME DESCRIPTION
---------- ---------- --------------- ------------------------- ------------------------------ -- ------------------------------ ------------------------------ ----------
33806152 24713297 19.1.0.0.0 SUCCESS 22-DEC-22 09.38.43.845617 AM Database Release Update : 19.15.0.0.220419 (33806152)
34419443 24972075 19.15.0.0.0 SUCCESS 21-JAN-23 01.18.07.655757 AM Database Release Update : 19.17.0.0.221018 (34419443)
35643107 25405995 19.17.0.0.0 SUCCESS 15-DEC-23 09.04.12.148086 PM Database Release Update : 19.21.0.0.231017 (35643107)
36582781 25751445 19.21.0.0.0 SUCCESS 26-SEP-24 10.39.15.073972 PM Database Release Update : 19.24.0.0.240716 (36582781)
37260974 26040769 19.24.0.0.0 SUCCESS 10-MAR-25 11.41.58.191910 PM Database Release Update : 19.26.0.0.250121 (37260974)
37642901 27123174 19.26.0.0.0 SUCCESS 10-JUL-25 12.04.10.902827 AM Database Release Update : 19.27.0.0.250415 (37642901)
38291812 28130960 19.27.0.0.0 SUCCESS 22-JAN-26 03.02.24.263485 AM Database Release Update : 19.29.0.0.251021 (38291812)
38291812 28130960 19.29.0.0.0 SUCCESS 21-FEB-26 01.36.42.108378 AM Database Release Update : 19.29.0.0.251021 (38291812)
39034528 28740323 19.27.0.0.0 SUCCESS 15-JUL-26 01.40.49.902641 AM Database Release Update : 19.31.0.0.260421 (REL-APR2026) (39034528)
9 rows selected.
COMP_ID COMP_NAME VERSION STATUS
-------------------- ------------------------------ ---------- --------------- ---------------
APS OLAP Analytic Workspace 19.0.0.0.0 VALID
CATALOG Oracle Database Catalog Views 19.0.0.0.0 VALID
CATJAVA Oracle Database Java Packages 19.0.0.0.0 VALID
CATPROC Oracle Database Packages and Types 19.0.0.0.0 VALID
CONTEXT Oracle Text 19.0.0.0.0 VALID
DV Oracle Database Vault 19.0.0.0.0 VALID
JAVAVM JServer JAVA Virtual Machine 19.0.0.0.0 VALID
OLS Oracle Label Security 19.0.0.0.0 VALID
ORDIM Oracle Multimedia 19.0.0.0.0 VALID
OWM Oracle Workspace Manager 19.0.0.0.0 VALID
RAC Oracle Real Application Clusters 19.0.0.0.0 VALID
SDO Spatial 19.0.0.0.0 VALID
XDB Oracle XML Database 19.0.0.0.0 VALID
XML Oracle XDK 19.0.0.0.0 VALID
XOQ Oracle OLAP API 19.0.0.0.0 VALID
15 rows selected.
SQL>
Inventory
opatch lsinventory
Cluster
crsctl stat res -t
Listener
lsnrctl status
ASM
asmcmd lsdg
Data Guard Validation
Verify redo transport.
select process,status from v$managed_standby;
select transport_lag,apply_lag
from v$dataguard_stats;
Verify Broker.
dgmgrl
show configuration;
Expected
SUCCESS
OEM Validation
Verify all targets are Up.
Confirm no agent upload backlog.
Check monitoring alerts.
Validate metric collection.
Confirm no critical incidents after restart.
Health Checks
Database open successfully
Listener registered services
CRS healthy
ASM mounted
RMAN backup tested
Data Guard synchronized
OEM monitoring normal
Application connectivity verified
Troubleshooting
| Issue | Resolution |
|---|---|
| OPatch version mismatch | Upgrade OPatch |
| Conflict detected | Resolve conflicts before applying |
| Datapatch failure | Review sqlpatch_invocation.log |
| CRS startup issue | Review crsd.log |
| Listener not registering | Run ALTER SYSTEM REGISTER; |
| Invalid objects | Execute utlrp.sql |
| Data Guard lag | Restart MRP and verify redo transport |
Best Practices
Perform a full RMAN backup before patching.
Apply Grid Infrastructure patches before Database Home patches.
Use
opatchautofor RAC environments.Always execute
datapatchafter applying an RU.Validate application connectivity before handing the environment back to users.
Monitor the environment closely for at least 24 hours after patching.
Check Oracle's latest release notes and any known issues for the RU before production deployment, as Oracle may publish revisions or temporary holds for specific environments.
No comments:
Post a Comment