19c数据库打补丁 34133642，升级至 19.16

升级数据库软件

[oracle@iyoume08 admin]$ cd /u01/34133642/

[oracle@iyoume08 34133642]$ $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -ph ./

Oracle Interim Patch Installer version 12.2.0.1.32

PREREQ session

Oracle Home : /u01/app/oracle/product/19c/db

Central Inventory : /u01/app/oraInventory

from : /u01/app/oracle/product/19c/db/oraInst.loc

OPatch version : 12.2.0.1.32

OUI version : 12.2.0.7.0

Log file location : /u01/app/oracle/product/19c/db/cfgtoollogs/opatch/opatch2022-09-16_15-11-50PM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.

[oracle@iyoume08 34133642]$ $ORACLE_HOME/OPatch/opatch apply

Oracle Interim Patch Installer version 12.2.0.1.32

Oracle Home : /u01/app/oracle/product/19c/db

Central Inventory : /u01/app/oraInventory

from : /u01/app/oracle/product/19c/db/oraInst.loc

OPatch version : 12.2.0.1.32

OUI version : 12.2.0.7.0

Log file location : /u01/app/oracle/product/19c/db/cfgtoollogs/opatch/opatch2022-09-16_15-09-37PM_1.log

Verifying environment and performing prerequisite checks...

Skip patch 34133642 from list of patches to apply: This patch is not needed.

After skipping patches with missing components, there are no patches to apply.

OPatch Session completed with warnings.

Log file location: /u01/app/oracle/product/19c/db/cfgtoollogs/opatch/opatch2022-09-16_15-09-37PM_1.log

OPatch completed with warnings.

[oracle@iyoume08 34133642]$ sqlplus -v

SQL*Plus: Release 19.0.0.0.0 - Production

Version 19.16.0.0.0

升级数据库实例

[oracle@iyoume08 34133642]$ lsnrctl start

LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 16-92022 15:15:22

/u01/app/oracle/product/19c/db/bin/tnslsnr: .

TNSLSNR for Linux: Version 19.0.0.0.0 - Production

ϵͳΪ/u01/app/oracle/product/19c/db/network/admin/listener.ora

д01/app/oracle/diag/tnslsnr/iyoume08/listener/alert/log.xml־

: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=iyoume08)(PORT=1521)))

: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))

DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=iyoume08)(PORT=1521)))

LISTENER TATUS

------------------------

LISTENER

TNSLSNR for Linux: Version 19.0.0.0.0 - Production

16-92022 15:15:38

ʱ 0 Сʱ 0 0 off

ON: Local OS Authentication

SNMP OFF

/u01/app/oracle/product/19c/db/network/admin/listener.ora

/u01/app/oracle/diag/tnslsnr/iyoume08/listener/alert/log.xml

...

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=iyoume08)(PORT=1521)))

(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))

[oracle@iyoume08 34133642]$ sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on 6 15:16:09 2022

Version 19.16.0.0.0

SQL> startup;

ORACLE

Total System Global Area 843052528 bytes

Fixed Size 8902128 bytes

Variable Size 583008256 bytes

Database Buffers 247463936 bytes

Redo Buffers 3678208 bytes

SQL> exit

racle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

Version 19.16.0.0.0

[oracle@iyoume08 34133642]$ $ORACLE_HOME/OPatch/datapatch -verbose

SQL Patching tool version 19.16.0.0.0 Production on Fri Sep 16 15:17:45 2022

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

Connecting to database...OK

Gathering database info...done

Bootstrapping registry and package to current versions...done

Determining current state...done

Current state of interim SQL patches:

Interim patch 33192694 (OJVM RELEASE UPDATE: 19.13.0.0.211019 (33192694)):

Binary registry: Installed

SQL registry: Applied successfully on 01-922 06.54.49.078053

Current state of release update SQL patches:

Binary registry:

19.16.0.0.0 Release_Update 220703022223: Installed

SQL registry:

Applied 19.3.0.0.0 Release_Update 190410122720 successfully on 01-922 05.36.28.975780

