RU 19.23 安装

2024-04-22 14:52
文章标签 安装 ru 19.23

本文主要是介绍RU 19.23 安装,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

分别通过对GRID_HOME和ORACLE_HOME进行安装补丁的方式。来安装RU19.23 。
前面的相关检查等步骤,略。
安装RU的过程
1 分别最GRID_HOME安装RU
2 分别对ORACLE_HOME安装RU
3 升级catalog (如有必要)
4 其他事项


1 对GRID HOME安装ru

# opatchauto apply <UNZIPPED_PATCH_LOCATION>/36233126 -oh <GI_HOME>
# /u01/app/19.0.0/grid/OPatch/opatchauto apply /psu/36233126 -oh /u01/app/19.0.0/gr

安装过程 :
此过程出现错误,查看log,原因为RU中的一些文件无法读取,修复后,resume继续补丁,产生新的问题,fuser命令查看一些文件被占用。 
放弃resume方式,重新一个会话打RU,问题解决。

[root@node19c01 OPatch]# /u01/app/19.0.0/grid/OPatch/opatchauto apply /psu/36233126 -oh /u01/app/19.0.0/gridOPatchauto session is initiated at Fri Apr 19 10:47:44 2024System initialization log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2024-04-19_10-48-03AM.log.Session log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/opatchauto2024-04-19_10-48-38AM.log
The id for this session is 5L8YExecuting OPatch prereq operations to verify patch applicability on home /u01/app/19.0.0/grid
Patch applicability verified successfully on home /u01/app/19.0.0/gridExecuting patch validation checks on home /u01/app/19.0.0/grid
Patch validation checks successfully completed on home /u01/app/19.0.0/gridPerforming prepatch operations on CRS - bringing down CRS service on home /u01/app/19.0.0/grid
Prepatch operation log file location: /u01/app/grid/crsdata/node19c01/crsconfig/crs_prepatch_apply_inplace_node19c01_2024-04-19_11-14-24AM.log
CRS service brought down successfully on home /u01/app/19.0.0/gridStart applying binary patch on home /u01/app/19.0.0/gridFailed while applying binary patches on home /u01/app/19.0.0/gridExecution of [OPatchAutoBinaryAction] patch action failed, check log for more details. Failures:
Patch Target : node19c01->/u01/app/19.0.0/grid Type[crs]
Details: [
---------------------------Patching Failed---------------------------------
Command execution failed during patching in home: /u01/app/19.0.0/grid, host: node19c01.
Command failed:  /u01/app/19.0.0/grid/OPatch/opatchauto  apply /psu/36233126 -oh /u01/app/19.0.0/grid -target_type cluster -binary -invPtrLoc /u01/app/19.0.0/grid/oraInst.loc -jre /u01/app/19.0.0/grid/OPatch/jre -persistresult /u01/app/19.0.0/grid/opatchautocfg/db/sessioninfo/sessionresult_node19c01_crs_1.ser -analyzedresult /u01/app/19.0.0/grid/opatchautocfg/db/sessioninfo/sessionresult_analyze_node19c01_crs_1.ser
Command failure output:
==Following patches FAILED in apply:Patch: /psu/36233126/36233263
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_11-15-36AM_1.log
Reason: Failed during Patching: oracle.opatch.opatchsdk.OPatchException:
Prerequisite check "CheckApplicable" failed.Patch: /psu/36233126/36233343
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_11-15-36AM_1.log
Reason: Failed during Patching: oracle.opatch.opatchsdk.OPatchException:
Prerequisite check "CheckApplicable" failed.Patch: /psu/36233126/36240578
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_11-15-36AM_1.log
Reason: Failed during Patching: oracle.opatch.opatchsdk.OPatchException:
Prerequisite check "CheckApplicable" failed.Patch: /psu/36233126/36383196
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_11-15-36AM_1.log
Reason: Failed during Patching: oracle.opatch.opatchsdk.OPatchException:
Prerequisite check "CheckApplicable" failed.Patch: /psu/36233126/36460248
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_11-15-36AM_1.log
Reason: Failed during Patching: oracle.opatch.opatchsdk.OPatchException:
Prerequisite check "CheckApplicable" failed.After fixing the cause of failure Run opatchauto resume]
OPATCHAUTO-68061: The orchestration engine failed.
OPATCHAUTO-68061: The orchestration engine failed with return code 1
OPATCHAUTO-68061: Check the log for more details.
OPatchAuto failed.OPatchauto session completed at Fri Apr 19 11:40:59 2024
Time taken to complete the session 52 minutes, 57 secondsopatchauto failed with error code 42
[root@node19c01 OPatch]# 

