1、登录数据库
[oracle@forest ~]$ . oraenv
ORACLE_SID = [oracle] ? FOREST
The Oracle base has been set to /u01/app/oracle
[oracle@forest ~]$ sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on Fri Oct 18 15:41:12 2024
Version 19.23.0.0.0

Copyright (c) 1982, 2023, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> 

2、启动数据库
SQL> startup
ORACLE instance started.

Total System Global Area 4.2950E+10 bytes
Fixed Size                 23388200 bytes
Variable Size            5502926848 bytes
Database Buffers         3.7313E+10 bytes
Redo Buffers              110825472 bytes
Database mounted.
Database opened.

3、打开pdb
SQL> alter pluggable database all open;

Pluggable database altered.

4、退出
SQL> quit
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.23.0.0.0

5、进入补丁目录
[oracle@forest ~]$ cd $ORACLE_HOME/OPatch

6、执行./datapatch -sanity_checks
[oracle@forest OPatch]$ ./datapatch -sanity_checks
SQL Patching sanity checks version 19.23.0.0.0 on Fri 18 Oct 2024 03:45:05 PM CST
Copyright (c) 2021, 2024, Oracle.  All rights reserved.

Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sanity_checks_20241018_154505_31345/sanity_checks_20241018_154505_31345.log

Running checks
JSON report generated in /u01/app/oracle/cfgtoollogs/sqlpatch/sanity_checks_20241018_154505_31345/sqlpatch_sanity_checks_summary.json file
Checks completed. Printing report:

Check: Database component status - INFO
  There should be no INVALID components prior patching due to risk of potential errors.
  Listed components have a non-valid status.
  Run '?/rdbms/admin/utlrp.sql' (per container) to try recompiling invalid objects and restore component status.
  PDB$SEED:
    | COMPONENT | STATUS  |
    |-----------+---------|
    |    SDO    | INVALID |
    |-----------+---------|
Check: PDB Violations - OK
Check: Invalid System Objects - OK
Check: Tablespace Status - OK
Check: Backup jobs - OK
Check: Temp file exists - OK
Check: Temp file online - OK
Check: Data Pump running - OK
Check: Container status - OK
Check: Oracle Database Keystore - OK
Check: Dictionary statistics gathering - WARNING
  Patching the database while dictionary statistics are being collected may lead to performance issues.
  Dictionary statistics are currently being collected in the database.
  Consider patching the database when dictionary statistics are not being collected. To check if such operations are currently running, run this query:
    SELECT sofar, totalwork, units, start_time, time_remaining, message
    FROM sys.v$session_longops
    WHERE opname = 'Gather Dictionary Schema Statistics'
    AND time_remaining > 0;
  PDB$SEED:
    |     LATEST      |        OPERATION        |
    |-----------------+-------------------------|
    | 17-APR-19 02:03 | gather_dictionary_stats |
    |-----------------+-------------------------|
  PDB2:
    |     LATEST      |        OPERATION        |
    |-----------------+-------------------------|
    | 17-APR-19 02:03 | gather_dictionary_stats |
    |-----------------+-------------------------|
Check: Scheduled Jobs - WARNING
  Execution of scheduler jobs while database patching is running may lead to failures and/or performance issues.
  There are jobs currently running or scheduled to be executed during next hour.
  Consider patching the database when jobs are not running and will not be scheduled to run during patching.
  To check for jobs that are running or scheduled to run:
    SELECT owner as schema_name, job_name, state, next_run_date
    FROM sys.all_scheduler_jobs
    WHERE state = 'RUNNING'
    UNION
      SELECT owner as schema_name, job_name, state, next_run_date
      FROM sys.all_scheduler_jobs
      WHERE state = 'SCHEDULED'
      and cast(next_run_date as date) > sysdate
      and cast(next_run_date as date) < sysdate + 1/24;
