How to upgrade to Oracle 19.8 on Windows

Posted by

As always, you should follow the instructions in the README.html that comes with the Release Update, but because I know many people like to see what the experience of others is like, here’s my run of the patch application.

As always don’t forget to run your CMD prompt as Administrator, otherwise OPatch will typically have trouble accessing and locking the software inventory

Prerequisites

Get your environment setup as per the patch notes.


C:\WINDOWS\system32>set ORACLE_SID=db19

C:\WINDOWS\system32>set ORACLE_HOME=C:\oracle\product\19

C:\WINDOWS\system32>set PATH=C:\oracle\product\19\bin;%PATH%

C:\WINDOWS\system32>set PATH=%ORACLE_HOME%\perl\bin;%PATH%

C:\WINDOWS\system32>set PERL5LIB=

C:\WINDOWS\system32>net stop msdtc
The Distributed Transaction Coordinator service is stopping.
The Distributed Transaction Coordinator service was stopped successfully.

Check your OPatch version

For this patch, it needs to be 12.2.0.1.17 or higher. Mine was OK but my general recommendation is to always download the latest OPatch any time you need to use it. Of course, I was lazy here and did not Smile


C:\WINDOWS\system32>set PATH=%ORACLE_HOME%\Opatch;%PATH%

C:\WINDOWS\system32>opatch version
OPatch Version: 12.2.0.1.19

OPatch succeeded.

Apply the patch

Shutdown everything that might be using the Oracle executables in the ORACLE_HOME you are about to patch. Note that on Windows this is more than just running a “shutdown” on the database. You need to go into the Windows Services and ensure any of the Oracle services are also shutdown to ensure nothing is running.

Now when you apply the patch, there is a good chance it is going to fail Smile



D:\>cd D:\oracle\stage\win198\31247621

D:\oracle\stage\win198\31247621>opatch apply
Oracle Interim Patch Installer version 12.2.0.1.19
Copyright (c) 2020, Oracle Corporation.  All rights reserved.


Oracle Home       : C:\oracle\product\19
Central Inventory : C:\Program Files\Oracle\Inventory
   from           :
OPatch version    : 12.2.0.1.19
OUI version       : 12.2.0.7.0
Log file location : C:\oracle\product\19\cfgtoollogs\opatch\opatch2020-08-18_14-41-35PM_1.log

Verifying environment and performing prerequisite checks...

Conflicts/Supersets for each patch are:

Patch : 31247621

        Bug Superset of 30901317
        Super set bugs are:
        29947145, 29968085, 29293072, 29516727, 28774416, 29766679, 30147473, 29631749, 29434301, 29443250, 29643721, 30114534, ....

        Conflict with 30805684
        Conflict details:
        C:\oracle\product\19\rdbms\admin\oracle.sym
        C:\oracle\product\19\bin\oracle.exe


Following patches have conflicts: [   30805684   31247621 ]
Use the MOS Patch Conflict Checker "https://support.oracle.com/epmos/faces/PatchConflictCheck" to resolve.
See MOS documents 1941934.1 and 1299688.1 for additional information and resolution methods.


UtilSession failed: Please rebuild the superset patch [31247621] to make sure it supersedes all the relevant patch(es) [30901317,30805684].
The rebuild patch should contain bug fix [29994370, 29947145, 30834110, 29968085, 29293072, 29516727, 28774416, 29766679, 30147473, 29631749, ...

Log file location: C:\oracle\product\19\cfgtoollogs\opatch\opatch2020-08-18_14-41-35PM_1.log

OPatch failed with error code = 73

It failed because of a conflict with patch 30805684, and it is at this point I found the following line that I should have paid attention to in the patch README:

If Opatch reports conflicts with an earlier version of OJVM Bundle Patch, perform a rollback of the OJVM patch before following below steps.

And yes indeed, 30805684 is my 19.7 OJVM patch. So you’ll need to head off the My Oracle Support and download the 19.8 OJVM as well (patch 31219897).

Rollback the old JVM


D:\oracle\stage\win198\31247621>opatch rollback -id 30805684
Oracle Interim Patch Installer version 12.2.0.1.19
Copyright (c) 2020, Oracle Corporation.  All rights reserved.


Oracle Home       : C:\oracle\product\19
Central Inventory : C:\Program Files\Oracle\Inventory
   from           :
OPatch version    : 12.2.0.1.19
OUI version       : 12.2.0.7.0
Log file location : C:\oracle\product\19\cfgtoollogs\opatch\opatch2020-08-18_14-46-25PM_1.log


Patches will be rolled back in the following order:
   30805684
The following patch(es) will be rolled back: 30805684

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = 'C:\oracle\product\19')