-- 错误log, log中显示,找不到一些文件。

[Apr 19, 2024 11:40:40 AM] [INFO]   Prereq checkPatchApplicableOnCurrentPlatform Passed on patch :36460248
[Apr 19, 2024 11:40:57 AM] [INFO]   Patch 36240578:Copy Action: Source File "/psu/36233126/36240578/files/bin/ocrcheck.bin" does not exists or is not readable'oracle.has.crs, 19.0.0.0.0': Cannot copy file from 'ocrcheck.bin' to '/u01/app/19.0.0/grid/bin/ocrcheck.bin'Copy Action: Source File "/psu/36233126/36240578/files/bin/ocrconfig.bin" does not exists or is not readable'oracle.has.crs, 19.0.0.0.0': Cannot copy file from 'ocrconfig.bin' to '/u01/app/19.0.0/grid/bin/ocrconfig.bin'
[Apr 19, 2024 11:40:57 AM] [INFO]   Prerequisite check "CheckApplicable" failed.The details are:Patch 36240578:Copy Action: Source File "/psu/36233126/36240578/files/bin/ocrcheck.bin" does not exists or is not readable'oracle.has.crs, 19.0.0.0.0': Cannot copy file from 'ocrcheck.bin' to '/u01/app/19.0.0/grid/bin/ocrcheck.bin'Copy Action: Source File "/psu/36233126/36240578/files/bin/ocrconfig.bin" does not exists or is not readable'oracle.has.crs, 19.0.0.0.0': Cannot copy file from 'ocrconfig.bin' to '/u01/app/19.0.0/grid/bin/ocrconfig.bin'
[Apr 19, 2024 11:40:57 AM] [SEVERE] OUI-67073:UtilSession failed:Prerequisite check "CheckApplicable" failed.
[Apr 19, 2024 11:40:57 AM] [INFO]   Finishing UtilSession at Fri Apr 19 11:40:57 CST 2024
[root@node19c01 bin]# ls -l /psu/36233126/36240578/files/bin/ocrcheck.bin
-rwx------ 1 root oinstall 1096600 Apr 12 10:03 /psu/36233126/36240578/files/bin/ocrcheck.bin
[root@node19c01 bin]#

-- 以下会用到su -m -c 命令,  切换到grid用户后,grid用户无权限访问ocrcheck.bin 。

2024-04-19 13:14:15,631 INFO  [283] com.oracle.glcm.patch.auto.db.product.executor.GISystemCall - Return code: 0
2024-04-19 13:14:15,631 INFO  [283] com.oracle.glcm.patch.auto.db.integration.controller.action.OPatchAutoBinaryAction -
Executing command as grid:/u01/app/19.0.0/grid/OPatch/opatchauto  apply /psu/36233126 -oh /u01/app/19.0.0/grid -target_type cluster -binary -invPtrLoc /u01/app/19.0.0/grid/oraInst.loc -jre /u01/app/19.0.0/grid/OPatch/jre -persistresult /u01/app/19.0.0/grid/opatchautocfg/db/sessioninfo/sessionresult_node19c01_crs_1.ser -analyzedresult /u01/app/19.0.0/grid/opatchautocfg/db/sessioninfo/sessionresult_analyze_node19c01_crs_1.ser
2024-04-19 13:14:15,631 INFO  [283] com.oracle.glcm.patch.auto.db.integration.controller.action.OPatchAutoBinaryAction - Updating perl path as /u01/app/19.0.0/grid/opatchautocfg/db/dbtmp/bootstrap_node19c01/perl/bin/perl
2024-04-19 13:14:15,631 INFO  [283] com.oracle.glcm.patch.auto.db.product.executor.GISystemCall - System Call command is: [/bin/su, grid, -m, -c, /u01/app/19.0.0/grid/OPatch/opatchauto  apply /psu/36233126 -oh /u01/app/19.0.0/grid -target_type cluster -binary -invPtrLoc /u01/app/19.0.0/grid/oraInst.loc -jre /u01/app/19.0.0/grid/OPatch/jre -persistresult /u01/app/19.0.0/grid/opatchautocfg/db/sessioninfo/sessionresult_node19c01_crs_1.ser -analyzedresult /u01/app/19.0.0/grid/opatchautocfg/db/sessioninfo/sessionresult_analyze_node19c01_crs_1.ser]