Use of uninitialized value in subroutine entry at /u01/app/oracle/product/19.3.0/dbhome_1/sqlpatch/sqlpatch_sanity_checks.pm line 3252.
Use of uninitialized value in subtraction (-) at /u01/app/oracle/product/19.3.0/dbhome_1/sqlpatch/sqlpatch_sanity_checks.pm line 3286.
Use of uninitialized value $rowElem in concatenation (.) or string at /u01/app/oracle/product/19.3.0/dbhome_1/sqlpatch/sqlpatch_sanity_checks.pm line 3287.
Use of uninitialized value in subroutine entry at /u01/app/oracle/product/19.3.0/dbhome_1/sqlpatch/sqlpatch_sanity_checks.pm line 3252.
Use of uninitialized value in subtraction (-) at /u01/app/oracle/product/19.3.0/dbhome_1/sqlpatch/sqlpatch_sanity_checks.pm line 3286.
Use of uninitialized value $rowElem in concatenation (.) or string at /u01/app/oracle/product/19.3.0/dbhome_1/sqlpatch/sqlpatch_sanity_checks.pm line 3287.
  PDB1:
    |      JOB_NAME      | NEXT_RUN_DATE | SCHEMA_NAME |  STATE  |
    |--------------------+---------------+-------------+---------|
    | ORA$AT_OS_OPT_SY_1 |               |     SYS     | RUNNING |
    |--------------------+---------------+-------------+---------|
  PDB2:
    |      JOB_NAME      | NEXT_RUN_DATE | SCHEMA_NAME |  STATE  |
    |--------------------+---------------+-------------+---------|
    | ORA$AT_OS_OPT_SY_1 |               |     SYS     | RUNNING |
    |--------------------+---------------+-------------+---------|
Check: GoldenGate triggers - OK
Check: Logminer DDL triggers - OK
Check: Check sys public grants - OK
Check: Statistics gathering running - OK
Check: Optim dictionary upgrade parameter - OK
Check: Symlinks on oracle home path - OK
Check: Central Inventory - OK
Check: Queryable Inventory dba directories - OK
Check: Queryable Inventory locks - OK
Check: Queryable Inventory package - ERROR
  Datapatch uses Queryable Inventory to get OPatch Inventory information and create a patching installation plan.
  The Queryable Inventory package is not able to retrieve OPatch Inventory information.
  Refer to MOS Note 1602089.1 for details on verifying the Queryable Inventory package before patching.
  CDB$ROOT:
    | RESULT  |
    |---------|
    | Failure |
    |---------|
Check: Queryable Inventory external table - SKIPPED (ERROR)
  Message: Skipped as previous check wasn't executed successfully.
Check: Imperva processes - OK
Check: Guardium processes - OK
Check: Locale - OK

Refer to MOS Note 2680521.1 and debug log
/u01/app/oracle/cfgtoollogs/sqlpatch/sanity_checks_20241018_154505_31345/sanity_checks_debug_20241018_154505_31345.log

SQL Patching sanity checks completed on Fri 18 Oct 2024 03:45:30 PM CST

7、安装补丁数据修补程序
./datapatch -verbose
[oracle@forest OPatch]$ ./datapatch -verbose
SQL Patching tool version 19.23.0.0.0 Production on Fri Oct 18 15:46:31 2024
Copyright (c) 2012, 2024, Oracle.  All rights reserved.

Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_7314_2024_10_18_15_46_31/sqlpatch_invocation.log

Connecting to database...OK
Gathering database info...done

Note:  Datapatch will only apply or rollback SQL fixes for PDBs
       that are in an open state, no patches will be applied to closed PDBs.
       Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation
       (Doc ID 1585822.1)

Bootstrapping registry and package to current versions...done
Determining current state...done

Current state of interim SQL patches:
  No interim patches found

