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/grid

OPatchauto session is initiated at Fri Apr 19 10:47:44 2024

System 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 5L8Y

Executing 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/grid


Executing patch validation checks on home /u01/app/19.0.0/grid
Patch validation checks successfully completed on home /u01/app/19.0.0/grid


Performing 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/grid


Start applying binary patch on home /u01/app/19.0.0/grid
 Failed while applying binary patches on home /u01/app/19.0.0/grid

Execution 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 seconds

 opatchauto 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/grid

OPatchauto session is initiated at Fri Apr 19 14:19:02 2024

System 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 63PR

Executing 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/grid


Executing patch validation checks on home /u01/app/19.0.0/grid
Patch validation checks successfully completed on home /u01/app/19.0.0/grid


Performing 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/grid


Start applying binary patch on home /u01/app/19.0.0/grid
Binary patch applied successfully on home /u01/app/19.0.0/grid


Running rootadd_rdbms.sh on home /u01/app/19.0.0/grid
Successfully executed rootadd_rdbms.sh on home /u01/app/19.0.0/grid


Performing 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/grid

OPatchAuto 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.log

Patch: /psu/36233126/36233343
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_14-47-35PM_1.log

Patch: /psu/36233126/36240578
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_14-47-35PM_1.log

Patch: /psu/36233126/36383196
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_14-47-35PM_1.log

Patch: /psu/36233126/36460248
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_14-47-35PM_1.log



OPatchauto 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/grid

OPatchauto session is initiated at Fri Apr 19 15:37:31 2024

System 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 QGP7

Executing 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/grid


Executing patch validation checks on home /u01/app/19.0.0/grid
Patch validation checks successfully completed on home /u01/app/19.0.0/grid


Performing 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/grid


Start applying binary patch on home /u01/app/19.0.0/grid
Binary patch applied successfully on home /u01/app/19.0.0/grid


Running rootadd_rdbms.sh on home /u01/app/19.0.0/grid
Successfully executed rootadd_rdbms.sh on home /u01/app/19.0.0/grid


Performing 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/grid

OPatchAuto 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.log

Patch: /psu/36233126/36233343
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_16-10-13PM_1.log

Patch: /psu/36233126/36240578
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_16-10-13PM_1.log

Patch: /psu/36233126/36383196
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_16-10-13PM_1.log

Patch: /psu/36233126/36460248
Log: /u01/app/19.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_16-10-13PM_1.log



OPatchauto 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_1

OPatchauto session is initiated at Fri Apr 19 16:02:44 2024

System 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 HZVP

Executing 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_1


Executing 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_1


Verifying 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_1


Preparing 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 service


Bringing 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_1


Performing 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_1


Start 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 resume

Invalid 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 HZVP

Start 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_1


Running 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_1


Performing 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_1


Starting 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_1


Preparing 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 home

OPatchAuto 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.log

Patch: /psu/36233126/36240578
Log: /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_19-25-49PM_1.log


Patching 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_1

Invalid 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_1

OPatchauto session is initiated at Fri Apr 19 20:59:20 2024

System 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 T4GS

Executing 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_1


Executing 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_1


Verifying 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_1


Preparing 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 service


Bringing 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_1


Performing 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_1


Start 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_1


Running 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_1


Performing 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_1


Starting 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_1


Preparing 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_1

OPatchAuto 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.log

Patch: /psu/36233126/36240578
Log: /u01/app/oracle/product/19.0.0/db_1/cfgtoollogs/opatchauto/core/opatch/opatch2024-04-19_21-47-14PM_1.log



OPatchauto 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@bak

Recovery Manager: Release 19.0.0.0.0 - Production on Fri Apr 19 16:09:00 2024
Version 19.23.0.0.0