-- 一些文件被占用 
 

[Apr 19, 2024 2:14:05 PM] [INFO]    Finish fuser command /sbin/fuser /u01/app/19.0.0/grid/lib/libsqlplus.so at Fri Apr 19 14:14:05 CST 2024
[Apr 19, 2024 2:14:06 PM] [INFO]    Following active files/executables/libs are used by ORACLE_HOME :/u01/app/19.0.0/grid/u01/app/19.0.0/grid/bin/oracle/u01/app/19.0.0/grid/bin/tnslsnr/u01/app/19.0.0/grid/lib/libclntsh.so.19.1/u01/app/19.0.0/grid/lib/libasmclntsh19.so
[Apr 19, 2024 2:14:06 PM] [INFO]    Prerequisite check "CheckActiveFilesAndExecutables" failed.The details are:Following active files/executables/libs are used by ORACLE_HOME :/u01/app/19.0.0/grid/u01/app/19.0.0/grid/bin/oracle/u01/app/19.0.0/grid/bin/tnslsnr/u01/app/19.0.0/grid/lib/libclntsh.so.19.1/u01/app/19.0.0/grid/lib/libasmclntsh19.so
[Apr 19, 2024 2:14:22 PM] [SEVERE]  OUI-67073:UtilSession failed: Prerequisite check "CheckActiveFilesAndExecutables" failed.
[Apr 19, 2024 2:14:22 PM] [INFO]    Finishing UtilSession at Fri Apr 19 14:14:22 CST 2024
[Apr 19, 2024 2:14:22 PM] [INFO]    Log file location: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_13-47-01PM_1.log

重新打补丁,成功 

