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 : 24-05-2017

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

  • ora-13798 : Parameter string cannot be NULL.
  • ora-06910 : CMX: Cannot start oracle process on remote machine
  • ora-06742 : TLI Driver: cannot alloc t_bind
  • ora-06536 : IN bind variable bound to an OUT position
  • ora-19770 : invalid change tracking file name
  • ora-29335 : tablespace 'string' is not read only
  • ora-14310 : VALUES LESS THAN or AT clause cannot be used with List partitioned tables
  • ora-26515 : no master log available for 'string.string'
  • ora-16177 : media recovery is not required
  • ora-06130 : NETTCP: host access denied
  • ora-24102 : invalid prefix for generate_job_name
  • ora-01984 : invalid auditing option for procedures/packages/functions
  • ora-30179 : invalid argument index used in a format code
  • ora-36706 : (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.
  • ora-37182 : you may only specify one dimension to partition
  • ora-39768 : only one direct path context top level column array is allowed
  • ora-02079 : no new sessions may join a committing distributed transaction
  • ora-31422 : owner schema string does not exist
  • ora-14032 : partition bound of partition number string is too high
  • ora-24952 : register, unregister or post has incorrect collection count
  • ora-02241 : must of form EXTENTS (FILE BLOCK SIZE , ...)
  • ora-27060 : could not set close-on-exec bit on file
  • ora-39503 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-28003 : password verification for the specified password failed
  • ora-04075 : invalid trigger action
  • ora-27029 : skgfrtrv: sbtrestore returned error
  • ora-31018 : Error deleting XML document
  • ora-15002 : parameter LOCK_NAME_SPACE exceeds limit of string characters
  • ora-07597 : spguns: $GETJPIW failure
  • ora-01346 : LogMiner processed redo beyond specified reset log scn
  • 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.