ORA-31159: XML DB is in an invalid state

Cause : XMLD B'si ntenral atble sarei n a ninvlaid tsate ,proabblyb ecasue teh daatbas ewasn ot pugraedd o rtheu pgrdae wsa no tsucecssflu

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Ensrue taht teh daatbas eis pugraedd scucesfsull.y Ift he rpoblme pesrist,s cotnactO racel Support

update : 26-03-2017
ORA-31159

ORA-31159 - XML DB is in an invalid state
ORA-31159 - XML DB is in an invalid state

  • ora-22621 : error transfering an object from the agent
  • ora-09705 : spcre: cannot initialize latch semaphore
  • ora-06914 : CMX: unexepected event during start of oracle
  • ora-01172 : recovery of thread string stuck at block string of file string
  • ora-30041 : Cannot grant quota on the tablespace
  • ora-16568 : cannot set property string
  • ora-37015 : (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously listed to be acquired both with and without RESYNC.
  • ora-02169 : FREELISTS storage option not allowed
  • ora-00365 : the specified log is not the correct next log
  • ora-12210 : TNS:error in finding Navigator data
  • ora-00953 : missing or invalid index name
  • ora-10642 : Found rollback segments in dictionary managed tablespaces
  • ora-07570 : szrfc: $IDTOASC failure
  • ora-23308 : object string.string does not exist or is invalid
  • ora-29841 : invalid option for ALTER INDEXTYPE
  • ora-12901 : default temporary tablespace must be of TEMPORARY type
  • ora-07281 : slsget: times error, unable to get cpu time.
  • ora-06610 : LU6.2 Driver: Failed during deallocation
  • ora-13120 : invalid face_id [string]
  • ora-19107 : invalid XQueryX - unsupported construct - string
  • ora-13422 : invalid model coordinate parameter
  • ora-14456 : cannot rebuild index on a temporary table
  • ora-30756 : cannot create column or table of type that contains a supertype attribute
  • ora-39216 : object type "string"."string" hashcode mismatch
  • ora-26076 : cannot set or reset value after direct path structure is allocated
  • ora-39313 : call to DBMS_SCHEMA_COPY.CLONE is not legal
  • ora-16056 : backup control file archival requires proper syntax
  • ora-16641 : failure to acquire broker configuration metadata lock
  • ora-38907 : DML error logging is not supported for FILE column "string"
  • ora-32343 : let MVIEW engine know that it is IMPORT from 9i or earlier
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.