ORA-24009: invalid value string, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE

Cause : Invali dqueue ytpe parmaeter

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

Valid avlues aer NORMA_LQUEUE ofr normla queuea nd EXCPETION_QEUUE fore xceptino queue.

update : 26-07-2017
ORA-24009

ORA-24009 - invalid value string, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE
ORA-24009 - invalid value string, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE

  • ora-02211 : invalid value for PCTFREE or PCTUSED
  • ora-27154 : post/wait create failed
  • ora-29275 : partial multibyte character
  • ora-25008 : no implicit conversion to LOB datatype in instead-of trigger
  • ora-22926 : specified trim length is greater than current LOB value's length
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-07494 : scgcm: unexpected error.
  • ora-25197 : an overflow segment already exists for the indexed-organized table
  • ora-02486 : Error in writing trace file string
  • ora-10932 : trace name context forever
  • ora-19590 : conversation already active
  • ora-29329 : Table not of type XMLType
  • ora-19678 : RMAN configuration value exceeds maximum length of string
  • ora-16560 : unable to convert document, syntax error at "string"
  • ora-30930 : NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolumn
  • ora-36380 : (AGGRECURSE) AGGREGATE was called recursively, which is not allowed.
  • ora-13025 : polygon does not close
  • ora-28200 : IDENTIFIED USING already specified
  • ora-31203 : DBMS_LDAP: PL/SQL - Init Failed.
  • ora-02383 : illegal cost factor
  • ora-15067 : command or option incompatible with diskgroup redundancy
  • ora-29366 : invalid CONSUMER_GROUP argument specified
  • ora-37016 : (XSACQUIRE01) You must specify objects to acquire for the ACQUIRE command.
  • ora-14601 : Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template
  • ora-22132 : hexadecimal string does not correspond to a valid REF
  • ora-34722 : (NLSCHARSET05) CAUTION: Character data loss in character set conversion from string to string
  • ora-22602 : pickler TDS handle [string] is not well-formed
  • ora-12054 : cannot set the ON COMMIT refresh attribute for the materialized view
  • ora-31625 : Schema string is needed to import this object, but is unaccessible
  • ora-07261 : spdde: kill error, unable to send signal to process.
  • 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.