Is the local system ready for patching? [y|n]
y
User Responded with: Y

Rolling back patch 30805684...

RollbackSession rolling back interim patch '30805684' from OH 'C:\oracle\product\19'

Patching component oracle.rdbms, 19.0.0.0.0...

Patching component oracle.rdbms.dbscripts, 19.0.0.0.0...

Patching component oracle.javavm.server, 19.0.0.0.0...

Patching component oracle.javavm.client, 19.0.0.0.0...
RollbackSession removing interim patch '30805684' from inventory
Log file location: C:\oracle\product\19\cfgtoollogs\opatch\opatch2020-08-18_14-46-25PM_1.log

OPatch succeeded.

Now we can try again to apply the patch 🙂

Apply the patch (take 2)

Hopefully this time we’ll make more progress.


D:\oracle\stage\win198\31247621>opatch apply
Oracle Interim Patch Installer version 12.2.0.1.19
Copyright (c) 2020, Oracle Corporation.  All rights reserved.


Oracle Home       : C:\oracle\product\19
Central Inventory : C:\Program Files\Oracle\Inventory
   from           :
OPatch version    : 12.2.0.1.19
OUI version       : 12.2.0.7.0
Log file location : C:\oracle\product\19\cfgtoollogs\opatch\opatch2020-08-18_14-48-02PM_1.log

Verifying environment and performing prerequisite checks...
OPatch continues with these patches:   31247621

Do you want to proceed? [y|n]
y
User Responded with: Y
All checks passed.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = 'C:\oracle\product\19')


Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files...
Applying interim patch '31247621' to OH 'C:\oracle\product\19'
ApplySession: Optional component(s) [ oracle.assistants.usm, 19.0.0.0.0 ] , [ oracle.rdbms.ic, 19.0.0.0.0 ] , [ oracle.rdbms.tg4ifmx, 19.0.0.0.0 ] ....

Patching component oracle.sdo, 19.0.0.0.0...

Patching component oracle.rdbms.rman, 19.0.0.0.0...

Patching component oracle.aspnet_2, 19.0.0.0.0...

Patching component oracle.dbjava.ic, 19.0.0.0.0...

Patching component oracle.ons, 19.0.0.0.0...

Patching component oracle.ntoramts, 19.0.0.0.0...

Patching component oracle.rdbms.dbscripts, 19.0.0.0.0...

Patching component oracle.nlsrtl.rsf, 19.0.0.0.0...

Patching component oracle.xdk.parser.java, 19.0.0.0.0...

Patching component oracle.rdbms, 19.0.0.0.0...

Patching component oracle.blaslapack, 19.0.0.0.0...

Patching component oracle.rdbms.oci, 19.0.0.0.0...

Patching component oracle.assistants.acf, 19.0.0.0.0...

Patching component oracle.duma, 19.0.0.0.0...

Patching component oracle.tfa.db, 19.0.0.0.0...

Patching component oracle.ldap.security.osdt, 19.0.0.0.0...

Patching component oracle.ctx.atg, 19.0.0.0.0...

Patching component oracle.xdk.rsf, 19.0.0.0.0...

Patching component oracle.precomp.common, 19.0.0.0.0...

Patching component oracle.dbjava.jdbc, 19.0.0.0.0...

