Utlrp Issues Warning: XDB Now Invalid
(Doc ID 2974795.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.19.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
-- Running utlrp throws the following errors:
Errors:
...(19:11:35) Starting validate_apex for APEX_220100
...(19:11:36) Checking missing sys privileges
...(19:11:36) Re-generating APEX_220100.wwv_flow_db_version
... wwv_flow_db_version is up to date
...(19:11:36) Checking invalid public synonyms
...(19:11:36) Key object existence check
...(19:11:36) Setting DBMS Registry for APEX to valid
...(19:11:36) Exiting validate_apex
Warning: XDB now invalid
-- Executing sys.dbms_regxdb.validatexdb fails with the following error:
ERROR at line 1:
ORA-39705: component 'XDB' not found in registry
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_REGISTRY", line 353
ORA-06512: at "SYS.DBMS_REGISTRY", line 365
ORA-06512: at "SYS.DBMS_REGXDB", line 110
ORA-06512: at line 1
-- Running sql trace also also shows:
*** 2023-08-31T21:47:38.516071+00:00 (MTU01SIM01(4))
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=1, mask=0x0)
----- Error Stack Dump -----
<error barrier> at 0x7ffd350f1b90 placed dbkda.c@298
ORA-39705: component 'CONTEXT' not found in registry
----- Current SQL Statement for this session (sql_id=4ghdq9fcyght7) -----
BEGIN SYS.VALIDATE_CONTEXT; END;
----- PL/SQL Stack -----
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 |
Cause |
Solution |
References |