Adding patches to installation queue and performing prereq checks...done

Installation queue:

No interim patches need to be rolled back

Patch 34133642 (Database Release Update : 19.16.0.0.220719 (34133642)):

Apply from 19.3.0.0.0 Release_Update 190410122720 to 19.16.0.0.0 Release_Update 220703022223

No interim patches need to be applied

Installing patches...

Patch installation complete. Total patches installed: 1

Validating logfiles...done

Patch 34133642 apply: SUCCESS

logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/34133642/24865470/34133642_apply_IYOUME08_2022Sep16_15_24_43.log (no errors)

SQL Patching tool complete on Fri Sep 16 15:44:15 2022

[oracle@iyoume08 34133642]$ cd $ORACLE_HOME/rdbms/admin

[oracle@iyoume08 admin]$ sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on 6 15:44:41 2022

Version 19.16.0.0.0

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

Version 19.16.0.0.0

SQL> @utlrp.sql

TIMESTAMP

--------------------------------------------------------------------------------

COMP_TIMESTAMP UTLRP_BGN 2022-09-16 15:44:53

DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalid

DOC> objects in the database. Recompilation time is proportional to the

DOC> number of invalid objects in the database, so this command may take

DOC> a long time to execute on a database with a large number of invalid

DOC> objects.

DOC>

DOC> Use the following queries to track recompilation progress:

DOC>

DOC> 1. Query returning the number of invalid objects remaining. This

DOC> number should decrease with time.

DOC> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);

DOC>

DOC> 2. Query returning the number of objects compiled so far. This number

DOC> should increase with time.

DOC> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;

DOC>

DOC> This script automatically chooses serial or parallel recompilation

DOC> based on the number of CPUs available (parameter cpu_count) multiplied

DOC> by the number of threads per CPU (parameter parallel_threads_per_cpu).

DOC> On RAC, this number is added across all RAC nodes.

DOC>

DOC> UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel

DOC> recompilation. Jobs are created without instance affinity so that they

DOC> can migrate across RAC nodes. Use the following queries to verify

DOC> whether UTL_RECOMP jobs are being created and run correctly:

DOC>

DOC> 1. Query showing jobs created by UTL_RECOMP

DOC> SELECT job_name FROM dba_scheduler_jobs

DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';

DOC>

DOC> 2. Query showing UTL_RECOMP jobs that are running

DOC> SELECT job_name FROM dba_scheduler_running_jobs

DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';

DOC>#

PL/SQL

TIMESTAMP

--------------------------------------------------------------------------------

COMP_TIMESTAMP UTLRP_END 2022-09-16 15:44:54

DOC> The following query reports the number of invalid objects.

DOC>

DOC> If the number is higher than expected, please examine the error

DOC> messages reported with each object (using SHOW ERRORS) to see if they

DOC> point to system misconfiguration or resource constraints that must be

DOC> fixed before attempting to recompile these objects.

DOC>#

OBJECTS WITH ERRORS

-------------------

0

DOC> The following query reports the number of exceptions caught during

DOC> recompilation. If this number is non-zero, please query the error

DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors

DOC> are due to misconfiguration or resource constraints that must be

DOC> fixed before objects can compile successfully.

DOC> Note: Typical compilation errors (due to coding errors) are not

DOC> logged into this table: they go into DBA_ERRORS instead.

DOC>#

ERRORS DURING RECOMPILATION

---------------------------

0

SQL> select comments,action from registry$history;

COMMENTS

--------------------------------------------------------------------------------

ACTION

------------------------------

RDBMS_19.16.0.0.0DBRU_LINUX.X64_220701

BOOTSTRAP

Patch applied on 19.3.0.0.0: Release_Update - 190410122720

RU_APPLY

Patch applied from 19.3.0.0.0 to 19.16.0.0.0: Release_Update - 220703022223

RU_APPLY

SQL> shutdown immediate;

жORACLE SQL>

升级数据库实例
升级数据库软件

ꄴ前一个：无

ꄲ后一个：无

19c数据库打补丁 34133642，升级至 19.16

全部评论 (0)