[root@node19c01 OPatch]# /u01/app/19.0.0/grid/OPatch/opatchauto apply /psu/36233126 -oh /u01/app/19.0.0/gridOPatchauto session is initiated at Fri Apr 19 14:19:02 2024System initialization log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2024-04-19_02-19-20PM.log.Session log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/opatchauto2024-04-19_02-19-44PM.log
The id for this session is 63PRExecuting OPatch prereq operations to verify patch applicability on home /u01/app/19.0.0/grid
Patch applicability verified successfully on home /u01/app/19.0.0/gridExecuting patch validation checks on home /u01/app/19.0.0/grid
Patch validation checks successfully completed on home /u01/app/19.0.0/gridPerforming prepatch operations on CRS - bringing down CRS service on home /u01/app/19.0.0/grid
Prepatch operation log file location: /u01/app/grid/crsdata/node19c01/crsconfig/crs_prepatch_apply_inplace_node19c01_2024-04-19_02-46-21PM.log
CRS service brought down successfully on home /u01/app/19.0.0/gridStart applying binary patch on home /u01/app/19.0.0/grid
Binary patch applied successfully on home /u01/app/19.0.0/gridRunning rootadd_rdbms.sh on home /u01/app/19.0.0/grid
Successfully executed rootadd_rdbms.sh on home /u01/app/19.0.0/gridPerforming postpatch operations on CRS - starting CRS service on home /u01/app/19.0.0/grid
Postpatch operation log file location: /u01/app/grid/crsdata/node19c01/crsconfig/crs_postpatch_apply_inplace_node19c01_2024-04-19_03-23-32PM.log
CRS service started successfully on home /u01/app/19.0.0/gridOPatchAuto successful.--------------------------------Summary--------------------------------Patching is completed successfully. Please find the summary as follows:Host:node19c01
CRS Home:/u01/app/19.0.0/grid
Version:19.0.0.0.0
Summary:==Following patches were SUCCESSFULLY applied:Patch: /psu/36233126/36233263
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_14-47-35PM_1.logPatch: /psu/36233126/36233343
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_14-47-35PM_1.logPatch: /psu/36233126/36240578
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_14-47-35PM_1.logPatch: /psu/36233126/36383196
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_14-47-35PM_1.logPatch: /psu/36233126/36460248
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_14-47-35PM_1.logOPatchauto session completed at Fri Apr 19 15:29:31 2024
Time taken to complete the session 70 minutes, 12 seconds
[root@node19c01 OPatch]#
[root@node19c02 psu]#
[root@node19c02 psu]# /u01/app/19.0.0/grid/OPatch/opatchauto apply /psu/36233126 -oh /u01/app/19.0.0/gridOPatchauto session is initiated at Fri Apr 19 15:37:31 2024System initialization log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2024-04-19_03-37-42PM.log.Session log file is /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/opatchauto2024-04-19_03-38-03PM.log
The id for this session is QGP7Executing OPatch prereq operations to verify patch applicability on home /u01/app/19.0.0/grid
Patch applicability verified successfully on home /u01/app/19.0.0/gridExecuting patch validation checks on home /u01/app/19.0.0/grid
Patch validation checks successfully completed on home /u01/app/19.0.0/gridPerforming prepatch operations on CRS - bringing down CRS service on home /u01/app/19.0.0/grid
Prepatch operation log file location: /u01/app/grid/crsdata/node19c02/crsconfig/crs_prepatch_apply_inplace_node19c02_2024-04-19_04-08-46PM.log
CRS service brought down successfully on home /u01/app/19.0.0/gridStart applying binary patch on home /u01/app/19.0.0/grid
Binary patch applied successfully on home /u01/app/19.0.0/gridRunning rootadd_rdbms.sh on home /u01/app/19.0.0/grid
Successfully executed rootadd_rdbms.sh on home /u01/app/19.0.0/gridPerforming postpatch operations on CRS - starting CRS service on home /u01/app/19.0.0/grid
Postpatch operation log file location: /u01/app/grid/crsdata/node19c02/crsconfig/crs_postpatch_apply_inplace_node19c02_2024-04-19_04-55-00PM.log
CRS service started successfully on home /u01/app/19.0.0/gridOPatchAuto successful.--------------------------------Summary--------------------------------Patching is completed successfully. Please find the summary as follows:Host:node19c02
CRS Home:/u01/app/19.0.0/grid
Version:19.0.0.0.0
Summary:==Following patches were SUCCESSFULLY applied:Patch: /psu/36233126/36233263
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_16-10-13PM_1.logPatch: /psu/36233126/36233343
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_16-10-13PM_1.logPatch: /psu/36233126/36240578
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_16-10-13PM_1.logPatch: /psu/36233126/36383196
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_16-10-13PM_1.logPatch: /psu/36233126/36460248
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_16-10-13PM_1.logOPatchauto session completed at Fri Apr 19 17:09:31 2024
Time taken to complete the session 91 minutes, 50 seconds
[root@node19c02 psu]#

2 对ORACLE_HOME安装RU,其中一个节点,安装一半后,中断了,resume后继续。
 

# opatchauto apply <UNZIPPED_PATCH_LOCATION>/36233126 -oh <oracle_home1_path>,<oracle_home2_path># /u01/app/oracle/product/19.0.0/db_1/OPatch/opatchauto apply /psu/36233126 -oh /u01/app/oracle/product/19.0.0/db_1
[root@node19c01 OPatch]# /u01/app/oracle/product/19.0.0/db_1/OPatch/opatchauto apply /psu/36233126 -oh /u01/app/oracle/product/19.0.0/db_1OPatchauto session is initiated at Fri Apr 19 16:02:44 2024System initialization log file is /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchautodb/systemconfig2024-04-19_04-02-56PM.log.Session log file is /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/opatchauto2024-04-19_04-03-34PM.log
The id for this session is HZVPExecuting OPatch prereq operations to verify patch applicability on home /u01/app/oracle/product/19.0.0/db_1
Patch applicability verified successfully on home /u01/app/oracle/product/19.0.0/db_1Executing patch validation checks on home /u01/app/oracle/product/19.0.0/db_1
Patch validation checks successfully completed on home /u01/app/oracle/product/19.0.0/db_1Verifying SQL patch applicability on home /u01/app/oracle/product/19.0.0/db_1
SQL patch applicability verified successfully on home /u01/app/oracle/product/19.0.0/db_1Preparing to bring down database service on home /u01/app/oracle/product/19.0.0/db_1
Successfully prepared home /u01/app/oracle/product/19.0.0/db_1 to bring down database serviceBringing down database service on home /u01/app/oracle/product/19.0.0/db_1
Database service successfully brought down on home /u01/app/oracle/product/19.0.0/db_1Performing prepatch operation on home /u01/app/oracle/product/19.0.0/db_1
Prepatch operation completed successfully on home /u01/app/oracle/product/19.0.0/db_1Start applying binary patch on home /u01/app/oracle/product/19.0.0/db_1

