ORA-30957: cannot downgrade because there are XML indexes

Cause : An attempt was made to downgrade a database that has XML indexes.

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

Drop all XML indexes before attempting the downgrade.

update : 29-06-2017
ORA-30957

ORA-30957 - cannot downgrade because there are XML indexes
ORA-30957 - cannot downgrade because there are XML indexes

  • ora-19595 : archivelog string already included in backup conversation
  • ora-01952 : system privileges not granted to 'string'
  • ora-23349 : cannot generate replication support for functions
  • ora-34164 : (MXCGVAR01) A dimension used to define a local string variable cannot be located. Execution cannot continue.
  • ora-31404 : all input parameters are null
  • ora-17506 : I/O Error Simulation
  • ora-16411 : ONDEMAND archival requires active managed recovery operation
  • ora-13117 : [string]_RELATION$ table does not exist
  • ora-06776 : TLI Driver: error sending parms
  • ora-02097 : parameter cannot be modified because specified value is invalid
  • ora-31039 : XML namespace length string exceeds maximum string
  • ora-38422 : invalid datatype for the attribute: string
  • ora-22885 : cannot get REF to a non-persistent object
  • ora-01178 : file string created before last CREATE CONTROLFILE, cannot recreate
  • ora-19958 : potential deadlock involving DIAG process
  • ora-38416 : A stored attribute may not be longer then 300 characters.
  • ora-12682 : Login failed: the SecurID card is in next PRN mode
  • ora-24043 : destination string uses a reserved name, names with AQ$_ prefix are not valid
  • ora-23384 : replication parallel push string argument out of range
  • ora-06028 : NETASY: unable to intialise for logging
  • ora-01986 : OPTIMIZER_GOAL is obsolete
  • ora-23344 : constraint (string.string) does not exist
  • ora-28538 : result set not found
  • ora-19921 : maximum number of string rows exceeded
  • ora-35095 : (QFSVNS01) One or more imported values of fixed-width dimension workspace object have been truncated.
  • ora-30349 : specified dimension hierarchy does not exist
  • ora-02089 : COMMIT is not allowed in a subordinate session
  • ora-35074 : (QFHEAD02) EIF file string cannot be read by this version of string.
  • ora-34901 : (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES option.
  • ora-07744 : slemcl: invalid error message file handle
  • 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.