B AutoUpgrade Error Messages

AutoUpgrade provides a set of errors and messages for failures in preupgrade, upgrade, and postupgrade errors.

Host Errors (UPG-1000 to UPG-1200)

  • UPG-1000: It was not possible to create the data file where the jobsTable is being written or there was a problem during the writing, it might be thrown due to a permission error or a busy resource scenario
  • UPG-1001: There was a problem reading the state file perhaps there was corruption writing the file and in the next write it might be fixed
  • UPG-1002: Error deserializing the object for rerun, review log for any errors
  • UPG-1100: Either the console or the job manager were interrupted and it might lead to unknown errors because if there were active tasks running they won't be able to be finish gracefully nor we will guarantee that we track their progress properly
  • UPG-1200: Error reading the standard input, perhaps a malformed character or there was a problem with the process's stdin

Preupgrade Errors (UPG-1300 to UPG-1319

  • UPG-1300: The current execution of the database fixups was interrupted and a set of checks is still pending
  • UPG-1301: The current execution of the database fixups was not completed
  • UPG-1302: The current execution of the database checks was interrupted
  • UPG-1303: A failed check has an ERROR severity but the fixup is unavailable or failed to correct the problem. Manually fix the problem and rerun AutoUpgrade
  • UPG-1304: IO error creating before, during or after upgrade pfile
  • UPG-1305: Error executing SQL statement in upgrade inspector during database preupgrade checks
  • UPG-1306: Error during the database preupgrade checks in upgrade inspector
  • UPG-1307: Error running database postupgrade checks in upgrade inspector
  • UPG-1308: Error running database postupgrade checks in upgrade inspector
  • UPG-1309: Error accessing the log file that contains the check list (CFG format)
  • UPG-1310: Error accessing the log file that contains the check list (log format)
  • UPG-1311: Error accessing the checks HTML report file
  • UPG-1312: A failed check has an ERROR severity but the fixup is unavailable or failed to correct the problem. Manually fix the problem and rerun AutoUpgrade
  • UPG-1313: Internal error, contact Oracle Support
  • UPG-1314: User requested an abort of the checks
  • UPG-1315: User requested an abort of the fixups
  • UPG-1316: Error running database checks or fixups
  • UPG-1317: Required checklist file unavailable; unable to run fixups
  • UPG-1318: Error creating custom pfiles
  • UPG-1319: Loading the current state of the database failed

Upgrade Process Errors

  • UPG-1400: Database upgrade failed with errors
  • UPG-1401: Opening database for upgrade in the target home failed
  • UPG-1402: GRP creation prior to upgrade failed
  • UPG-1403: Drop of existing GRP failed
  • UPG-1404: Error running upgrade
  • UPG-1405: Database upgrade was interrupted
  • UPG-1406: Unexpected Exception occurred during database compilations
  • UPG-1407: IO error creating database spfile
  • UPG-1408: Unable to open pdb in upgrade mode
  • UPG-1409: Unable to open pdb in normal mode
  • UPG-1410: Unable to open database in normal mode
  • UPG-1411: Invalid version of catctl.pl and catctl.pm
  • UPG-1412: Unable to query database
  • UPG-1413: Error occurred during upgrade
  • UPG-1414: Database compilation interrupted
  • UPG-1415: Database upgrade interrupted by a system shutdown or CTRL+C
  • UPG-1416: Error during database compilations
  • UPG-1417: PDB upgrade failed with errors
  • UPG-1418: Database upgrade failed; review the upgrade log files
  • UPG-1419 Database upgrade job has been killed, by abort or restore
  • UPG-1420 Enabling Local Undo failed

Postupgrade Errors

  • UPG-1500: Database post upgrade failed
  • UPG-1501: Oratab file not readable
  • UPG-1502: Oratab file not writable
  • UPG-1503: IO error updating the oratab file
  • UPG-1504: Error writing to oratab file
  • UPG-1505: Error copying listener.ora file in postupgrade
  • UPG-1506: Error copying tnsnames.ora file in postupgrade
  • UPG-1507: Error copying sqlnet.ora file in postupgrade
  • UPG-1508: Error processing the ifile
  • UPG-1509: Error copying the wallet files
  • UPG-1510: Unable to create the postupgrade directory
  • UPG-1511: Error during user-defined postupgrade action
  • UPG-1512: Error copying the password files
  • UPG-1513: Error restoring the database state
  • UPG-1514: Error deserializing the database state
  • UPG-1515: Error dropping the GRP
  • UPG-1516: Error restarting the databas
  • UPG-1517: Error recreating the final spfile
  • UPG-1518: An error occurred while copying Context text files in Postupgrade phase
  • UPG-1519: An error occurred while generating Context text file list in Drain phase
  • UPG-1520: Error copying oranfstab file in postupgrade
  • UPG-1521: Error copying ldap.ora file in postupgrade
  • UPG-1522: Error updating network file's ORACLE_HOME in postupgrade
  • UPG-1523: Error restarting the pdbs

Database Upgrade Stage Errors

  • UPG-1600: Error copying the pfile during an UPGRADE mode job
  • UPG-1601: Error reading the error properties file
  • UPG-1602: Job killed
  • UPG-1603: Error executing a database command for PDB$SEED
  • UPG-1604: Error executing a database command
  • UPG-1605: Unable to abort a job in a unsupported stage
  • UPG-1606: Source version cannot be upgraded to the specified target version
  • UPG-1607: Target version is not supported by AutoUpgrade
  • UPG-1608: Unable to determine database version; review the logs files
  • UPG-1699: Error finding error definition, contact Oracle Support
  • UPG-1700: Error generating Windows services in drain module
  • UPG-1701: Error stopping queue jobs during drain
  • UPG-1702: Error deleting service during drain, review log files
  • UPG-1703: Error creating service during drain, review log files
  • UPG-1704: Error commenting service during drain, review log files
  • UPG-1705: Error changing service owner during drain, review log files
  • UPG-1706: Error starting service during drain, review log files
  • UPG-1707: Error stopping service during drain, review log files
  • UPG-1708: Error changing the source database state
  • UPG-1709: Error serializing the database state
  • UPG-1710: Error during PDB operation in drain
  • UPG-1711: An error occurred while deferring Standby in Drain phase
  • UPG-1800: Progress report is empty, review log file
  • UPG-1900: Unable to create preupgrade directory
  • UPG-1901: Error during user-defined preupgrade action
  • UPG-2000: Creation of GRP failed
  • UPG-2001: Unable to drop GRP
  • UPG-2002: Restoration of the GRP failed

Non-CDB to CDB Upgrade Errors (UPG-3000 to

  • UPG-3000: Error executing noncdbtopdb task
  • UPG-3001: Could not describe the specified database
  • UPG-3002: Could not execute database action
  • UPG-3003: Plugin violations found
  • UPG-3004: Could not create pluggable database
  • UPG-3005: Error running noncdb_to_pdb.sql script
  • UPG-3006: Error starting the database
  • UPG-3007: User requested an abort of the noncdbtopdb task
  • UPG-3008: Unable to remove the oratab entry of the source DB
  • UPG-3009: After running noncdb_to_pdb.sql, the pdb was closed or was opened in restricted mode
  • UPG-3010: Error running approot_to_pdb.sql script
  • UPG-3100: Unable to list RAC service
  • UPG-3101: Unable to shutdown RAC services
  • UPG-3102: Unable to shutdown RAC database
  • UPG-3103: Failed to disable RAC database
  • UPG-3104: Unable to remove spfile parameter
  • UPG-3105: Unable to start RAC database
  • UPG-3106: Unable to upgrade RAC database on CRS
  • UPG-3107: Unable to update spfile information on CRS
  • UPG-3108: Failed to enable RAC database on CRS
  • UPG-3109: Unable to stop current instance
  • UPG-3110: Unable to downgrade RAC database source binaries on CRS
  • UPG-3111: Failed to enable RAC database source binaries on CRS
  • UPG-3112: Unable to start RAC database after downgrade source binaries on CRS
  • UPG-3113: After executing "srvctl stop database", AutoUpgrade sees that the RAC database is still up, which suggests that the database was started up manually and not via CRS. This condition can cause AutoUpgrade to stop the current job.
  • CON-4000: Database {0} shutdown or open with incorrect binaries for {1}. Ensure it is open with {2}
  • CON-4001Database {0} currently has a status of {1}. For {2} mode, open it with one of the following: {3}