Patching component oracle.rdbms.hsodbc, 19.0.0.0.0...

Patching component oracle.sqlplus.ic, 19.0.0.0.0...

Patching component oracle.oracore.rsf, 19.0.0.0.0...

Patching component oracle.rsf, 19.0.0.0.0...

Patching component oracle.precomp.common.core, 19.0.0.0.0...

Patching component oracle.network.client, 19.0.0.0.0...

Patching component oracle.precomp.lang, 19.0.0.0.0...

Patching component oracle.install.deinstalltool, 19.0.0.0.0...

Patching component oracle.ctx, 19.0.0.0.0...

Patching component oracle.dbjava.ucp, 19.0.0.0.0...

Patching component oracle.javavm.client, 19.0.0.0.0...

Patching component oracle.network.listener, 19.0.0.0.0...

Patching component oracle.ntoledb.odp_net_2, 19.0.0.0.0...

Patching component oracle.rdbms.util, 19.0.0.0.0...

Patching component oracle.usm.deconfig, 19.0.0.0.0...

Patching component oracle.assistants.server, 19.0.0.0.0...

Patching component oracle.rdbms.deconfig, 19.0.0.0.0...

Patching component oracle.ntoledb, 19.0.0.0.0...

Patching component oracle.has.common, 19.0.0.0.0...

Patching component oracle.assistants.deconfig, 19.0.0.0.0...

Patching component oracle.ldap.rsf, 19.0.0.0.0...

Patching component oracle.ovm, 19.0.0.0.0...

Patching component oracle.has.db, 19.0.0.0.0...

Patching component oracle.rdbms.plsql, 19.0.0.0.0...

Patching component oracle.precomp.rsf, 19.0.0.0.0...

Patching component oracle.javavm.server, 19.0.0.0.0...

Patching component oracle.xdk, 19.0.0.0.0...

Patching component oracle.sdo.locator, 19.0.0.0.0...

Patching component oracle.rdbms.install.plugins, 19.0.0.0.0...

Patching component oracle.rdbms.olap, 19.0.0.0.0...

Patching component oracle.rdbms.scheduler, 19.0.0.0.0...

Patching component oracle.rdbms.rsf.ic, 19.0.0.0.0...

Patching component oracle.ldap.owm, 19.0.0.0.0...

Patching component oracle.rdbms.rsf, 19.0.0.0.0...

Patching component oracle.network.rsf, 19.0.0.0.0...

Patching component oracle.oraolap, 19.0.0.0.0...

Patching component oracle.clrintg.ode_net_2, 19.0.0.0.0...

Patching component oracle.rdbms.dv, 19.0.0.0.0...

Patching component oracle.has.rsf, 19.0.0.0.0...

Patching component oracle.sqlplus, 19.0.0.0.0...

Patching component oracle.has.common.cvu, 19.0.0.0.0...
Patch 31247621 successfully applied.
Sub-set patch [30901317] has become inactive due to the application of a super-set patch [31247621].
Please refer to Doc ID 2161861.1 for any possible further required actions.
Log file location: C:\oracle\product\19\cfgtoollogs\opatch\opatch2020-08-18_14-48-02PM_1.log

OPatch succeeded.

Bring the JVM up to 19.8

We just rolled back the OJVM, so once we’ve downloaded/unzipped the fresh 19.8 version, it is time to apply that.


D:\oracle\stage\win198\31247621>cd D:\oracle\stage\jvm_win_198\31219897

D:\oracle\stage\jvm_win_198\31219897>opatch apply
Oracle Interim Patch Installer version 12.2.0.1.19
Copyright (c) 2020, Oracle Corporation.  All rights reserved.


Oracle Home       : C:\oracle\product\19
Central Inventory : C:\Program Files\Oracle\Inventory
   from           :
OPatch version    : 12.2.0.1.19
OUI version       : 12.2.0.7.0
Log file location : C:\oracle\product\19\cfgtoollogs\opatch\opatch2020-08-18_14-51-28PM_1.log

