<< Back to previous view
Questions & Answers

The autoupgrade utility fails with "Warning: XDB now invalid" message

Created: 06/Feb/25 03:55 PM   Updated: 06/Feb/25 10:00 PM
Fix Version/s: None

Product Version: 24.8.241119
Operating System: Windows
Host Name: .
Database Name: .


 Description  « Hide
PROBLEM:

The autoupgrade utility fails with "Warning: XDB now invalid" message.

DATABASES:

  • Source database version: 12.2.0.1 (EE)
  • Target database version: 19.25 (EE)

CONFIGURATION:

global.autoupg_log_dir=C:\oracle\app\Ora-Admin\cfgtoollogs\autoupgrade
upg1.manage_network_files=SKIP
upg1.sid=REPO
upg1.source_home=C:\oracle\product\12.2.0\dbhome_1
upg1.target_cdb=PRODCDB
upg1.target_home=C:\oracle\app\Ora-Admin\product\19.0.0\dbhome_1
upg1.target_pdb_copy_option.REPO=file_name_convert=('C:\ORACLE\ORADATA\', 'D:\ORACLE\ORADATA\PRODCDB\')
upg1.source_dblink.REPO=repo_link 600
upg1.start_time=30/01/2025 14:00:00

ERROR MESSAGE:

DOS> %ORACLE_HOME%\jdk\bin\java -jar %ORACLE_HOME%\rdbms\admin\autoupgrade.jar -config REPO-autopgrade_config.txt -mode deploy
AutoUpgrade 24.8.241119 launched with default internal options
Processing config file ...
+--------------------------------+
| Starting AutoUpgrade execution |
+--------------------------------+
1 Non-CDB(s) will be processed
Type 'help' to list console commands
upg> Copying remote database 'REPO' as 'REPO' for job 100

...
Errors in database [REPO]
Stage     [NONCDBTOPDB]
Operation [STOPPED]
Status    [ERROR]
Info    [
Error: UPG-3005
Warning: XDB now invalid
Cause: Error running noncdb_to_pdb.sql script


 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
ubTools Support - 06/Feb/25 06:34 PM
ANALYSIS:
  • The error happened while running utlrp.sql in NONCDBTOPDB stage.
SQL> Rem ===========================================================================
SQL> Rem BEGIN utlrp.sql
SQL> Rem ===========================================================================
SQL> 
...
SQL> 
SQL> Rem =====================================================================
SQL> Rem Run component validation procedure
SQL> Rem =====================================================================
SQL> 
SQL> SET serveroutput on
SQL> EXECUTE dbms_registry_sys.validate_components;
Warning: XDB now invalid

PL/SQL procedure successfully completed.

Elapsed: 00:00:02.09
SQL> SET serveroutput off
SQL> 
SQL> 
SQL> Rem ===========================================================================
SQL> Rem END utlrp.sql
SQL> Rem ===========================================================================

Ref: <global.autoupg_log_dir>\REPO\100\noncdbtopdb\noncdbtopdb_repo_REPO.log

  • Even though it is a warning, the autoupgrade utility reported it as an error.

[ Permlink | « Hide ]
ubTools Support - 06/Feb/25 07:30 PM - edited
WORKAROUNDS:

Workaround 1:

  • Resume failed autoupgrade utility job
  • After the autoupgrade utility completes successfully, if there are invalid objects in upgraded PBD, consider running %ORACLE_HOME%\rdbms\admin\utlrp.sql as SYS user

Workaround 2:

  • Exit from the autoupgrade utility
  • For a new fresh upgrade; drop target PDB, and delete the autoupgrade utility logging directory(global.autoupg_log_dir in the issue) or set the logging directory parameter to a new directory
  • Set run_utlrp=no in the autoupgrade utility configuration file
  • Run the autoupgrade utility again
  • After the autoupgrade utility completes successfully, if there are invalid objects in upgraded PBD, consider running %ORACLE_HOME%\rdbms\admin\utlrp.sql as SYS user

[ Permlink | « Hide ]
ubTools Support - 06/Feb/25 08:35 PM - edited
ENHANCEMENT:
  • File an enhancement request for the autoupgrade utility to Oracle to run utlrp.sql or its equivalent multiple times in case there are invalid objects of Oracle-maintained schemas or invalid components in DBA_REGISTRY.