-- 中断后resume方式继续打补丁,最后提示,实例未启动,sqlpatch要手工处理

/u01/app/oracle/product/19.0.0/db_1/OPatch/opatchauto resume [root@node19c01 ~]# /u01/app/oracle/product/19.0.0/db_1/OPatch/opatchauto resumeInvalid current directory.  Please run opatchauto from other than '/root' or '/' directory.
And check if the home owner user has write permission set for the current directory.
opatchauto returns with error code = 2
[root@node19c01 ~]# cd /
[root@node19c01 /]# /u01/app/oracle/product/19.0.0/db_1/OPatch/opatchauto resume
Session log file is /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/opatchauto2024-04-19_07-20-20PM.log
Resuming existing session with id HZVPStart applying binary patch on home /u01/app/oracle/product/19.0.0/db_1
Binary patch applied successfully on home /u01/app/oracle/product/19.0.0/db_1Running rootadd_rdbms.sh on home /u01/app/oracle/product/19.0.0/db_1
Successfully executed rootadd_rdbms.sh on home /u01/app/oracle/product/19.0.0/db_1Performing postpatch operation on home /u01/app/oracle/product/19.0.0/db_1
Postpatch operation completed successfully on home /u01/app/oracle/product/19.0.0/db_1Starting database service on home /u01/app/oracle/product/19.0.0/db_1
Database service successfully started on home /u01/app/oracle/product/19.0.0/db_1Preparing home /u01/app/oracle/product/19.0.0/db_1 after database service restarted
No step execution required.........Trying to apply SQL patch on home /u01/app/oracle/product/19.0.0/db_1
No SQL patch operations are required on local node for this homeOPatchAuto successful.--------------------------------Summary--------------------------------Patching is completed successfully. Please find the summary as follows:Host:node19c01
RAC Home:/u01/app/oracle/product/19.0.0/db_1
Version:19.0.0.0.0
Summary:==Following patches were SKIPPED:Patch: /psu/36233126/36233343
Reason: This patch is not applicable to this specified target type - "rac_database"Patch: /psu/36233126/36383196
Reason: This patch is not applicable to this specified target type - "rac_database"Patch: /psu/36233126/36460248
Reason: This patch is not applicable to this specified target type - "rac_database"==Following patches were SUCCESSFULLY applied:Patch: /psu/36233126/36233263
Log: /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_19-25-49PM_1.logPatch: /psu/36233126/36240578
Log: /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_19-25-49PM_1.logPatching session reported following warning(s):
_________________________________________________[WARNING] The database instance 'test1' from '/u01/app/oracle/product/19.0.0/db_1', in host'node19c01' 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.OPatchauto session completed at Fri Apr 19 20:55:06 2024
Time taken to complete the session 95 minutes, 12 seconds
[root@node19c01 /]#
[root@node19c02 36233126]# cd ~
[root@node19c02 ~]# /u01/app/oracle/product/19.0.0/db_1/OPatch/opatchauto apply /psu/36233126 -oh /u01/app/oracle/product/19.0.0/db_1Invalid current directory.  Please run opatchauto from other than '/root' or '/' directory.
And check if the home owner user has write permission set for the current directory.
opatchauto returns with error code = 2
[root@node19c02 ~]# pwd
/root
[root@node19c02 ~]# cd /
[root@node19c02 /]# /u01/app/oracle/product/19.0.0/db_1/OPatch/opatchauto apply /psu/36233126 -oh /u01/app/oracle/product/19.0.0/db_1OPatchauto session is initiated at Fri Apr 19 20:59:20 2024System initialization log file is /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchautodb/systemconfig2024-04-19_08-59-36PM.log.Session log file is /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/opatchauto2024-04-19_09-00-12PM.log
The id for this session is T4GSExecuting OPatch prereq operations to verify patch applicability on home /u01/app/oracle/product/19.0.0/db_1
Patch applicability verified successfully on home /u01/app/oracle/product/19.0.0/db_1Executing patch validation checks on home /u01/app/oracle/product/19.0.0/db_1
Patch validation checks successfully completed on home /u01/app/oracle/product/19.0.0/db_1Verifying SQL patch applicability on home /u01/app/oracle/product/19.0.0/db_1
SQL patch applicability verified successfully on home /u01/app/oracle/product/19.0.0/db_1Preparing to bring down database service on home /u01/app/oracle/product/19.0.0/db_1
Successfully prepared home /u01/app/oracle/product/19.0.0/db_1 to bring down database serviceBringing down database service on home /u01/app/oracle/product/19.0.0/db_1
Following database(s) and/or service(s) are stopped and will be restarted later during the session: test
Database service successfully brought down on home /u01/app/oracle/product/19.0.0/db_1Performing prepatch operation on home /u01/app/oracle/product/19.0.0/db_1
Prepatch operation completed successfully on home /u01/app/oracle/product/19.0.0/db_1Start applying binary patch on home /u01/app/oracle/product/19.0.0/db_1
Binary patch applied successfully on home /u01/app/oracle/product/19.0.0/db_1Running rootadd_rdbms.sh on home /u01/app/oracle/product/19.0.0/db_1
Successfully executed rootadd_rdbms.sh on home /u01/app/oracle/product/19.0.0/db_1Performing postpatch operation on home /u01/app/oracle/product/19.0.0/db_1
Postpatch operation completed successfully on home /u01/app/oracle/product/19.0.0/db_1Starting database service on home /u01/app/oracle/product/19.0.0/db_1
Database service successfully started on home /u01/app/oracle/product/19.0.0/db_1Preparing home /u01/app/oracle/product/19.0.0/db_1 after database service restarted
No step execution required.........Trying to apply SQL patch on home /u01/app/oracle/product/19.0.0/db_1
SQL patch applied successfully on home /u01/app/oracle/product/19.0.0/db_1OPatchAuto successful.--------------------------------Summary--------------------------------Patching is completed successfully. Please find the summary as follows:Host:node19c02
RAC Home:/u01/app/oracle/product/19.0.0/db_1
Version:19.0.0.0.0
Summary:==Following patches were SKIPPED:Patch: /psu/36233126/36233343
Reason: This patch is not applicable to this specified target type - "rac_database"Patch: /psu/36233126/36383196
Reason: This patch is not applicable to this specified target type - "rac_database"Patch: /psu/36233126/36460248
Reason: This patch is not applicable to this specified target type - "rac_database"==Following patches were SUCCESSFULLY applied:Patch: /psu/36233126/36233263
Log: /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_21-47-14PM_1.logPatch: /psu/36233126/36240578
Log: /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_21-47-14PM_1.logOPatchauto session completed at Fri Apr 19 22:29:27 2024
Time taken to complete the session 89 minutes, 52 seconds
[root@node19c02 /]#