Verifying environment and performing prerequisite checks...
OPatch continues with these patches:   31219897

Do you want to proceed? [y|n]
y
User Responded with: Y
All checks passed.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = 'C:\oracle\product\19')


Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files...
Applying interim patch '31219897' to OH 'C:\oracle\product\19'

Patching component oracle.rdbms, 19.0.0.0.0...

Patching component oracle.rdbms.dbscripts, 19.0.0.0.0...

Patching component oracle.javavm.server, 19.0.0.0.0...

Patching component oracle.javavm.client, 19.0.0.0.0...
Patch 31219897 successfully applied.
Log file location: C:\oracle\product\19\cfgtoollogs\opatch\opatch2020-08-18_14-51-28PM_1.log

OPatch succeeded.

No problems and it all goes through just fine.

Datapatch

Now that our software is updated, it is time to bring the data dictionary into alignment. In Windows you’ll need to restart all the services to get your databases running.

It is important to remember that datapatch will only patch fully open (ie, read write) pluggables, so if you have customised any of your databases to open only a partial set of pluggables, some of the closed ones might miss out which can make for nasty surprises later on. (Did anyone say “PDB_PLUG_IN_VIOLATIONS”? Smile)

It is often safest just to pop into each container and run a “alter pluggable database all open”.

Note: In the patch notes for the JVM, it says the databases must be opened with “upgrade” mode. I checked with some people internally and this is not required. Hence you can run datapatch to perform both the 19.8 update and the 19.8 OJVM update with a single invocation of datapatch.


c:\oracle\product\19\OPatch>set ORACLE_SID
ORACLE_SID=db19

c:\oracle\product\19\OPatch>datapatch -verbose
SQL Patching tool version 19.3.0.0.0 Production on Tue Aug 18 14:58:01 2020
Copyright (c) 2012, 2019, Oracle.  All rights reserved.

Log file for this invocation: C:\oracle\cfgtoollogs\sqlpatch\sqlpatch_47356_2020_08_18_14_58_01\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:
Interim patch 30805684 (OJVM RELEASE UPDATE: 19.7.0.0.200414 (30805684)):
  Binary registry: Not installed
  PDB CDB$ROOT: Applied successfully on 05-JUN-20 07.29.52.735000 PM
  PDB PDB$SEED: Applied successfully on 05-JUN-20 07.29.54.295000 PM
  PDB PDB1: Applied successfully on 05-JUN-20 07.29.55.855000 PM
Interim patch 31219897 (OJVM RELEASE UPDATE: 19.8.0.0.200714 (31219897)):
  Binary registry: Installed
  PDB CDB$ROOT: Not installed
  PDB PDB$SEED: Not installed
  PDB PDB1: Not installed

Current state of release update SQL patches:
  Binary registry:
    19.8.0.0.0 Release_Update 200724191610: Installed
  PDB CDB$ROOT:
    Applied 19.7.0.0.0 Release_Update 200514113449 successfully on 05-JUN-20 07.29.52.729000 PM
  PDB PDB$SEED:
    Applied 19.7.0.0.0 Release_Update 200514113449 successfully on 05-JUN-20 07.29.54.289000 PM
  PDB PDB1:
    Applied 19.7.0.0.0 Release_Update 200514113449 successfully on 05-JUN-20 07.29.55.852000 PM

Adding patches to installation queue and performing prereq checks...done
Installation queue:
  For the following PDBs: CDB$ROOT PDB$SEED PDB1
    The following interim patches will be rolled back:
      30805684 (OJVM RELEASE UPDATE: 19.7.0.0.200414 (30805684))
    Patch 31247621 (Windows Database Bundle Patch : 19.8.0.0.200714 (31247621)):
      Apply from 19.7.0.0.0 Release_Update 200514113449 to 19.8.0.0.0 Release_Update 200724191610
    The following interim patches will be applied:
      31219897 (OJVM RELEASE UPDATE: 19.8.0.0.200714 (31219897))

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

