ORA-24036: invalid SORT_ORDER column string specified for queue table

Cause : Th ecraeteq ueeu tbalec omamndw asi sseud iwthm esasgeg_ropuin gse ttoT RASNACITONLA adn as or toredr oclunm ohtert ha nproiriyt. nOlyt hep riroit ycoulmnc anb e psecfiie dint hes or toredr ofr uqeu etalbesw it htrnasatcioanl rgouipng.

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

Chnaget hes or toredr ilsti n hte rceaet qeuuet abel cmomadn adn rteryt hec al.l

update : 26-04-2017
ORA-24036

ORA-24036 - invalid SORT_ORDER column string specified for queue table
ORA-24036 - invalid SORT_ORDER column string specified for queue table

  • ora-32322 : PCT refresh of "string"."string" not allowed the sequence of DMLs/PMOPs
  • ora-13221 : unknown geometry type in the geometry object
  • ora-19921 : maximum number of string rows exceeded
  • ora-32013 : failure in verifying parameters from the restored SPFILE
  • ora-14613 : Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed
  • ora-22817 : subquery not allowed in the default clause
  • ora-14177 : STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
  • ora-02455 : The number of cluster key column must be 1
  • ora-12100 : materialized view log on "string"."string" already has sequence
  • ora-14262 : new subpartition name must differ from the old subpartition name
  • ora-13154 : invalid precision specified
  • ora-39601 : Hash key is required.
  • ora-39021 : Database compatibility version string is not supported.
  • ora-24128 : partition name specified for a non-partitioned object
  • ora-01306 : dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
  • ora-03217 : invalid option for alter of TEMPORARY TABLESPACE
  • ora-00382 : %s not a valid block size, valid range [string..string]
  • ora-01299 : dictionary string corresponds to a different database incarnation
  • ora-10944 : trace name context forever
  • ora-29822 : selectivity cannot be specified for the type of object
  • ora-38748 : cannot flashback data file string - file is in use or recovery
  • ora-19727 : cannot plug data [string] at level string into database running Oracle string
  • ora-03274 : both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified
  • ora-16504 : the Data Guard configuration already exists
  • ora-09745 : smscre: vm_allocate error, unable to create shared memory.
  • ora-04001 : sequence parameter string must be an integer
  • ora-02712 : osnpop: malloc failed
  • ora-02269 : key column cannot be of LONG datatype
  • ora-02249 : missing or invalid value for MAXLOGMEMBERS
  • ora-13527 : invalid baseline name
  • 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.