This page provides generic patching instructions based on some patch specific variables being set.
The assumption is that "Database RU and OJVM Combo" patches will be used.
The assumption is that the .profile contains all recommended settings and all recommended aliases are set.
For Data Guard environments...
Guaranteed Restore Points
prereq
Prevent any applications that may access your target database from doing so.
applyoff # Physical Standby Databases only
grpset
stoplist
dbshut
Not currently required.
cd /u01/img/${PTAR}/${PCOM}/${DBRU}
opatch apply -silent
Note: The Warnings listed below are expected on AIX and can be safely ignored. Always check opatch lsinventory to confirm patch application.
ld: 0711-773 WARNING:
ld: 0711-783 WARNING:
ld: 0711-319 WARNING:
ld: 0711-415 WARNING:
ld: 0711-224 WARNING:
ld: 0711-324 WARNING:
ld: 0711-301 WARNING:
ld: 0711-345 WARNING:
Note: If /u01/img/ocm.rsp does not exist then create it using the instructions here
Note: You may see a reference to Doc ID 2161861.1... this note does not exist on MOS... however, as long as the mentioned patch is a previous RU, then this can be ignored...
Sub-set patch [28440711] has become inactive due to the application of a super-set patch [28790654].
Please refer to Doc ID 2161861.1 for any possible further required actions.
cd /u01/img/${PTAR}/${PCOM}/${RJVM}
opatch apply -silent
Note: The Warnings listed below are expected on AIX and can be safely ignored. Always check opatch lsinventory to confirm patch application.
ld: 0711-773 WARNING:
ld: 0711-783 WARNING:
ld: 0711-319 WARNING:
ld: 0711-415 WARNING:
ld: 0711-224 WARNING:
ld: 0711-324 WARNING:
ld: 0711-301 WARNING:
ld: 0711-345 WARNING:
Note: You may see a reference to Doc ID 2161861.1... this note does not exist on MOS... however, as long as the mentioned patch is a previous JVM RU, then this can be ignored...
Sub-set patch [28440711] has become inactive due to the application of a super-set patch [28790654].
Please refer to Doc ID 2161861.1 for any possible further required actions.
Not currently required.
Not currently required.
lsinv
sqlplus / as sysdba
startup upgrade
exit
datapatch
dbshut
sqlplus / as sysdba
startup # Standalone or Primary Instances only
startup mount # Standby Instances only
exit
rman catalog username/password@alias
UPGRADE CATALOG;
UPGRADE CATALOG;
EXIT;
checkreg
startlist
Any applications that may access your target database can now safely do so again.
adrci
show alert -p "originating_timestamp > systimestamp-1 and message_group like '%ddl%'" -term
Prevent any applications that may access your target database from doing so.
stoplist
dbshut
opatch rollback -id ${DBRU} -silent
opatch rollback -id ${RJVM} -silent
sqlplus / as sysdba
startup upgrade
exit
datapatch
dbshut
sqlplus / as sysdba
startup # Standalone or Primary Instances only
startup mount # Standby Instances only
exit
rman catalog username/password@alias
UPGRADE CATALOG;
UPGRADE CATALOG;
EXIT;
checkreg
The registry$sqlpatch view will record the APPLY and the ROLLBACK as shown below...
ACTION ACTION_TIME PATCH_ID DESCRIPTION
---------- ------------------------- ---------- -------------------------------------------------------
APPLY 27-APR-20 13.53.23.280012 30805580 OJVM RELEASE UPDATE 12.2.0.1.200414
APPLY 27-APR-20 13.53.26.453299 30886680 DATABASE APR 2020 RELEASE UPDATE 12.2.0.1.200414
ROLLBACK 27-APR-20 16.11.55.612517 30805580 OJVM RELEASE UPDATE 12.2.0.1.200414
ROLLBACK 27-APR-20 16.11.59.149423 30886680 DATABASE APR 2020 RELEASE UPDATE 12.2.0.1.200414
startlist
adrci
show alert -p "originating_timestamp > systimestamp-1 and message_group like '%ddl%'" -term
Prevent any applications that may access your target database from doing so.
stoplist
dbshut
opatch rollback -id ${DBRU} -silent
opatch rollback -id ${RJVM} -silent
sqlplus / as sysdba
startup # Standalone or Primary Instances only
startup mount # Standby Instances only
exit
startlist
applyoff # Set Apply Off (Physical Standby Databases only)
grpfback # Flashback to Guaranteed Restore Point
dbopenresetlogs # Open reset Logs (Standalone or Primary only)
invobjcnt # Check Invalid Objects (Standalone or Primary only)
checkreg
Your Patch activity should have disappeared.
For each Standby with the environment correctly set...
applyon