Validating logfiles...done
Patch 30805684 rollback (pdb CDB$ROOT): SUCCESS
  logfile: C:\oracle\cfgtoollogs\sqlpatch\30805684\23504850/30805684_rollback_DB19_CDBROOT_2020Aug18_14_59_34.log (no errors)
Patch 31247621 apply (pdb CDB$ROOT): SUCCESS
  logfile: C:\oracle\cfgtoollogs\sqlpatch\31247621\23674370/31247621_apply_DB19_CDBROOT_2020Aug18_15_00_05.log (no errors)
Patch 31219897 apply (pdb CDB$ROOT): SUCCESS
  logfile: C:\oracle\cfgtoollogs\sqlpatch\31219897\23690485/31219897_apply_DB19_CDBROOT_2020Aug18_15_00_05.log (no errors)
Patch 30805684 rollback (pdb PDB$SEED): SUCCESS
  logfile: C:\oracle\cfgtoollogs\sqlpatch\30805684\23504850/30805684_rollback_DB19_PDBSEED_2020Aug18_15_00_58.log (no errors)
Patch 31247621 apply (pdb PDB$SEED): SUCCESS
  logfile: C:\oracle\cfgtoollogs\sqlpatch\31247621\23674370/31247621_apply_DB19_PDBSEED_2020Aug18_15_01_09.log (no errors)
Patch 31219897 apply (pdb PDB$SEED): SUCCESS
  logfile: C:\oracle\cfgtoollogs\sqlpatch\31219897\23690485/31219897_apply_DB19_PDBSEED_2020Aug18_15_01_09.log (no errors)
Patch 30805684 rollback (pdb PDB1): SUCCESS
  logfile: C:\oracle\cfgtoollogs\sqlpatch\30805684\23504850/30805684_rollback_DB19_PDB1_2020Aug18_15_00_58.log (no errors)
Patch 31247621 apply (pdb PDB1): SUCCESS
  logfile: C:\oracle\cfgtoollogs\sqlpatch\31247621\23674370/31247621_apply_DB19_PDB1_2020Aug18_15_01_09.log (no errors)
Patch 31219897 apply (pdb PDB1): SUCCESS
  logfile: C:\oracle\cfgtoollogs\sqlpatch\31219897\23690485/31219897_apply_DB19_PDB1_2020Aug18_15_01_09.log (no errors)

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

SQL Patching tool complete on Tue Aug 18 15:02:06 2020

I don’t really know what the “Automatic recompilation incomplete” message means, so I jumped in and ran utlrp.sql manually within the root and each pluggable just in case.



c:\oracle\product\19\OPatch>sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on Tue Aug 18 15:05:29 2020
Version 19.8.0.0.0

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


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

SQL> @?/rdbms/admin/utlrp.sql

Session altered.


TIMESTAMP
----------------------------------------------------------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN              2020-08-18 15:05:40

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 procedure successfully completed.


TIMESTAMP
----------------------------------------------------------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_END              2020-08-18 15:05:52

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


Function created.


PL/SQL procedure successfully completed.


Function dropped.


PL/SQL procedure successfully completed.

SQL> alter session set container = pdb1;

Session altered.

SQL> @?/rdbms/admin/utlrp.sql

Session altered.


TIMESTAMP
----------------------------------------------------------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN              2020-08-18 15:06:29

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 procedure successfully completed.


TIMESTAMP
----------------------------------------------------------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_END              2020-08-18 15:07:10

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

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


Function created.


PL/SQL procedure successfully completed.


Function dropped.


PL/SQL procedure successfully completed.

SQL> exit
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.8.0.0.0

c:\oracle\product\19\OPatch>

And we’re done…A couple of gotchas which were mainly my own fault for not reading the notes carefully enough, but other than that, all smooth sailing…as it I hope it will be for you.

Also, if you are reading this with respect to an earlier version of the database, there are some things about datapatch you need to be aware of, which I’ve covered in the video below

Got some thoughts? Leave a comment

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.