筆者好久沒有使用opatchauto打過補丁了，搜了下自己的歷史隨筆，上次opatchauto打補丁的記錄還是Oracle 11g版本：
而11g版本如今已經不再向客戶推薦，19c也已經成為當下強力推薦的長期支持版本，我們知道19c的補丁也改為RU，今天給一個客戶做測試，為了規避已知bug，恰好需要應用RU補丁，索性就做個記錄備忘。
DBA很熟悉打補丁都要看對應的readme文件，從本次readme內容來看，19c實際不再需要配置響應文件，也無需手工執行DB腳本，不得不說O在自動化應用補丁的工作上又有了很大進步。
實際步驟只需兩步，本次應用補丁不幸遇到一些問題，匯總到第三部分供大家參考。
1.更新OPatch版本
下載需要的補丁介質，我習慣將其權限修改如下：
[root@db193 media]# chown grid:oinstall p*
[root@db193 media]# chmod 775 p*
[root@db193 media]# ls -lrth
總用量 2.6G
-rwxrwxr-x 1 grid oinstall 116M 9月 13 15:10 p6880880_190000_Linux-x86-64.zip
-rwxrwxr-x 1 grid oinstall 2.5G 9月 13 15:12 p32895426_190000_Linux-x86-64.zip
在所有節點的GI HOME和DB HOME下，都更新為符合應用補丁需求的OPatch版本。 將之前OPatch備份，解壓新版本的OPatch到$ORACLE_HOME目錄下，最后檢查OPatch版本。
--更新OPatch版本 @all nodes including GI HOME and DB HOME
mv OPatch OPatch_bak
unzip p6880880_112000_Linux-x86-64.zip -d $ORACLE_HOME
$ORACLE_HOME/OPatch/opatch version
這點和之前一樣，同樣GI的$ORACLE_HOME目錄權限默認無法寫，需要更改下，我通常會采用以下兩種方法：
--方法1:將GI的$ORACLE_HOME目錄權限臨時改為775（注意只改這一層即可！），操作完成后再修改回原來的755：
[root@db193 media]# chmod 775 /u01/app/19.3.0/grid
mv OPatch OPatch_bak
[grid@db193 grid]$ unzip /u01/media/p6880880_190000_Linux-x86-64.zip -d $ORACLE_HOME
[grid@db193 ~]$ $ORACLE_HOME/OPatch/opatch version
OPatch Version: 12.2.0.1.27
OPatch succeeded.
[root@db193 media]# chmod 755 /u01/app/19.3.0/grid
--方法2:直接使用root用戶解壓OPatch，然后修改OPatch目錄及子目錄權限：
[root@db195 grid]# mv OPatch OPatch_bak
[root@db195 grid]# unzip /u01/media/p6880880_190000_Linux-x86-64.zip -d /u01/app/19.3.0/grid
[root@db195 grid]# chown -R grid:oinstall OPatch
2.使用opatch auto應用補丁
實際按照readme，我的環境是最典型的，直接在每個節點分別執行opatchauto apply：
--opatchauto
As root user, execute the following command on each node of the cluster:
# <GI_HOME>/OPatch/opatchauto apply <UNZIPPED_PATCH_LOCATION>/32895426
# /u01/app/19.3.0/grid/OPatch/opatchauto apply /u01/media/32895426
[root@db193 ~]# /u01/app/19.3.0/grid/OPatch/opatchauto apply /u01/media/32895426
[root@db195 ~]# /u01/app/19.3.0/grid/OPatch/opatchauto apply /u01/media/32895426
3.本次遇到問題處理
3.1 節點1應用補丁，提示空間不足
實際上，打補丁空間剩余建議至少10GB+，這里錯誤顯示至少需要7465.104MB，實際肯定要多冗余一些空間。
仔細看19c的RU也比之前更智能了，空間不足實際是在補丁應用校驗階段就報出，這是個值得稱贊的改進，要知道之前很多客戶案例都是因為空間不足導致補丁應用中途失敗的，現在把這個空間問題提前校驗就免去了很多不必要的麻煩：
[root@db193 ~]# /u01/app/19.3.0/grid/OPatch/opatchauto apply /u01/media/32895426
OPatchauto session is initiated at Mon Sep 13 16:17:34 2021
System initialization log file is /u01/app/19.3.0/grid/cfgtoollogs/opatchautodb/systemconfig2021-09-13_04-17-45PM.log.
會話日志文件是/u01/app/19.3.0/grid/cfgtoollogs/opatchauto/opatchauto2021-09-13_04-19-50PM.log
此會話的 ID 為 ESYS
Executing OPatch prereq operations to verify patch applicability 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/db_1
Patch applicability verification failed on home /u01/app/19.3.0/grid
Patch applicability verification failed on home /u01/app/oracle/product/19.3.0/db_1
未能執行 [OPatchAutoBinaryAction] 補丁程序操作, 有關詳細信息, 請查看日志。故障:
Patch Target : db193->/u01/app/oracle/product/19.3.0/db_1 類型 [rac]
Details: [
---------------------------Patching Failed---------------------------------
Command execution failed during patching in home: /u01/app/oracle/product/19.3.0/db_1, host: db193.
Command failed: /u01/app/oracle/product/19.3.0/db_1/OPatch/opatchauto apply /u01/media/32895426 -oh /u01/app/oracle/product/19.3.0/db_1 -target_type rac_database -binary -invPtrLoc /u01/app/19.3.0/grid/oraInst.loc -jre /u01/app/19.3.0/grid/OPatch/jre -persistresult /u01/app/oracle/product/19.3.0/db_1/opatchautocfg/db/sessioninfo/sessionresult_analyze_db193_rac_2.ser -analyze -online -prepare_home
Command failure output:
==Following patches FAILED in analysis for apply:
Patch: /u01/media/32895426/32916816
Log: /u01/app/oracle/product/19.3.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2021-09-13_16-21-05下午_1.log
Reason: Failed during Analysis: CheckSystemSpace Failed, [ Prerequisite Status: FAILED, Prerequisite output:
The details are:
Required amount of space(7465.104MB) is not available.]
Patch: /u01/media/32895426/32904851
Log: /u01/app/oracle/product/19.3.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2021-09-13_16-21-05下午_1.log
Reason: Failed during Analysis: CheckSystemSpace Failed, [ Prerequisite Status: FAILED, Prerequisite output:
The details are:
Required amount of space(7465.104MB) is not available.]
After fixing the cause of failure Run opatchauto resume
]
OPATCHAUTO-68061: 業務流程引擎失敗。
OPATCHAUTO-68061: 業務流程引擎失敗, 返回代碼為 1
OPATCHAUTO-68061: 有關詳細資料, 請查看日志。
OPatchAuto 失敗。
OPatchauto session completed at Mon Sep 13 16:25:15 2021
Time taken to complete the session 7 minutes, 42 seconds
opatchauto failed with error code 42
清理一些日志空間后，再次執行嘗試：
[root@db193 ~]# /u01/app/19.3.0/grid/OPatch/opatchauto apply /u01/media/32895426
OPatchauto session is initiated at Mon Sep 13 16:40:14 2021
System initialization log file is /u01/app/19.3.0/grid/cfgtoollogs/opatchautodb/systemconfig2021-09-13_04-40-25PM.log.
會話日志文件是/u01/app/19.3.0/grid/cfgtoollogs/opatchauto/opatchauto2021-09-13_04-41-21PM.log
此會話的 ID 為 7M6S
Executing OPatch prereq operations to verify patch applicability 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/db_1
Patch applicability verified successfully on home /u01/app/oracle/product/19.3.0/db_1
Patch applicability verified successfully on home /u01/app/19.3.0/grid
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/db_1
Patch validation checks successfully completed on home /u01/app/oracle/product/19.3.0/db_1
Verifying SQL patch applicability on home /u01/app/oracle/product/19.3.0/db_1
SQL patch applicability verified successfully on home /u01/app/oracle/product/19.3.0/db_1
Preparing to bring down database service on home /u01/app/oracle/product/19.3.0/db_1
Successfully prepared home /u01/app/oracle/product/19.3.0/db_1 to bring down database service
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/db193/crsconfig/crs_prepatch_apply_inplace_db193_2021-09-13_04-48-22PM.log
CRS service brought down successfully on home /u01/app/19.3.0/grid
Performing prepatch operation on home /u01/app/oracle/product/19.3.0/db_1
Perpatch operation completed successfully on home /u01/app/oracle/product/19.3.0/db_1
Start applying binary patch on home /u01/app/oracle/product/19.3.0/db_1
Binary patch applied successfully on home /u01/app/oracle/product/19.3.0/db_1
Performing postpatch operation on home /u01/app/oracle/product/19.3.0/db_1
Postpatch operation completed successfully on home /u01/app/oracle/product/19.3.0/db_1
Start applying binary patch on home /u01/app/19.3.0/grid
Binary patch applied successfully 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/db193/crsconfig/crs_postpatch_apply_inplace_db193_2021-09-13_05-16-37PM.log
CRS service started successfully on home /u01/app/19.3.0/grid
Preparing home /u01/app/oracle/product/19.3.0/db_1 after database service restarted
No step execution required.........
Trying to apply SQL patch on home /u01/app/oracle/product/19.3.0/db_1
SQL patch applied successfully on home /u01/app/oracle/product/19.3.0/db_1
OPatchAuto 成功。
--------------------------------Summary--------------------------------
Patching is completed successfully. Please find the summary as follows:
Host:db193
RAC Home:/u01/app/oracle/product/19.3.0/db_1
Version:19.0.0.0.0
Summary:
==Following patches were SKIPPED:
Patch: /u01/media/32895426/32915586
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/media/32895426/32585572
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /u01/media/32895426/32918050
Reason: This patch is not applicable to this specified target type - "rac_database"
==Following patches were SUCCESSFULLY applied:
Patch: /u01/media/32895426/32904851
Log: /u01/app/oracle/product/19.3.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2021-09-13_16-51-45下午_1.log
Patch: /u01/media/32895426/32916816
Log: /u01/app/oracle/product/19.3.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2021-09-13_16-51-45下午_1.log
Host:db193
CRS Home:/u01/app/19.3.0/grid
Version:19.0.0.0.0
Summary:
==Following patches were SUCCESSFULLY applied:
Patch: /u01/media/32895426/32585572
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-09-13_17-03-57下午_1.log
Patch: /u01/media/32895426/32904851
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-09-13_17-03-57下午_1.log
Patch: /u01/media/32895426/32915586
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-09-13_17-03-57下午_1.log
Patch: /u01/media/32895426/32916816
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-09-13_17-03-57下午_1.log
Patch: /u01/media/32895426/32918050
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-09-13_17-03-57下午_1.log
OPatchauto session completed at Mon Sep 13 17:26:52 2021
Time taken to complete the session 46 minutes, 39 seconds
[root@db193 ~]#
好家伙，整個過程居然花了46分鍾..不過整體都是自動化執行的，也非常方便，期間可以休息一會兒，喝杯咖啡順便看着不報錯即可。
3.2 節點2應用補丁，提示權限不夠
在節點2應用補丁之前，進一步清理了能夠清理的日志，想加快補丁應用的時間。
本以為節點1順利成功，節點2也不會有啥問題了，結果還真的遇到了問題，在節點2執行補丁應用時，報錯有文件權限不夠：
[root@db195 ~]# /u01/app/19.3.0/grid/OPatch/opatchauto apply /u01/media/32895426
OPatchauto session is initiated at Mon Sep 13 17:29:29 2021
System initialization log file is /u01/app/19.3.0/grid/cfgtoollogs/opatchautodb/systemconfig2021-09-13_05-29-48PM.log.
會話日志文件是/u01/app/19.3.0/grid/cfgtoollogs/opatchauto/opatchauto2021-09-13_05-30-51PM.log
此會話的 ID 為 AMSA
Executing OPatch prereq operations to verify patch applicability 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/db_1
Patch applicability verified successfully on home /u01/app/oracle/product/19.3.0/db_1
Patch applicability verified successfully on home /u01/app/19.3.0/grid
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/db_1
Patch validation checks successfully completed on home /u01/app/oracle/product/19.3.0/db_1
Verifying SQL patch applicability on home /u01/app/oracle/product/19.3.0/db_1
SQL patch applicability verified successfully on home /u01/app/oracle/product/19.3.0/db_1
Preparing to bring down database service on home /u01/app/oracle/product/19.3.0/db_1
Successfully prepared home /u01/app/oracle/product/19.3.0/db_1 to bring down database service
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/db195/crsconfig/crs_prepatch_apply_inplace_db195_2021-09-13_05-40-09PM.log
CRS service brought down successfully on home /u01/app/19.3.0/grid
Performing prepatch operation on home /u01/app/oracle/product/19.3.0/db_1
Perpatch operation completed successfully on home /u01/app/oracle/product/19.3.0/db_1
Start applying binary patch on home /u01/app/oracle/product/19.3.0/db_1
Binary patch applied successfully on home /u01/app/oracle/product/19.3.0/db_1
Performing postpatch operation on home /u01/app/oracle/product/19.3.0/db_1
Postpatch operation completed successfully on home /u01/app/oracle/product/19.3.0/db_1
Start applying binary patch on home /u01/app/19.3.0/grid
Failed while applying binary patches on home /u01/app/19.3.0/grid
未能執行 [OPatchAutoBinaryAction] 補丁程序操作, 有關詳細信息, 請查看日志。故障:
Patch Target : db195->/u01/app/19.3.0/grid 類型 [crs]
Details: [
---------------------------Patching Failed---------------------------------
Command execution failed during patching in home: /u01/app/19.3.0/grid, host: db195.
Command failed: /u01/app/19.3.0/grid/OPatch/opatchauto apply /u01/media/32895426 -oh /u01/app/19.3.0/grid -target_type cluster -binary -invPtrLoc /u01/app/19.3.0/grid/oraInst.loc -jre /u01/app/19.3.0/grid/OPatch/jre -persistresult /u01/app/19.3.0/grid/opatchautocfg/db/sessioninfo/sessionresult_db195_crs_1.ser -analyzedresult /u01/app/19.3.0/grid/opatchautocfg/db/sessioninfo/sessionresult_analyze_db195_crs_1.ser
Command failure output:
==Following patches FAILED in apply:
Patch: /u01/media/32895426/32585572
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-09-13_17-56-51下午_1.log
Reason: Failed during Patching: oracle.opatch.opatchsdk.OPatchException: ApplySession 在系統修改階段失敗... 'ApplySession::apply failed: java.io.IOException: oracle.sysman.oui.patch.PatchException: java.io.FileNotFoundException: /u01/app/oraInventory/ContentsXML/oui-patch.xml (權限不夠)'
After fixing the cause of failure Run opatchauto resume
]
OPATCHAUTO-68061: 業務流程引擎失敗。
OPATCHAUTO-68061: 業務流程引擎失敗, 返回代碼為 1
OPATCHAUTO-68061: 有關詳細資料, 請查看日志。
OPatchAuto 失敗。
OPatchauto session completed at Mon Sep 13 17:57:49 2021
Time taken to complete the session 28 minutes, 22 seconds
opatchauto failed with error code 42
[root@db195 ~]#
查看對應的日志/u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-09-13_17-56-51下午_1.log，里面有錯誤號：OUI-67124，但沒啥價值。回到最直觀的這個文件權限錯誤，對比了兩個節點發現節點2這個文件權限確實不一樣，手工更正為和節點1一致：
--/u01/app/oraInventory/ContentsXML/oui-patch.xml
[root@db195 ~]# ls -l /u01/app/oraInventory/ContentsXML/oui-patch.xml
-rw-r--r-- 1 oracle oinstall 174 9月 13 17:56 /u01/app/oraInventory/ContentsXML/oui-patch.xml
[root@db195 ~]#
[root@db195 ~]# chown grid:oinstall /u01/app/oraInventory/ContentsXML/oui-patch.xml
[root@db195 ~]# chmod 664 /u01/app/oraInventory/ContentsXML/oui-patch.xml
[root@db195 ~]# ls -l /u01/app/oraInventory/ContentsXML/oui-patch.xml
-rw-rw-r-- 1 grid oinstall 174 9月 13 17:56 /u01/app/oraInventory/ContentsXML/oui-patch.xml
[root@db195 ~]#
然后按照提示，嘗試繼續應用補丁：
--opatchauto resume
/u01/app/19.3.0/grid/OPatch/opatchauto resume
結果很不幸，依然失敗：
[root@db195 ~]# /u01/app/19.3.0/grid/OPatch/opatchauto resume
OPatchauto session is initiated at Mon Sep 13 19:58:29 2021
會話日志文件是/u01/app/19.3.0/grid/cfgtoollogs/opatchauto/opatchauto2021-09-13_07-58-30PM.log
恢復 ID 為 AMSA 的現有會話
Start applying binary patch on home /u01/app/19.3.0/grid
Failed while applying binary patches on home /u01/app/19.3.0/grid
未能執行 [OPatchAutoBinaryAction] 補丁程序操作, 有關詳細信息, 請查看日志。故障:
Patch Target : db195->/u01/app/19.3.0/grid 類型 [crs]
Details: [
---------------------------Patching Failed---------------------------------
Command execution failed during patching in home: /u01/app/19.3.0/grid, host: db195.
Command failed: /u01/app/19.3.0/grid/OPatch/opatchauto apply /u01/media/32895426 -oh /u01/app/19.3.0/grid -target_type cluster -binary -invPtrLoc /u01/app/19.3.0/grid/oraInst.loc -jre /u01/app/19.3.0/grid/OPatch/jre -persistresult /u01/app/19.3.0/grid/opatchautocfg/db/sessioninfo/sessionresult_db195_crs_1.ser -analyzedresult /u01/app/19.3.0/grid/opatchautocfg/db/sessioninfo/sessionresult_analyze_db195_crs_1.ser
Command failure output:
==Following patches FAILED in apply:
Patch: /u01/media/32895426/32585572
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2021-09-13_19-59-27下午_1.log
Reason: Failed during Analysis: CheckNApplyReport Failed, [ Prerequisite Status: FAILED, Prerequisite output:
The details are:
Unable to create patchObject
Possible causes are:
ORACLE_HOME/inventory/oneoffs/32585572 is corrupted. PatchObject constructor: Input file "/u01/app/19.3.0/grid/inventory/oneoffs/32585572/etc/config/actions" or "/u01/app/19.3.0/grid/inventory/oneoffs/32585572/etc/config/inventory" does not exist.
]
After fixing the cause of failure Run opatchauto resume
]
OPATCHAUTO-68061: 業務流程引擎失敗。
OPATCHAUTO-68061: 業務流程引擎失敗, 返回代碼為 1
OPATCHAUTO-68061: 有關詳細資料, 請查看日志。
OPatchAuto 失敗。
OPatchauto session completed at Mon Sep 13 19:59:40 2021
Time taken to complete the session 1 minute, 11 seconds
這個報錯MOS沒有搜到特別匹配的已知問題，但這個報錯提示明顯，就是缺少文件，同樣去比對兩邊的/u01/app/19.3.0/grid/inventory/oneoffs目錄，將少的文件從1節點cp到2節點：
--節點1目錄下文件夾：
[root@db193 oneoffs]# ls -lrth
總用量 0
drwxr-x--- 4 grid oinstall 29 4月 18 2019 29401763
drwxr-x--- 4 grid oinstall 29 4月 18 2019 29517242
drwxr-x--- 4 grid oinstall 29 4月 18 2019 29517247
drwxr-x--- 4 grid oinstall 29 4月 18 2019 29585399
drwxr-xr-x 4 grid oinstall 29 9月 13 17:04 32585572
drwxr-xr-x 4 grid oinstall 29 9月 13 17:10 32904851
drwxr-xr-x 4 grid oinstall 29 9月 13 17:13 32915586
drwxr-xr-x 4 grid oinstall 29 9月 13 17:15 32916816
drwxr-xr-x 4 grid oinstall 29 9月 13 17:16 32918050
[root@db193 oneoffs]# pwd
/u01/app/19.3.0/grid/inventory/oneoffs
--節點2目錄下文件夾：
[root@db195 oneoffs]# ls -lrth
總用量 0
drwxr-x--- 4 grid oinstall 29 7月 31 2019 29401763
drwxr-x--- 4 grid oinstall 29 7月 31 2019 29517247
drwxr-x--- 4 grid oinstall 29 7月 31 2019 29585399
drwxr-x--- 4 grid oinstall 29 7月 31 2019 29517242
[root@db195 oneoffs]# pwd
/u01/app/19.3.0/grid/inventory/oneoffs
--從節點1用grid用戶拷貝這些缺少的文件夾和內容到節點2后，再次查看：
[grid@db193 oneoffs]$ scp -r 32* db195:/u01/app/19.3.0/grid/inventory/oneoffs/
inventory.xml 100% 2081 715.6KB/s 00:00
actions.xml 100% 2081 667.9KB/s 00:00
inventory.xml 100% 647KB 12.0MB/s 00:00
actions.xml 100% 5337KB 19.2MB/s 00:00
inventory.xml 100% 33KB 7.8MB/s 00:00
actions.xml 100% 84KB 11.5MB/s 00:00
inventory.xml 100% 139KB 9.5MB/s 00:00
actions.xml 100% 232KB 7.5MB/s 00:00
inventory.xml 100% 2197 831.3KB/s 00:00
actions.xml 100% 2651 1.0MB/s 00:00
[root@db195 oneoffs]# ls -lrth
總用量 0
drwxr-x--- 4 grid oinstall 29 7月 31 2019 29401763
drwxr-x--- 4 grid oinstall 29 7月 31 2019 29517247
drwxr-x--- 4 grid oinstall 29 7月 31 2019 29585399
drwxr-x--- 4 grid oinstall 29 7月 31 2019 29517242
drwxr-xr-x 4 grid oinstall 29 9月 13 20:51 32585572
drwxr-xr-x 4 grid oinstall 29 9月 13 20:51 32904851
drwxr-xr-x 4 grid oinstall 29 9月 13 20:51 32915586
drwxr-xr-x 4 grid oinstall 29 9月 13 20:51 32916816
drwxr-xr-x 4 grid oinstall 29 9月 13 20:51 32918050
確保所有文件一致時，此時再次嘗試應用補丁成功，最后可以查詢下補丁應用情況：
--node1@grid
[grid@db193 ~]$ $ORACLE_HOME/OPatch/opatch lspatches
32918050;TOMCAT RELEASE UPDATE 19.0.0.0.0 (32918050)
32916816;OCW RELEASE UPDATE 19.12.0.0.0 (32916816)
32915586;ACFS RELEASE UPDATE 19.12.0.0.0 (32915586)
32904851;Database Release Update : 19.12.0.0.210720 (32904851)
32585572;DBWLM RELEASE UPDATE 19.0.0.0.0 (32585572)
OPatch succeeded.
--node2@grid
[grid@db195 ~]$ $ORACLE_HOME/OPatch/opatch lspatches;
32918050;TOMCAT RELEASE UPDATE 19.0.0.0.0 (32918050)
32916816;OCW RELEASE UPDATE 19.12.0.0.0 (32916816)
32915586;ACFS RELEASE UPDATE 19.12.0.0.0 (32915586)
32904851;Database Release Update : 19.12.0.0.210720 (32904851)
32585572;DBWLM RELEASE UPDATE 19.0.0.0.0 (32585572)
OPatch succeeded.
--node1@oracle
[oracle@db193 ~]$ $ORACLE_HOME/OPatch/opatch lspatches
32916816;OCW RELEASE UPDATE 19.12.0.0.0 (32916816)
32904851;Database Release Update : 19.12.0.0.210720 (32904851)
OPatch succeeded.
--node2@oracle
[oracle@db195 ~]$ $ORACLE_HOME/OPatch/opatch lspatches
32916816;OCW RELEASE UPDATE 19.12.0.0.0 (32916816)
32904851;Database Release Update : 19.12.0.0.210720 (32904851)
OPatch succeeded.
--DB
[oracle@db193 ~]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Mon Sep 13 22:48:34 2021
Version 19.12.0.0.0
Copyright (c) 1982, 2021, Oracle. All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.12.0.0.0
SQL> set lines 1000
SQL> select * from v$version;
BANNER BANNER_FULL BANNER_LEGACY CON_ID
-------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----------
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production 0
Version 19.12.0.0.0
SQL> select * from dba_registry_history;
ACTION_TIME ACTION NAMESPACE VERSION ID COMMENTS BUNDLE_SERIES
--------------------------------------------------------------------------- ------------------------------ ------------------------------ ------------------------------ ---------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------
BOOTSTRAP DATAPATCH 19 RDBMS_19.12.0.0.0DBRU_LINUX.X64_210715
01-AUG-19 02.04.17.106249 AM RU_APPLY SERVER 19.0.0.0.0 Patch applied on 19.3.0.0.0: Release_Update - 190410122720
13-SEP-21 09.54.32.352018 PM RU_APPLY SERVER 19.0.0.0.0 Patch applied from 19.3.0.0.0 to 19.12.0.0.0: Release_Update - 210716141810
SQL>
至此，19c RAC的RU補丁應用完成。