My Oracle Support Banner

19c:Upgrade fails with Error:"ORA-1722" , 'MUST_BE_&C_ORACLE_HIGH_MAJ..&C_ORACLE_HIGH_RU..&C_ORACLE_HIGH_RUR' (Doc ID 2579192.1)

Last updated on MAY 12, 2022

Applies to:

Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and later
Microsoft Windows x64 (64-bit)

Symptoms

Symptom 1:  Database Upgrade to 19c on Windows platform  using DBUA, fails  with error:

catupgrd0.log shows:

SQL> SELECT TO_NUMBER(
  2   'MUST_BE_&C_ORACLE_HIGH_MAJ..&C_ORACLE_HIGH_RU..&C_ORACLE_HIGH_RUR')
  3  FROM v$instance
  4  WHERE substr(version_full,1,instr(version,'.',1,3)-1) !=
  5    '&C_ORACLE_HIGH_MAJ..&C_ORACLE_HIGH_RU..&C_ORACLE_HIGH_RUR';
   2: 'MUST_BE_&C_ORACLE_HIGH_MAJ..&C_ORACLE_HIGH_RU..&C_ORACLE_HIGH_RUR')
   2: 'MUST_BE_19.3.0')
   5:      '&C_ORACLE_HIGH_MAJ..&C_ORACLE_HIGH_RU..&C_ORACLE_HIGH_RUR'
   5:      '19.3.0'
  'MUST_BE_19.3.0')
  *
Line 2:
ORA-01722: invalid number

 

 Symptom 2: Database Upgrade to 19c , fails with error:

 catupgrd0.log shows:

 

SQL> SELECT TO_NUMBER(
2 'MUST_BE_&C_ORACLE_HIGH_MAJ..&C_ORACLE_HIGH_RU..&C_ORACLE_HIGH_RUR')
3 FROM v$instance
4 WHERE substr(version_full,1,instr(version_full,'.',1,3)-1) !=
5 '&C_ORACLE_HIGH_MAJ..&C_ORACLE_HIGH_RU..&C_ORACLE_HIGH_RUR';
old 2: 'MUST_BE_&C_ORACLE_HIGH_MAJ..&C_ORACLE_HIGH_RU..&C_ORACLE_HIGH_RUR')
new 2: 'MUST_BE_19.13.0')
old 5: '&C_ORACLE_HIGH_MAJ..&C_ORACLE_HIGH_RU..&C_ORACLE_HIGH_RUR'
new 5: '19.13.0'
'MUST_BE_19.13.0')
*
ERROR at line 2:
ORA-01722: invalid number

 

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
 Symptom 1:  Database Upgrade to 19c on Windows platform  using DBUA, fails  with error:

  Symptom 2: Database Upgrade to 19c , fails with error:
Cause
 Cause 1:
 Cause 2:
Solution
 Solution 1:
 Solution 2:
References


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