3  升级catalog  

[oracle@19ctest OPatch]$ rman target / catalog catuser/oracle@bakRecovery Manager: Release 19.0.0.0.0 - Production on Fri Apr 19 16:09:00 2024
Version 19.23.0.0.0Copyright (c) 1982, 2019, Oracle and/or its affiliates.  All rights reserved.connected to target database: CDBTEST (DBID=895265717)
connected to recovery catalog database
PL/SQL package CATUSER.DBMS_RCVCAT version 19.21.00.00. in RCVCAT database is not current
PL/SQL package CATUSER.DBMS_RCVMAN version 19.21.00.00 in RCVCAT database is not currentRMAN>  UPGRADE CATALOG;recovery catalog owner is CATUSER
enter UPGRADE CATALOG command again to confirm catalog upgradeRMAN> UPGRADE CATALOG;recovery catalog upgraded to version 19.23.00.00.00
DBMS_RCVMAN package upgraded to version 19.23.00.00
DBMS_RCVCAT package upgraded to version 19.23.00.00.RMAN> 

4 一些问题 
问题1 : 打补丁过程中出现问题,查看日志,原因为文件无法访问,将文件属性更改为777后,问题消失
问题2 : resume打补丁过程,报错,发现一些文件被$ORACLE_HOME占用了,不使用resume方式打补丁,重新打补丁(会重新开一个补丁会话), 问题消失 
问题3 : 在给oracle用户的ORACLE_HOME安装RU的时候,下班要带走测试电脑,中断补丁过程,随后再次resume,可以正常打补丁
问题4 : 在resume恢复补丁会话的时候,明确提示,Invalid current directory.  Please run opatchauto from other than '/root' or '/' directory.
问题5 : 分别对grid和oracle用户的ORACLE_HOME打补丁后,不再需要运行./datapatch (补丁过程中已执行)
 

