My Oracle Support Banner

Primary Note : ORA-1722 Errors during Upgrade (Doc ID 1466464.1)

Last updated on AUGUST 10, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.3 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 16-Dec-2013***

Symptoms

Case I) ORA-1722 : invalid number reported even after pre-Upgrade Script(utluxxxi.sql) has been run

=================================================================

While upgrading database version homes, the upgrade process fails with the below error:

SELECT TO_NUMBER('MUST_HAVE_RUN_PRE-UPGRADE_TOOL_FOR_TIMEZONE')
   *
   ERROR at line 1:
   ORA-01722: invalid number

This Error is reported even after running the Pre-Upgrade Script & when the latest/acceptable DST Patch is applied on both the Source & Target Oracle Homes.

WARNINGS for Case I

1: If you did not run the pre-upgrade script, this action described in this note can cause corruption of the database.

2: The TZ value you insert into that table MUST be the proper value of the pre-upgraded DB. Any other value can cause corruption of the database.

Case II) Upgrade Fails With ORA-01722 'LABEL_SECURITY_OPTION_OFF'

=================================================================

Manual upgrade to 11.1 using a Data Vault environment fails with an error similar to...

SELECT TO_NUMBER('LABEL_SECURITY_OPTION_OFF') FROM v$option
*
ERROR at line 1:
ORA-01722: invalid number

Data Vault has been disabled using...

 

  

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
 1: If you did not run the pre-upgrade script, this action described in this note can cause corruption of the database.
 2: The TZ value you insert into that table MUST be the proper value of the pre-upgraded DB. Any other value can cause corruption of the database.
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.