Current state of release update SQL patches:
  Binary registry:
    19.23.0.0.0 Release_Update 240406004238: Installed
  PDB CDB$ROOT:
    Applied 19.3.0.0.0 Release_Update 190410122720 successfully on 16-OCT-24 05.36.55.677813 PM
  PDB PDB$SEED:
    Applied 19.3.0.0.0 Release_Update 190410122720 successfully on 16-OCT-24 05.45.02.081538 PM
  PDB PDB1:
    Applied 19.3.0.0.0 Release_Update 190410122720 successfully on 16-OCT-24 05.45.02.081538 PM
  PDB PDB2:
    Applied 19.3.0.0.0 Release_Update 190410122720 successfully on 16-OCT-24 05.45.02.081538 PM

Adding patches to installation queue and performing prereq checks...done
Installation queue:
  For the following PDBs: CDB$ROOT PDB$SEED PDB1 PDB2
    No interim patches need to be rolled back
    Patch 36233263 (Database Release Update : 19.23.0.0.240416 (36233263)):
      Apply from 19.3.0.0.0 Release_Update 190410122720 to 19.23.0.0.0 Release_Update 240406004238
    No interim patches need to be applied


WARNING: Following components are NOT in a valid state.
         This could cause patching failure. If it does, consider
         running utlrp.sql to bring components to VALID state.
         Then, re-run datapatch.

         PDB$SEED : SDO [INVALID]

Installing patches...
Patch installation complete.  Total patches installed: 4

Validating logfiles...done
Patch 36233263 apply (pdb CDB$ROOT): SUCCESS
  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/36233263/25638263/36233263_apply_FOREST_CDBROOT_2024Oct18_15_48_26.log (no errors)
Patch 36233263 apply (pdb PDB$SEED): SUCCESS
  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/36233263/25638263/36233263_apply_FOREST_PDBSEED_2024Oct18_15_59_39.log (no errors)
Patch 36233263 apply (pdb PDB1): SUCCESS
  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/36233263/25638263/36233263_apply_FOREST_PDB1_2024Oct18_15_59_39.log (no errors)
Patch 36233263 apply (pdb PDB2): SUCCESS
  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/36233263/25638263/36233263_apply_FOREST_PDB2_2024Oct18_15_59_39.log (no errors)

Automatic recompilation incomplete; run utlrp.sql to revalidate.
  PDBs: CDB$ROOT PDB1 PDB2 PDB$SEED

SQL Patching tool complete on Fri Oct 18 16:08:32 2024

8、检查日志错误
Check the following log files in $ORACLE_BASE/cfgtoollogs/sqlpatch/36233263/<unique patch                      ID> for errors:
36233263_apply_<database SID>_<CDB name>_<timestamp>.log

[oracle@forest ~]$ ll -h /u01/app/oracle/cfgtoollogs/sqlpatch/36233263/25638263/36233263_apply_FOREST_CDBROOT_2024Oct18_15_48_26.log 
-rw-r--r--. 1 oracle oinstall 23M Oct 18 15:59 /u01/app/oracle/cfgtoollogs/sqlpatch/36233263/25638263/36233263_apply_FOREST_CDBROOT_2024Oct18_15_48_26.log

9、编译无效对象
export PATH=$PATH:$ORACLE_HOME/bin
cd $ORACLE_HOME/rdbms/admin
$ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catcon.pl -n 1 -e -b utlrp -d $ORACLE_HOME/rdbms/admin utlrp.sql

[oracle@forest ~]$ ll -h $ORACLE_HOME/perl/bin/perl
-rwxr-xr-x. 1 oracle oinstall 3.8M Apr  7  2024 /u01/app/oracle/product/19.3.0/dbhome_1/perl/bin/perl

[oracle@forest ~]$ ll -h $ORACLE_HOME/rdbms/admin/catcon.pl
-rw-r--r--. 1 oracle oinstall 38K Apr  9  2024 /u01/app/oracle/product/19.3.0/dbhome_1/rdbms/admin/catcon.pl

[oracle@forest ~]$ export PATH=$PATH:$ORACLE_HOME/bin
[oracle@forest ~]$ cd $ORACLE_HOME/rdbms/admin