END 

这篇关于RU 19.23 安装的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!


原文地址:
本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处:http://www.chinasem.cn/article/926078

相关文章

JAVA中安装多个JDK的方法

《JAVA中安装多个JDK的方法》文章介绍了在Windows系统上安装多个JDK版本的方法,包括下载、安装路径修改、环境变量配置(JAVA_HOME和Path),并说明如何通过调整JAVA_HOME在... 首先去oracle官网下载好两个版本不同的jdk(需要登录Oracle账号,没有可以免费注册)下载完

Java JDK1.8 安装和环境配置教程详解

《JavaJDK1.8安装和环境配置教程详解》文章简要介绍了JDK1.8的安装流程,包括官网下载对应系统版本、安装时选择非系统盘路径、配置JAVA_HOME、CLASSPATH和Path环境变量,... 目录1.下载JDK2.安装JDK3.配置环境变量4.检验JDK官网下载地址:Java Downloads

SQL server数据库如何下载和安装

《SQLserver数据库如何下载和安装》本文指导如何下载安装SQLServer2022评估版及SSMS工具,涵盖安装配置、连接字符串设置、C#连接数据库方法和安全注意事项,如混合验证、参数化查... 目录第一步:打开官网下载对应文件第二步:程序安装配置第三部:安装工具SQL Server Manageme

Python中win32包的安装及常见用途介绍

《Python中win32包的安装及常见用途介绍》在Windows环境下,PythonWin32模块通常随Python安装包一起安装,:本文主要介绍Python中win32包的安装及常见用途的相关... 目录前言主要组件安装方法常见用途1. 操作Windows注册表2. 操作Windows服务3. 窗口操作

gitlab安装及邮箱配置和常用使用方式

《gitlab安装及邮箱配置和常用使用方式》:本文主要介绍gitlab安装及邮箱配置和常用使用方式,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录1.安装GitLab2.配置GitLab邮件服务3.GitLab的账号注册邮箱验证及其分组4.gitlab分支和标签的

MySQL MCP 服务器安装配置最佳实践

《MySQLMCP服务器安装配置最佳实践》本文介绍MySQLMCP服务器的安装配置方法,本文结合实例代码给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考下... 目录mysql MCP 服务器安装配置指南简介功能特点安装方法数据库配置使用MCP Inspector进行调试开发指

在Windows上使用qemu安装ubuntu24.04服务器的详细指南

《在Windows上使用qemu安装ubuntu24.04服务器的详细指南》本文介绍了在Windows上使用QEMU安装Ubuntu24.04的全流程:安装QEMU、准备ISO镜像、创建虚拟磁盘、配置... 目录1. 安装QEMU环境2. 准备Ubuntu 24.04镜像3. 启动QEMU安装Ubuntu4

Python UV安装、升级、卸载详细步骤记录

《PythonUV安装、升级、卸载详细步骤记录》:本文主要介绍PythonUV安装、升级、卸载的详细步骤,uv是Astral推出的下一代Python包与项目管理器,主打单一可执行文件、极致性能... 目录安装检查升级设置自动补全卸载UV 命令总结 官方文档详见:https://docs.astral.sh/

Nexus安装和启动的实现教程

《Nexus安装和启动的实现教程》:本文主要介绍Nexus安装和启动的实现教程,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录一、Nexus下载二、Nexus安装和启动三、关闭Nexus总结一、Nexus下载官方下载链接:DownloadWindows系统根

Java SWT库详解与安装指南(最新推荐)

《JavaSWT库详解与安装指南(最新推荐)》:本文主要介绍JavaSWT库详解与安装指南,在本章中,我们介绍了如何下载、安装SWTJAR包,并详述了在Eclipse以及命令行环境中配置Java... 目录1. Java SWT类库概述2. SWT与AWT和Swing的区别2.1 历史背景与设计理念2.1.