Use these troubleshooting tips to address errors or issues that you may encounter while upgrading your database.
Also review the related links to learn about changes that affect this release, which may be related to errors you receive, and to see how to rerun the upgrade after you resolve errors.
About Starting Oracle Database in Upgrade Mode
When you start Oracle Database in upgrade mode, you can only run queries on fixed views. If you attempt to run other views or PL/SQL, then you receive the errors described here.
When the database is started in upgrade mode, only queries on fixed views execute without errors until after you run the Parallel Upgrade Utility (
catctl.pldirectly, or with the
dbupgrade script). Before running an upgrade script, queries on any other view or the use of PL/SQL returns an error.
Errors described in this section can occur when you attempt to start the new Oracle Database release. Some of these errors write to the alert log, and not to your session. If you receive any of these errors, then issue the
SHUTDOWN ABORT command to shut down the database and correct the problem.
ORA-00401: the value for parameter compatible is not supported by this release
COMPATIBLEinitialization parameter is set to a value less than
ORA-39701: database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE
CLUSTER_DATABASEinitialization parameter is set to
ORA-39700: database must be opened with UPGRADE option
STARTUPcommand was issued without the
Ora-00704: bootstrap failure
The path variable can be pointing to the earlier release Oracle home.
ORA-00336: log file size xxxx blocks is less than minimum 8192 blocks
A redo log file size is less than 4 MB.
If errors appear listing desupported initialization parameters, then make a note of the desupported initialization parameters and continue with the upgrade. Remove the desupported initialization parameters the next time you shut down the database.
Running DBUA with Different ORACLE_HOME Owner
Review this topic if your Oracle Database homes are owned by different operating system user accounts, or you encounter an upgrade.xml not found error.
DBUA upgrades by default assume that both the source (release earlier than Oracle Database 12c) Oracle home and the destination (new 12c) Oracle home are owned by the same user. If each Oracle home is not owned by the same user, then you must change to database file permissions and pass additional parameters to DBUA. If you do not do this, then during upgrade, the DBUA Prerequisite Checks page reports upgrade.xml not found errors. You are not permitted to proceed with the upgrade until this error is corrected.
All Oracle Database installation owners should have the group that you designate as the OINSTALL group (or Oracle Inventory group) as their primary group. Ensure all database files (data files, the redo file, control files, archive log destination, recovery area, SPFILE, and password file) are readable and writable by both the new 12c and pre-12c binary owners. If this is not the case, then confirm that each installation owner has the same group as their primary group, and ensure that members of the OINSTALL group have read/write access to all the earlier release and later release Oracle Database files and directories.
Run DBUA by specifying the
-logdircommand line option, and provide a directory to which both the new release and earlier release binary owners can write. For example:
/tmp. DBUA uses the directory you designate with the logdir parameter to store the output from the Pre-upgrade Information Tool, and to store any DBUA log files generated during the upgrade. You run the Pre-Upgrade Information tool from the earlier release Oracle Database instance as the earlier release Oracle Database installation owner user account.
dbua -logdir /tmp
Invalid Object Warnings and DBA Registry Errors
Before you start your upgrade, Oracle strongly recommends that you run the preupgrade information tool (
The preupgrade information tool identifies invalid SYS and SYSTEM objects, as well as other invalid objects. Use
utlrp.sql to recompile invalid objects. If you fail to do this before an upgrade, then it becomes difficult to determine which objects in your system were invalid before starting the upgrade, and which objects become invalid as a result of the upgrade.
Invalid Objects and Premature Use of Postupgrade Tool
Never run the postupgrade status tool for the new Oracle Database release (
utlu122s.sql) until after you complete the upgrade.
Oracle recommends that you run the postupgrade status tool only after the upgrade process is complete, and after you have run
utlrp.sql. If the postupgrade status tool is run before you run
@utlrp.sql, then the output of tool may not display the accurate final component status value. If the tool is run before running
utlrp.sql, then the component status values may not properly reflect the final state. You can only determine the final component state after running
Resolving Oracle Database Upgrade Script Termination Errors
Review this section if you encounter ORA-00942, ORA-00904, or ORA-01722 errors.
If you do not run the Pre-Upgrade Information Tool before starting the upgrade, then the
catupgrd.sql scripts terminate with errors as follows:
ORA-00942: table or view does not exist ORA-00904: "TZ_VERSION": invalid identifier ORA-01722: invalid number
If you receive any of these errors, then complete the following procedure:
SHUTDOWN ABORTcommand, and wait for the command to complete running.
Revert to the original Oracle home directory
Run the Pre-Upgrade Information Tool.
Troubleshooting Causes of Resource Limits Errors while Upgrading Oracle Database
Review this section if you encounter ORA-01650, ORA-01651, ORA-01652, ORA-01653, ORA-01654, ORA-01655, ORA-0431, ORA-01562, ORA-19815, or other errors that suggest resource limit errors.
If you run out of resources during an upgrade, then increase the resource allocation. After increasing the resource allocation, shut down the instance with SHUTDOWN ABORT, and restart the instance in UPGRADE mode before re-running the
The resources that generally require increases for a new Oracle Database release are as follows:
SYSTEMtablespace size is insufficient, then typically you receive the following error message:
ORA-01650: unable to extend rollback segment string by string in tablespace string ORA-01651: unable to extend save undo segment by string for tablespace string ORA-01652: unable to extend temp segment by string in tablespace string ORA-01653: unable to extend table string.string by string in tablespace string ORA-01654: unable to extend index string.string by string in tablespace string ORA-01655: unable to extend cluster string.string by string in tablespace string
To avoid these errors, set
AUTOEXTEND ON MAXSIZE UNLIMITEDfor the
In some cases, you may require larger shared memory pool sizes. The error message indicates which shared memory initialization parameter you must increase, in the following format:
ORA-04031: unable to allocate string bytes of shared memory ("string","string","string","string")
Oracle Database Administrator's Guide for information about using manual shared memory management
Rollback segments/undo tablespace
If you are using rollback segments, then you must have a single large (100 MB)
PUBLICrollback segment online while the upgrade scripts are being run. Smaller public rollback segments should be taken offline during the upgrade. If your rollback segment size is insufficient, then typically you encounter the following error:
ORA-01562: failed to extend rollback segment number string
If you are using an undo tablespace, then be sure it is at least 400 MB.
Fast Recovery Area
If you are using a Fast Recovery Area and it fills up during the upgrade, then the following error appears in the alert log, followed by suggestions for recovering from the problem:
ORA-19815: WARNING: db_recovery_file_dest_size of string bytes is 98.99% used, and has string remaining bytes available.
Identify the root cause of the problem, and take appropriate actions to proceed with the upgrade. To avoid issues during the upgrade, increase the amount of space available in your Fast Recovery Area before starting the upgrade.
Resolving SQL*Plus Edition Session Startup Error for Oracle Database
Use this section to understand and resolve SP2–1540: "Oracle Database cannot startup in an Edition session."
If an upgrade script or a command running in SQL*Plus set the EDITION parameter, then Oracle Database cannot start properly afterward. When you attempt to start the database, you receive the following error:
SP2-1540: "Oracle Database cannot startup in an Edition session"
To avoid this problem, after running
catugrd.sql or any SQL*Plus session where this parameter is changed, exit the SQL*Plus session and restart the instance in a different session.
Error ORA-00020 Maximum Number of Processes Exceeded When Running utlrp.sql
This error may indicate that your Oracle configuration does not have sufficient number of processes available for the recompile.
Refer to Oracle documentation for more details about setting the PROCESSES parameter.
Fixing ORA-01822 with DBMS_DST Package After Upgrades
Use this procedure to fix ORA-01822 and ORA-16512 errors involving time zone file mismatches.
DBMS_DST package after upgrading to Oracle Database 12c can result in an
ORA-01882: time zone region not found error.
This error is returned if the time zone file version is set incorrectly. An incorrect time zone setting results in the region IDs of several time zone regions being stored incorrectly in the database. For example:
ERROR at line 1: @ ORA-01882: time zone region not found @ ORA-06512: at "SYS.DBMS_DST", line 113 @ ORA-06512: at "SYS.DBMS_DST", line 1101 @ ORA-06512: at line 1
To fix this problem, update the time zone version, and re-run the upgrade.
Fixing ORA-28365: Wallet Is Not Open Error
If you use Oracle wallet with Transparent Data Encryption (TDE), and you use Database Upgrade Assistant (DBUA) to upgrade the database, then you can encounter an ORA-28365 "wallet is not open" error.
- Log in as an authorized user.
- Manually copy the
sqlnet.orafile, and the wallet file,
ewallet.p12, to the new release Oracle home.
- Open the Oracle wallet in mount.
SQL> STARTUP MOUNT; SQL> ALTER SYSTEM SET ENCRYPTION WALLET OPEN
- Start the upgrade as usual.
Resolving issues with view CDB_JAVA_POLICY
If the view CDB_JAVA_POLICY becomes invalid, then use this procedure.
After an upgrade to Oracle Database 12c release 2 (12.2) and later releases, or a downgrade from release 12.2 or later releases to 12.1, you can encounter issues with the CDB_JAVA_POLICY view. CDB_JAVA_POLICY can become invalid, or it can encounter errors when you use it in a manner that normally works. If this happens, then connect as SYS, and run the following commands.
alter session set "_ORACLE_SCRIPT"=true; exec CDBView.create_cdbview(false,'SYS','dba_java_policy','CDB_java_policy'); grant select on SYS.CDB_java_policy to select_catalog_role / create or replace public synonym CDB_java_policy for SYS.CDB_java_policy /
Multitenant architecture systems:
Run these same commands, but run them first in CDB$ROOT, and then in other containers in the CDB.
Continuing Upgrades After Server Restarts (ADVM/ACFS Driver Error)
On Windows platforms, an error may occur related to ADVM or ACFS drivers if a server restarts during an upgrade.
If a server restarts during the upgrade, then you may see one of the following error messages:
ACFS-9427: Failed to unload ADVM/ACFS drivers. A system reboot is recommended
ACFS-9428 Failed to load ADVM/ACFS drivers. A system reboot is recommended.
The ADVM and ACFS drivers are still in use. You must restart the system to start the new drivers.
Complete the steps as described in the following procedures.
For nodes other than the first node (the node on which the upgrade is started):
Restart the node where the error occurs.
Run the root script on that node again.
For first nodes (the node on which the upgrade is started):
Complete the upgrade of all other nodes in the cluster.
Restart the first node.
Run the root script on the first node again.
To complete the upgrade, log in as root, and run the script
configToolAllCommands, located in the path
Oracle Grid Infrastructure Installation Guide for your operating system for more information about troubleshooting upgrade issues for clusters
Component Status and Upgrades
Component status settings are affected both by the components that you previously installed, and by the support of those components for upgrades.
Understanding Component Status With the Post-Upgrade Status Tool
The Post-Upgrade Status tool,
utlu122s.sql, reports database component status after an upgrade is completed.
You can run the Post-Upgrade Status Tool
utlu122s.sql anytime after upgrade, post-upgrade, or after recompiling invalid objects with
The following list briefly describes the status values that the Post-Upgrade Status tool reports:
When the upgrade completed, some objects for the component remained in an invalid state. If you find no errors in the log file for component upgrades then run the script
utlrp.sql. Running this script may change the status of invalid components to
VALIDwithout rerunning the entire upgrade. Check the
DBA_REGISTRYview after running
The component is valid with no errors.
The component is loading
The component has successfully finished loading.
The component is in process being upgraded.
The component has completed upgrading with no errors.
The component is in process being downgraded.
The component has completed downgrading with no errors.
The component is in process being removed.
The component was not upgraded because it was removed from the database.
The server option required for the component was not installed or was not linked with the server. Check the
V$OPTIONview and the install logs. Install the component or relink the server with the required option, and then re-run the Parallel Upgrade Utility.
The component upgrade script was not found in $ORACLE_HOME. Check the install logs, install the component software, and then re-run the Parallel Upgrade Utility.
You can run the Parallel Upgrade Utility (
catctl.pl using the command-line scripts
dbupgrade on Linux and UNIX, and
dbupgrade.cmd on Windows) .
Component OPTION OFF Status and Upgrades
The upgrade status of
OPTION OFF components is affected both by the support in the target release for a component, and if a component must be upgraded as part of an upgrade.
There are three cases where OPTION OFF components are upgraded, or are not upgraded.
Unsupported Components With Status
If there is a component in the database that is in the status OPTION OFF, and that component is no longer supported for database upgrades to the target release, then this component is not upgraded. After the upgrade, its version and status remain unchanged..
Supported Components With Status
If there is a component in the database that is in the status
OPTION OFF, but that component is supported for database upgrades to the target release, then this component is upgraded. After the upgrade, the component’s version matches the target release version. The status for this component is either
UPGRADED (a successful upgrade), or
INVALID (errors). Rerun the upgrade as needed, until all the upgraded components have a status of
UPGRADED. Then run
utlrp.sql. If a component was in the status
OPTION OFF before the upgrade, then after it is upgraded, and its compile and validation is successful, its status reverts back to OPTION OFF.
Supported Components With Required Options That Must Be Upgraded
Starting with Oracle Database 18.1, all components with required options must be upgraded. These components are:
Components that must be upgraded follow the same procedure for upgrades as for standard supported components with status
Example of an Upgrade Summary Report
Upgrade summary reports provide information about the upgrade status of components.
After the upgrade completes, starting with Oracle Database 12c release 2, the upgrade utility script (for example, in 12.2 and 18c,
utlu1212.sql) writes a copy of the report using the following write order:
Linux and UNIX:
If the utility script cannot create the report under the first directory scheme, then it attempts to write to the second location, and then the third location. If it cannot write to any of these paths, then it does not write an upgrade summary report. This example is from Oracle Database 18c.
Example 3-40 Upgrade Summary Report for the Post-Upgrade Status Tool
Oracle Database Release 18 Post-Upgrade Status Tool 05-27-2018 23:41:0 Component Current Full Elapsed Time Name Status Version HH:MM:SS Oracle Server UPGRADED 22.214.171.124.0 00:18:21 JServer JAVA Virtual Machine UPGRADED 126.96.36.199.0 00:04:31 Oracle XDK UPGRADED 188.8.131.52.0 00:00:51 Oracle Database Java Packages UPGRADED 184.108.40.206.0 00:00:22 OLAP Analytic Workspace UPGRADED 220.127.116.11.0 00:00:51 Oracle Label Security UPGRADED 18.104.22.168.0 00:00:20 Oracle Database Vault UPGRADED 22.214.171.124.0 00:00:40 Oracle Text UPGRADED 126.96.36.199.0 00:01:37 Oracle Workspace Manager UPGRADED 188.8.131.52.0 00:01:10 Oracle Real Application Clusters UPGRADED 184.108.40.206.0 00:00:00 Oracle XML Database UPGRADED 220.127.116.11.0 00:02:17 Oracle Multimedia UPGRADED 18.104.22.168.0 00:03:01 Spatial UPGRADED 22.214.171.124.0 00:06:23 Oracle OLAP API UPGRADED 126.96.36.199.0 00:00:22 Upgrade Datapatch 00:00:10 Final Actions 00:00:20 Post Upgrade 00:00:05 Post Upgrade Datapatch 00:00:04 Total Upgrade Time: 00:41:45
Standard Edition Starter Database and Components with Status OPTION OFF
Starting in Oracle Database 18c (18.1), all
OPTION OFF components are upgraded to the new release, but these options are disabled for Oracle Database Standard Edition (SE) remain OPTION OFF.
When you upgrade Oracle Database Standard Edition (SE) starter databases, the components that are not included with starter databases are turned on and upgraded. When
utlrp.sql is run, options that are not turned on with your server and not included with SE are reset to
OPTION OFF in the
Adjusting Oracle ASM Password File Location After Upgrade
You must create a new password file for Oracle ASM after an Oracle Grid Infrastructure upgrade.
The Oracle ASM password file location is not shown in the command output when you run
srvctl config asm after a Grid Infrastructure upgrade. The location of the password file is not automatically passed to the new Oracle ASM disk group. To enable SRVCTL to have the password file location after upgrade, you must advance the diskgroup compatibility setting and create a PWFILE in the disk group. Then SRVCTL reports the configured location of the shared PWFILE.
Oracle Automatic Storage Management Administrator's Guide for information about managing shared password files in disk groups
Fixing "Warning XDB Now Invalid" Errors with Pluggable Database Upgrades
Review this topic if you encounter "Warning: XDB now invalid, invalid objects found” errors when upgrading pluggable databases (PDBs).
You can encounter XML object errors when you plug an Oracle Database 12c release 1 (12.1) pluggable database (PDB) into an Oracle Database 12c release 2 (12.2) or later release multitenant container database (CDB).
Common objects (objects with sharing='METADATA LINK' in
dba_objects) are created by registering system-generated names in an object-relational XML schema. Those common types are created by registering some ORDSYS schemas with object-relational storage.
The names of these common objects are system-generated, and the names generated in release 12.1 can be different from the names used for these objects in release 12.2 and later releases. Because of these possible name changes, you can find that the release 12.1 object types do not have matching common types in the release 12.2 or later release CDB root.
Resolve this issue using the following procedure:
- Query the view
PDB_PLUG_IN_VIOLATIONSin the target CDB root to see if there is any action containing
'GetTypeDDL'If you find
'GetTypeDDL'actions, then the upgraded PDB has the common objects issue.
- Run the PL/SQL packages
SET SERVEROUTPUT ONand
exec xdb.DBMS_XMLSTORAGE_MANAGE.GetTypeDDLin the target PDB to generate a user-named SQL script (for example,
- Run the script you created in step 2 (for example,
script1.sqlin the source 12.1 CDB to obtain the type creation script for each of the common types for which you are encountering errors
- Generate another user-named SQL script (for example,
script2.sql) that contains these creation scripts.
- Run the script that you created on the source 12.1 CDB (for example,
script2.sql) in the target PDB.
Fixing ORA-27248: sys.dra_reevaluate_open_failures is running
Use this procedure to identify
DRA_REEVALUATE_OPEN_FAILURES jobs that block upgrades.
During an upgrade, if DBUA fails with the error ORA-27248: sys.dra_reevaluate_open_failures is running, then the job
DRA_REEVALUATE_OPEN_FAILURES is running, which causes upgrade failures. Ensure that the job is stopped before continuing the upgrade.
In a job definition, if
ALLOW_RUNS_IN_RESTRICTED_MODE is set to TRUE, and the job owner is permitted to log in during restricted mode, then that job is permitted to run when the database is in restricted or upgrade mode. The default setting for this parameter is FALSE.
Use the following query to see the state of any running jobs:
SQL> select OBJECT_NAME, Owner, OBJECT_TYPE from dba_objects whereobject_name like '%DRA_REEVA%';
Fixing ORA-22288: File or LOB Operation FILEOPEN Failed Soft Link in Path
ORA-22288 occurs when symbolic links are in directory object paths or filenames when opening BFILES.
When you create a directory object or BFILE objects, you must meet the following conditions.
The operating system file must not be a symbolic or hard link.
The operating system directory path named in the Oracle DIRECTORY object must be an existing operating system directory path.
The operating system directory path named in the Oracle DIRECTORY object should not contain any symbolic links in its components.
When a BFILE is opened, the entire directory path and filename is checked. If any symbolic link is found, then you receive the following error.
ORA-22288: file or LOB operation FILEOPEN failed soft link in path
To resolve this error, remove symbolic links, and comply with other requirements for creating BFILEs.
Fixing Oracle Database Enterprise User Security, OLS-OID, and Provisioning Profile Error
Review to understand ORA-16000: database open for read-only access errors.
After upgrading databases that use OLS and a standby database, you may see ORA-16000 (database open for read-only access). After switchover, update the Provisioning profile with the connect information of the new primary. If you do not update the Provisioning profile, then the policies continue to be propagated to the new standby (old primary) and the database continues to fail with ORA-16000 errors.
Oracle Database Enterprise User Security Administrator's Guidefor information about the additional steps required for upgrading Oracle Database from release 10g (10.1) and higher to Oracle Database 12c
Fixing 32K Migration Error with utl32k.sql and MAX_STRING_SIZE
Use this procedure to fix ORA-01722: invalid number upgrade errors.
If the initialization parameter MAX_STRING_SIZE is set to
EXTENDED, but the 32K migration that the
utl32k.sql script carries out is not completed, then the database upgrade fails with the following error:
SELECT TO_NUMBER('32K_MIGRATION_NOT_COMPLETED') * ERROR at line 1: ORA-01722: invalid number
The database upgrade does not automatically run the
utl32k.sql script, and does not perform the 32K migration.
Complete the upgrade and the 32K migration by using this manual procedure:
Reset the initialization parameter MAX_STRING_SIZE to STANDARD.
Restart the database in
Rerun the upgrade using the manual procedure.
After the database is upgraded, set the initialization parameter MAX_STRING_SIZE to
Restart the database in
Run the SQL script
After you run the
utl32k.sql script, the upgraded database completes the 32K migration and supports the EXTENDED parameter.
Recovering from a CRS Shutdown and Oracle ASM Losing Rolling Migration
A Cluster Ready Services (CRS) shutdown on all cluster member nodes can place the cluster in a heterogeneous state. Use this procedure to recover from that problem.
Oracle Automatic Storage Management (Oracle ASM) loses the rolling migration state if CRS shuts down on all nodes. This CRS shutdown can create a heterogeneous state, so that you cannot restart all cluster member nodes. You cannot start two nodes of different versions in the cluster. If you attempt to start nodes running different versions of Oracle ASM, then one of the sets of heterogeneous nodes running Oracle ASM nodes fails, generating either ORA-15153 or ORA-15163 error messages.
Consider the following scenario of four nodes (node1, node2, node3, and node4) that are at Oracle Database release 188.8.131.52 and being upgraded to release 184.108.40.206.
Node1 and node2 are upgraded to 220.127.116.11 and running.
Node3 and node 4 are still at 18.104.22.168 and running.
Now consider that there is an outage where all CRS stacks are down, which leaves the cluster in a heterogeneous state (that is, two nodes at 22.214.171.124 and two nodes at 126.96.36.199).
Using this scenario as an example, complete the following procedure:
Restart only the nodes that are in the earlier release. In this scenario, start the nodes in release 188.8.131.52 ( node3 or node4, or both).
run the following SQL command on the Oracle ASM instance on node3 or node4 before starting any 184.108.40.206 node:
ALTER SYSTEM START ROLLING MIGRATION TO '220.127.116.11'
Continue the documented upgrade procedure from the point of failure.
Data Type Versioning Can Cause Cross-Version Replication (ORA-26656)
Review the user-defined object types affected by versioning.
Release 18.104.22.168 introduces versioning of data types that can be attributes of Oracle object types (reference Bug 18897657). Because of this feature, cross-version replication between release 22.214.171.124 and release 126.96.36.199 databases can be affected, which results in ORA-26656 errors.
If any user-defined object types contain attributes of
TIMESTAMP WITH TIME ZONE,
TIMESTAMP WITH LOCAL TIME ZONE,
ANYDATA, and similar objects, then you must apply the mandatory Patch Set Update 18038108 to all release 188.8.131.52 instances.
Referenced Symbol Count is Undefined Error libclntsh.so.11.1
Review this topic if you encounter errors that reference
libclntsh.so.11.1 with "referenced symbol count is undefined", "cannot open shared object file", or similar errors.
During an upgrade to Oracle Database 12c or 18c, client applications linked against the
libclntsh.so.11.1 file may fail to run on Oracle Solaris, HP-UX Itanium or IBM AIX platforms. In that event, you see error messages similar to the following:
referenced symbol count is undefined
Relink affected client applications against the new
libclntsh.so.12.2 for Oracle Database 12c, or
libclntssh.so.18.1 file for Oracle Database 18c.
Resolving Timestamp Errors Due to ISO 8601 Timestamps
Review this topic if you encounter timestamp errors with applications after upgrading to Oracle Database 12c, 18c, or later releases.
ISO 8601 is an international standard for exchanging date and time-related data, established by the International Organization for Standardization (ISO), and the International Electrotechnical Commission (IEC). The purpose of this standard is to provide a common international standard for representing dates and times, to avoid misinterpretation of dates and times with data used between countries using different conventions for writing numeric dates and times. For example:
Oracle recommends that you use this standard.
By default, the initialization parameter UNIFORM_LOG_TIMESTAMP_FORMAT is set to TRUE. If using the ISO 8601 standard causes scripts to break, then you can set UNIFORM_LOG_TIMESTAMP_FORMAT to FALSE to cause the Oracle Database 12.2 release or later releases to revert to the timestamp format used in Oracle Database 12.1. After you change the initialization parameter, fix your scripts so that they can use ISO 8601 timestamps. When your scripts can use the ISO 8601 standard, change the parameter back to the default value of TRUE.
Fixing Failed Upgrades Where Only Datapatch Fails
If only datapatch fails during an upgrade, then rerun datapatch directly.
The Datapatch script,
datapatch.pl , is a PERL script. In some patching operations, the final post-upgrade patches may not run, due to errors such as ORA-20001. If only the Datapatch script fails, then you do not need to run the upgrade again to fix this issue. Instead, run
To fix a failed datapatch, log in as the Oracle user, and complete this procedure:
- Change directory to Opatch inside the upgraded Oracle home.
$ cd $ORACLE_HOME/OPatch
- Run the datapatch command.
$ ./datapatch -verbose
Error "Timezone Datafiles May Not Be Downgraded To a Lower Version"
You encounter a time zone error that prohibits the upgrade if the daylight savings time (DST) version in the database you are upgrading is newer than the DST in the database release to which you are upgrading.
Scenario: You run Database Upgrade Assistant (DBUA) to upgrade from an earlier release Oracle Database to a later release Oracle Database, and encounter the following error:
SEVERE: Timezone datafiles may not be downgraded to a lower version as a result of an Oracle Database upgrade.
This error occurs if you upgrade from an earlier Oracle Database release to a later Oracle Database release, and your earlier release Oracle Database Oracle home has a more recent DST patch than the new upgrade Oracle Database Oracle home. In the log file,
preupgrade.log, you are instructed to patch the new Oracle Database Oracle home with the updated DST patch from the old Oracle home. For example:
+ Patch the new 184.108.40.206.0 $ORACLE_HOME/oracore/zoneinfo/ with the version 29 time zone data file from the 220.127.116.11.0 $ORACLE_HOME/oracore/zoneinfo/. The database is using a time zone file version that is newer than the version shipped with the 18.104.22.168.0 release. Timezone datafiles may not be downgraded to a lower version as a result of an Oracle Database upgrade.
However, this error can persist, even if you patch the new Oracle home to the same version as the earlier release Oracle Database Oracle home.
If you continue to encounter this error after patching the new Oracle home with the current time zone file, then run Oracle Database Upgrade Assistant with the flag
-ignorePreReqs true flag. Running the assistant with tis
$ dbua -sid mydb -oracleHome /u02/product/12.2.0/dbhome_1/ -ignorePreReqs - true
Only use this workaround of turning off prerequisite checks for this specific scenario. Ignoring valid failed checks that report timezone version errors between Oracle homes results in upgrade failures.
Fixing Failures to Complete Registration of Listeners with DBUA
On the Database Upgrade Assistant Progress step, a window appears with this warning: "Unable to create database entry in the directory service. No Listeners configured."
In this scenario, you have completed the following steps:
Created a listener in your earlier release Oracle home using Net Configuration Assistant (NetCA) or Net Manager.
Installed the new Oracle Database release in the new Oracle home, and registered it against the listener.
You want to register the listener to Oracle Internet Directory (OID), and upgrade the database, or you want to register the listener on OID on the new Oracle home.
If the listener is running from another Oracle home on the server, or the listener is running from the current Oracle home, but it is not configured in the
LISTENER.ORA file (that is, it uses an automatically generated default configuration), then DBCA is unable to locate the listener.
DBUA is no longer performing direct registration of the upgraded database to OID during the upgrade itself.
To resolve this issue, complete the following tasks:
De-register the listener from OID.
Perform the database upgrade.
Register again the migrated listener to the OID registry on the new release Oracle Database Oracle home.