Copyright (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 current

RMAN>  UPGRADE CATALOG;

recovery catalog owner is CATUSER
enter UPGRADE CATALOG command again to confirm catalog upgrade

RMAN> 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 

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

如若内容造成侵权/违法违规/事实不符，请联系我们进行投诉反馈qq邮箱809451989@qq.com，一经查实，立即删除！

相关文章

AI：165-Coze自定义赛博风格Bot-图片生成操作指南

AI：165-Coze自定义赛博风格Bot-图片生成操作指南

Coze是由字节跳动推出的一个AI聊天机器人和应用程序编辑开发平台&#xff0c;旨在帮助用户快速创建各种类型的聊天机器人、智能体、AI应用和插件&#xff0c;并将其部署在社交平台和即时聊天应用程序中&#xff0c;如Discord、WhatsApp、Twitter、飞书、微信公众号等。 这个平…
阅读更多...
计算机网络3——数据链路层3以太网的MAC层

计算机网络3——数据链路层3以太网的MAC层

文章目录 一、MAC 层的硬件地址1、介绍2、注意点3、定制标准 二、MAC 帧的格式1、结构2、工作原理3、其他 一、MAC 层的硬件地址 1、介绍 在局域网中&#xff0c;硬件地址又称为物理地址或 MAC地址(因为这种地址用在MAC帧中)。 大家知道&#xff0c;在所有计算机系统的设计中…
阅读更多...
剑指Offer题目笔记32（拓扑排序）

剑指Offer题目笔记32（拓扑排序）

面试题113&#xff1a; 解决方案&#xff1a; 将课程看成图中的节点&#xff0c;如果两门课程存在先修顺序那么它们在图中对应的节点之间存在一条从先修课程到后修课程的边&#xff0c;因此这是一个有向图。可行的修课序列实际上是图的拓扑排序序列。图中的每条边都是从先修课…
阅读更多...
C++并发编程

C++并发编程

基本介绍 线程 C98标准没有直接提供原生的多线程支持 在C98中&#xff0c;并没有像后来的C11标准中那样的<thread>库或其他直接的多线程工具 然而&#xff0c;这并不意味着在C98中无法实现多线程。开发者通常会使用平台特定的API&#xff08;如Windows的线程API或POSI…
阅读更多...
前端开发攻略---用原生JS在网页中也能实现 文本转语音！

前端开发攻略---用原生JS在网页中也能实现 文本转语音！

1、原理 语音合成 (也被称作是文本转为语音&#xff0c;英语简写是 tts) 包括接收 app 中需要语音合成的文本&#xff0c;再在设备麦克风播放出来这两个过程。 Web API中对此有一个主要控制接口 SpeechSynthesis&#xff0c;外加一些处理如何表示要被合成的文本 (也被称为 utte…
阅读更多...
玩转微服务-SonarQube

玩转微服务-SonarQube

这里写目录标题 第一节 SonarQube1.1 简介1.2 四个组成部分1.2.1 SonarQube服务器1.2.2 SonarQube数据库1.2.3 插件1.2.4 Scanner 1.3 工作流程 第二节 SonarQube的安装2.1 安装2.2 插件 第三节 P3C规范3.1 简介3.2 SonarQube 配置 P3C规范3.3 IDEA配置 P3C规范 第四节 Maven项…
阅读更多...
机器学习-期末复习

机器学习-期末复习

本文的内容按照作者的课程考试要求书写&#xff0c;仅供复习参考。&#x1f337;&#x1f337;&#x1f337;欢迎大家指正&#xff01; 机器学习是一种人工智能&#xff08;AI&#xff09;的分支领域&#xff0c;它致力于开发能够通过数据学习和改进的算法和模型。简而言之&…
阅读更多...
2024年AIGC+教育行业报告

2024年AIGC+教育行业报告

在宏观层面上&#xff0c;如果把人工智能看作一种生命体&#xff0c;AIGC教育的内涵其实是碳基生命和硅基生命的 交互和培育问题。AIGC技术是对人脑计算、思考、判断等内在能力的延伸&#xff0c;是人的智能在机器形态 上的规模化聚集、运作和反应。由此&#xff0c;部分基础性…
阅读更多...
【漏洞复现】云时空社会化商业ERP系统LoginName SQL注入漏洞

【漏洞复现】云时空社会化商业ERP系统LoginName SQL注入漏洞

漏洞描述&#xff1a; 云时空社会化商业ERP系统loginName存在SQL注入漏洞&#xff0c;攻击者可以通过此漏洞获取数据库敏感信息。 搜索语法: Fofa-Query: app"云时空社会化商业ERP系统" 漏洞详情&#xff1a; 1.云时空社会化商业ERP系统。 2.漏洞POC&#xff1a…
阅读更多...
倒计时开始！Big Demo Day第十二期，揭秘DePIN，探索Web3未来（附参会指南）

倒计时开始！Big Demo Day第十二期，揭秘DePIN，探索Web3未来（附参会指南）

香港—— 全球领先的 Web3.0 活动 Big Demo Day 第十二期即将于 4 月 26 日在香港数码港盛大举行。本次活动由知名科技企业 ZeeprLabs 赞助&#xff0c;Central Research 主办&#xff0c;并得到 Techub News 的联合主办以及数码港、852Web3 等机构的合作支持。 在过去的 11 期…
阅读更多...
鸿蒙HarmonyOS应用 - ArkUI组件

鸿蒙HarmonyOS应用 - ArkUI组件

ArkUI组件 基础组件 Image 声明Image组件并设置图片源 网络权限&#xff1a;ohos.permission.INTERNET Image(scr: string | PixelMap | Resource)// 1. string&#xff1a;用于加载网络图片&#xff0c;需要申请网络权限 Image("https://xxx.png")// 2. PixelMap…
阅读更多...
驱鸟器低成本OTP语音方案选型-wtn6020唯创知音

驱鸟器低成本OTP语音方案选型-wtn6020唯创知音

一、开发背景&#xff1a; 随着农业现代化的不断推进&#xff0c;鸟类对农作物的侵扰问题愈发严重。传统的驱鸟方法&#xff0c;如人工驱赶或使用化学药剂&#xff0c;不仅效率低下&#xff0c;而且可能对环境造成污染。因此&#xff0c;开发一种高效、环保、低成本的驱鸟器成…
阅读更多...
考研日常记录（upd 24.4.24）

考研日常记录（upd 24.4.24）

由于实在太无聊了 &#xff0c; 所以记录以下考研备考日常 &#xff0c; 增加一点成就感 &#xff0c; 获得一点前进动力。 文章目录 2024.4.18 周四课程情况&#xff1a;时间规划&#xff1a; 2024.4.19 周五课程情况&#xff1a;时间规划&#xff1a; 2024.4.20 周六2024.4.2…
阅读更多...
RK3588构建ubuntu22.04根文件系统

RK3588构建ubuntu22.04根文件系统

前言 RK系列的平台提供了buildroot和debian的系统&#xff0c;使用脚本可以直接构建出来&#xff0c;但是没有提供ubuntu的系统&#xff0c;很多厂商只提供一个rootfs.img的固件包&#xff0c;没有将方法开源出来。本文实现了从ubuntu官网开始构建一个ubuntu22.04根文件系统。…
阅读更多...
SSTV音频转图片

SSTV音频转图片

SSTV工具有很多&#xff0c;这里使用RX-SSTV慢扫描工具 下载安装 RX-SSTV解码软件 下载地址&#xff1a;https://www.qsl.net/on6mu/rxsstv.htm 一直点下一步&#xff0c;安装成功如下图: 虚拟声卡e2eSoft 由于SSTV工具是根据音频传递图片信息&#xff0c;正常解法需要一…
阅读更多...
人耳的七个效应

人耳的七个效应

1、掩蔽效应 • 人们在安静环境中能够分辨出轻微的声音&#xff0c;即人耳对这个声音的听域很低&#xff0c;但在嘈杂的环境中轻微的声音就会被淹没掉&#xff0c;这时将轻微的声音增强才能听到。 • 这种在聆听时&#xff0c;一个声音的听阈因另一声音的出现而提高的现象&…
阅读更多...
本地修改localhost--手把手

本地修改localhost--手把手

找到本地hosts文件 1、C:\Windows\System32\drivers–快捷键ctrlR,输入drivers 2、点击etc目录&#xff0c;找到hosts文件&#xff0c;右键使用记事本方式打开编辑 3、添加自己想得到的域名【只能在本地使用】 127.0.0.1 eureka7001.com 127.0.0.1 eureka7002.com 127.0.0.…
阅读更多...
面试：JVM内存结构

面试：JVM内存结构

一、Java代码的运行步骤 一段Java代码先会被反编译为Java字节码&#xff0c;当执行java命令时&#xff0c;JVM虚拟机会被创建出来&#xff0c;并会创建一个main主线程来执行主方法。 二、JVM的内存结构有哪些&#xff1f; 1、方法区&#xff1a;&#xff08;线程共享&#xff…
阅读更多...
Linux交换空间的创建使用

Linux交换空间的创建使用

交换空间&#xff1a; 换出&#xff1a;将内存中不常用&#xff08;冷数据&#xff09;的放去硬盘里 换出&#xff1a;内存要使用这部分数据时&#xff0c;将硬盘的这部分数据放入内存 在内存和硬盘上用来交换数据的空间就是交换空间 创建交换空间的步骤 1.去磁盘上创建一个分…
阅读更多...
Linux中的高级IO函数（一）pipe socketpair dup

Linux中的高级IO函数（一）pipe socketpair dup

Linux提供了很多高级的I/O函数。它们并不像Linux基础I/O函数&#xff08;比如open和read&#xff09;那么常用&#xff08;编写内核模块时一般要实现这些I/O函数&#xff09;&#xff0c;但在特定的条件下却表现出优秀的性能。这些函数大致分为三类&#xff1a; 用于创建文件描…
阅读更多...
最新文章

Copyright @ 2022~2023

友情链接： 我的编程经验分享 一条长河网 尧图网站开发 尧图建网站