执行命令报错
[oracle@forest admin]$ $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catcon.pl -n 1 -e -b utlrp -d $ORACLE_HOME/rdbms/admin utlrp.sql
catcon::set_log_file_base_path: ALL catcon-related output will be written to [/u01/app/oracle/product/19.3.0/dbhome_1/rdbms/admin/utlrp_catcon_11902.lst]

catcon::set_log_file_base_path: catcon: See [/u01/app/oracle/product/19.3.0/dbhome_1/rdbms/admin/utlrp*.log] files for output generated by scripts

catcon::set_log_file_base_path: catcon: See [/u01/app/oracle/product/19.3.0/dbhome_1/rdbms/admin/utlrp_*.lst] files for spool files, if any

catcon::print_exec_DB_script_output:   ] end of output produced in exec_DB_script

catcon::catconInit2: unexpected error in get_instance_status_and_name

Unexpected error encountered in catconInit2; exiting

[oracle@forest ~]$ . oraenv
ORACLE_SID = [oracle] ? FOREST
The Oracle base has been set to /u01/app/oracle

再次执行不报错，执行成功，环境变量问题
[oracle@forest admin]$ $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catcon.pl -n 1 -e -b utlrp -d $ORACLE_HOME/rdbms/admin utlrp.sql
catcon::set_log_file_base_path: ALL catcon-related output will be written to [/u01/app/oracle/product/19.3.0/dbhome_1/rdbms/admin/utlrp_catcon_24814.lst]

catcon::set_log_file_base_path: catcon: See [/u01/app/oracle/product/19.3.0/dbhome_1/rdbms/admin/utlrp*.log] files for output generated by scripts

catcon::set_log_file_base_path: catcon: See [/u01/app/oracle/product/19.3.0/dbhome_1/rdbms/admin/utlrp_*.lst] files for spool files, if any

catcon.pl: completed successfully

10、升级RMAN catalog目录
$ rman catalog username/password@alias
UPGRADE CATALOG;
UPGRADE CATALOG;

11、Update Permissions for extjob
# chown root $ORACLE_HOME/bin/extjob
# chmod 4750 $ORACLE_HOME/bin/extjob

[root@forest ~]# ll -h /u01/app/oracle/product/19.3.0/dbhome_1/bin/extjob
-rwxr-xr-x. 1 oracle oinstall 2.9M Oct 18 15:35 /u01/app/oracle/product/19.3.0/dbhome_1/bin/extjob

[root@forest ~]# chown root /u01/app/oracle/product/19.3.0/dbhome_1/bin/extjob
[root@forest ~]# chmod 4750 /u01/app/oracle/product/19.3.0/dbhome_1/bin/extjob

[root@forest ~]# ll -h /u01/app/oracle/product/19.3.0/dbhome_1/bin/extjob
-rwsr-x---. 1 root oinstall 2.9M Oct 18 15:35 /u01/app/oracle/product/19.3.0/dbhome_1/bin/extjob

[oracle@forest ~]$ sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on Fri Oct 18 16:29:03 2024
Version 19.23.0.0.0

Copyright (c) 1982, 2023, Oracle.  All rights reserved.


Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.23.0.0.0

SQL> select banner_full from v$version;

BANNER_FULL
--------------------------------------------------------------------------------
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.23.0.0.0


SQL> show pdbs

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
         3 PDB1                           READ WRITE NO
         4 PDB2                           READ WRITE NO

SQL> select action,comments from registry$history;

ACTION
------------------------------
COMMENTS
--------------------------------------------------------------------------------
BOOTSTRAP
RDBMS_19.23.0.0.0DBRU_LINUX.X64_240405

RU_APPLY
Patch applied on 19.3.0.0.0: Release_Update - 190410122720

RU_APPLY
Patch applied from 19.3.0.0.0 to 19.23.0.0.0: Release_Update - 240406004238