The database is upgraded from oracle10.2.0.5 to 11.2.0.3:
Oracle uses RMAN to directly restore the database from 10g to 11g.
Http://blog.csdn.net/tianlesoftware/article/details/7311352
This problem occurs during the upgrade, and the problem is also caused by the invalid XDB and ordim components, as follows:
SQL> Col comp_id for A15
SQL> Col version for A15
SQL> Col comp_name for A30
SQL> selectcomp_id, comp_name, version, status from dba_registry;
Comp_id comp_name version status
-----------------------------------------------------------------------------
Amd olap catalog 11.2.0.3.0 valid
Em Oracle Enterprise Manager 11.2.0.3.0 valid
SDO spatial 11.2.0.3.0 valid
Ordim Oracle multimedia 11.2.0.3.0 invalid
XDB Oracle XML database 11.2.0.3.0 invalid
Context Oracle Text 11.2.0.3.0 valid
ODM Oracle Data Mining 11.2.0.3.0 valid
Exf Oracle Expression Filter 11.2.0.3.0 valid
RUL Oracle Rules Manager 11.2.0.3.0 valid
Owm Oracle Workspace Manager 11.2.0.3.0 valid
Catalog Oracle Database catalog views 11.2.0.3.0 valid
Comp_id comp_name version status
-----------------------------------------------------------------------------
Catproc Oracle database packages and t11.2.0.3.0 invalid
JavaVM jserver Java Virtual Machine 11.2.0.3.0 valid
XML Oracle xdk 11.2.0.3.0 valid
Catjava Oracle Database Java packages 11.2.0.3.0 valid
Xoq Oracle olap api 11.2.0.3.0 valid
Aps olap analytic workspace 11.2.0.3.0 valid
17 rows selected.
After using the XDB reload method to reconstruct all XDB objects, XDB becomes a valid object:
SQL> selectcomp_id, comp_name, version, status from dba_registry;
Comp_id comp_name version status
-----------------------------------------------------------------------------
Amd olap catalog 11.2.0.3.0 valid
Em Oracle Enterprise Manager 11.2.0.3.0 valid
SDO spatial 11.2.0.3.0 valid
Ordim Oracle multimedia 11.2.0.3.0 invalid
XDB Oracle XML database 11.2.0.3.0 valid
Context Oracle Text 11.2.0.3.0 valid
ODM Oracle Data Mining 11.2.0.3.0 valid
Exf Oracle Expression Filter 11.2.0.3.0 valid
RUL Oracle Rules Manager 11.2.0.3.0 valid
Owm Oracle Workspace Manager 11.2.0.3.0 valid
Catalog Oracle Database catalog views 11.2.0.3.0 valid
Comp_id comp_name version status
-----------------------------------------------------------------------------
Catproc Oracle database packages and t11.2.0.3.0 valid
JavaVM jserver Java Virtual Machine 11.2.0.3.0 valid
XML Oracle xdk 11.2.0.3.0 valid
Catjava Oracle Database Java packages 11.2.0.3.0 valid
Xoq Oracle olap api 11.2.0.3.0 valid
Aps olap analytic workspace 11.2.0.3.0 valid
17 rows selected.
The ordim component is invalid. When you reload the component, run @? /Ord/IM/admin/imxreg. SQL; there are still a large number of such errors during script:
SQL> @? /Ord/IM/admin/imxreg. SQL;
PL/SQL procedure successfully completed.
Declare
*
Error at line 1:
ORA-31000: Resource 'HTTP: // xmlns.oracle.com/xdb/acl.xsd' is not an XDB Schema
Document
ORA-06512: At line 1240
Declare
*
Error at line 1:
ORA-31000: Resource 'HTTP: // xmlns.oracle.com/xdb/acl.xsd' is not an XDB Schema
Document
ORA-06512: At line 1010
Declare
*
Error at line 1:
ORA-31000: Resource 'HTTP: // xmlns.oracle.com/xdb/acl.xsd' is not an XDB Schema
Document
ORA-06512: At line 1008
Declare
*
Error at line 1:
ORA-31000: Resource 'HTTP: // xmlns.oracle.com/xdb/acl.xsd' is not an XDB Schema
Document
ORA-06512: At line 1012
The reload of ordim will also be suspended, so the XDB and ordim components are invalid and cannot be solved using the reload XDB component method, but should be solved using the reinstall XDB method, in this way, you can avoid ORA-31000 errors and reload the ordim component smoothly.
For more information about XDB component reconstruction and reload, refer to my blog:
Oracle XDB component reconstruction description
Http://blog.csdn.net/tianlesoftware/article/details/7323139
-- Uninstall XDB:
SQL> @? /Rdbms/admin/catnoqm. SQL
-- Install XDB
SQL> shutdown immediate
SQL> startup
SQL> @? /Rdbms/admin/catqm. SQL Oracle sysaux temp Yes
SQL> @? /Rdbms/admin/utlrp. SQL
Verify that XDB is normal:
SQL> set wrap off
SQL> Col comp_id for A15
SQL> Col version for A15
SQL> Col comp_name for A30
SQL> selectcomp_id, comp_name, version, status from dba_registry;
Comp_id comp_name version status
-----------------------------------------------------------------------------
XDB Oracle XML database 11.2.0.3.0 valid
Amd olap catalog 11.2.0.3.0 valid
Em Oracle Enterprise Manager 11.2.0.3.0 valid
SDO spatial 11.2.0.3.0 valid
Ordim Oracle multimedia 11.2.0.3.0 invalid
Context Oracle Text 11.2.0.3.0 valid
ODM Oracle Data Mining 11.2.0.3.0 valid
Exf Oracle Expression Filter 11.2.0.3.0 valid
RUL Oracle Rules Manager 11.2.0.3.0 valid
Owm Oracle Workspace Manager 11.2.0.3.0 valid
Catalog Oracle Database catalog views 11.2.0.3.0 valid
Catproc Oracle database packages and t11.2.0.3.0 valid
JavaVM jserver Java Virtual Machine 11.2.0.3.0 valid
XML Oracle xdk 11.2.0.3.0 valid
Catjava Oracle Database Java packages 11.2.0.3.0 valid
Xoq Oracle olap api 11.2.0.3.0 valid
Aps olap analyticworkspace 11.2.0.3.0 valid
17 rows selected.
In the next reload ordim component:
SQL> alter session set current_schema = "ordsys ";
SQL> @? /Ord/IM/admin/imxreg. SQL;
SQL> @? /Ord/IM/admin/impbs. SQL;
SQL> @? /Ord/IM/admin/impvs. SQL;
SQL> @? /Ord/IM/admin/imtyb. SQL;
SQL> @? /Ord/IM/admin/implb. SQL;
SQL> @? /Ord/IM/admin/imxrepos. SQL;
This time passed, no ORA-31000 error encountered.
SQL> selectcomp_id, comp_name, version, status from dba_registry;
Comp_id comp_name version status
-----------------------------------------------------------------------------
XDB Oracle XML database 11.2.0.3.0 valid
Amd olap catalog 11.2.0.3.0 valid
Em Oracle Enterprise Manager 11.2.0.3.0 valid
SDO spatial 11.2.0.3.0 valid
Ordim Oracle multimedia 11.2.0.3.0 valid
Context Oracle Text 11.2.0.3.0 valid
ODM Oracle Data Mining 11.2.0.3.0 valid
Exf Oracle Expression Filter 11.2.0.3.0 valid
RUL Oracle Rules Manager 11.2.0.3.0 valid
Owm Oracle Workspace Manager 11.2.0.3.0 valid
Catalog Oracle Database catalog views 11.2.0.3.0 valid
Catproc Oracle database packages and t11.2.0.3.0 valid
JavaVM jserver Java Virtual Machine 11.2.0.3.0 valid
XML Oracle xdk 11.2.0.3.0 valid
Catjava Oracle Database javapackages 11.2.0.3.0 valid
Xoq Oracle olap api 11.2.0.3.0 valid
Aps olap analytic workspace 11.2.0.3.0 valid
17 rows selected.
Summary:
(1) When the XDB and ordim components expire at the same time, you can only use the reinstall XDB component instead of the reload XDB component method. Otherwise the ORA-31000 error will occur during the reload ordim component process:
ORA-31000: Resource 'HTTP: // xmlns.oracle.com/xdb/acl.xsd' is not an XDB schema document
(2) The reinstall and reload methods vary with Oracle versions. For details, refer:
Oracle XDB component reconstruction description
Http://blog.csdn.net/tianlesoftware/article/details/7323139
Bytes -------------------------------------------------------------------------------------------------------
All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!
Skype: tianlesoftware
Email: tianlesoftware@gmail.com
Blog: http://www.tianlesoftware.com
WEAVER: http://weibo.com/tianlesoftware
Twitter: http://twitter.com/tianlesoftware
Facebook: http://www.facebook.com/tianlesoftware
LinkedIn: http://cn.linkedin.com/in/tianlesoftware
------- Add a group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, reject the application ----
Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)
Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823
Dba6 group: 158654907 dba7 group: 172855474 DBA group: 104207940