ORA-25314: a commit-time queue table cannot be migrated to 8.0

Cause : An attmept wasm ade tom igratea commi-ttime qeuue tabel to anu nsuppotred comaptibiliyt level.

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

Provid ean apporpriatec ompatiiblity lveel, an dretry hte opertaion.

update : 27-06-2017
ORA-25314

ORA-25314 - a commit-time queue table cannot be migrated to 8.0
ORA-25314 - a commit-time queue table cannot be migrated to 8.0

  • ora-24039 : Queue string not created in queue table for multiple consumers
  • ora-12057 : materialized view "string"."string" is INVALID and must complete refresh
  • ora-07263 : sptpa: kill error.
  • ora-36314 : (PHYS01) workspace object must be a dimension, relation or variable.
  • ora-14455 : attempt to create referential integrity constraint on temporary table
  • ora-12817 : parallel query option must be enabled
  • ora-04068 : existing state of packagesstringstringstring has been discarded
  • ora-24806 : LOB form mismatch
  • ora-36833 : (XSLMGEN03) View token cannot be blank
  • ora-26687 : no instantiation SCN provided for "string"."string" in source database "string"
  • ora-09292 : sksabln: unable to build archive file name
  • ora-23615 : Block number string does not exist for script string
  • ora-12686 : Invalid command specified for a service
  • ora-10259 : get error message text from remote using explicit call
  • ora-26059 : Data is too large for column string
  • ora-26524 : nls subsystem initialization failure for product=string, facility=string
  • ora-16564 : lookup failed, syntax error at string
  • ora-28575 : unable to open RPC connection to external procedure agent
  • ora-15018 : diskgroup cannot be created
  • ora-14113 : partitioned table cannot have column with LOB datatype
  • ora-37013 : (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock.
  • ora-39150 : bad flashback time
  • ora-19657 : cannot inspect current datafile string
  • ora-25114 : invalid file number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-38906 : insert into DML Error Logging table "string" failed
  • ora-00315 : log string of thread string, wrong thread # string in header
  • ora-22316 : input type is not a collection type
  • ora-01605 : missing numbers in clause "string" of string
  • ora-12901 : default temporary tablespace must be of TEMPORARY type
  • ora-38477 : attribute set cannot be derived from an evolved type or a subtype.
  • 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.