ORA-31114 XDB configuration has been deleted or is corrupted during upgrade to 11.2
(Doc ID 1091252.1)
Last updated on FEBRUARY 18, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - 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 11-Apr-2013
Checked as Top Hit on 09-NOV-2011
Symptoms
Upgrade from 10.2.0.4 to 11.2.0.1 generated errors during XDBCONFIG upgrade:
SQL> @catupgrd.sql
SQL> Rem
SQL> Rem $Header: catupgrd.sql 29-mar-2007.12:50:24 cdilling Exp $
SQL> Rem
SQL> Rem catupgrd.sql
...
...
SQL>
SQL> @@xdbuud
SQL> Rem
SQL> Rem $Header: xdbuud.sql 12-nov-2007.16:03:02 yifeng Exp $
SQL> Rem
SQL> Rem xdbuud.sql
...
...
SQL> Rem TODO - We should do the XDBCONFIG Upgrade here
SQL>
SQL> Rem Add new servlets
SQL> declare
2 cfg_data XMLTYPE;
3 begin
4 cfg_data := dbms_xdb.cfg_get();
...
...
52 INTO cfg_data
53 FROM dual;
54
55 dbms_xdb.cfg_update(cfg_data);
56 end;
57 /
declare
*
ERROR at line 1:
ORA-31114: XDB configuration has been deleted or is corrupted
ORA-06512: at "SYS.XMLTYPE", line 310
ORA-06512: at line 1
ORA-06512: at line 7
SQL> Rem
SQL> Rem $Header: catupgrd.sql 29-mar-2007.12:50:24 cdilling Exp $
SQL> Rem
SQL> Rem catupgrd.sql
...
...
SQL>
SQL> @@xdbuud
SQL> Rem
SQL> Rem $Header: xdbuud.sql 12-nov-2007.16:03:02 yifeng Exp $
SQL> Rem
SQL> Rem xdbuud.sql
...
...
SQL> Rem TODO - We should do the XDBCONFIG Upgrade here
SQL>
SQL> Rem Add new servlets
SQL> declare
2 cfg_data XMLTYPE;
3 begin
4 cfg_data := dbms_xdb.cfg_get();
...
...
52 INTO cfg_data
53 FROM dual;
54
55 dbms_xdb.cfg_update(cfg_data);
56 end;
57 /
declare
*
ERROR at line 1:
ORA-31114: XDB configuration has been deleted or is corrupted
ORA-06512: at "SYS.XMLTYPE", line 310
ORA-06512: at line 1
ORA-06512: at line 7
No other errors found in the upgrade log file, and no memory related errors found in OS system log.
ASMM is configured on the database with SHARED_POOL_SIZE = 0, JAVA_POOL_SIZE = 0, and MEMORY_TARGET = <some size>.
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 |