ORA-25243: CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string

Cause : An atetmpt wsa madet o deqeuue frmo an ecxeptio nqueueb y speicfyingt he COSNUMER_ANME int he deuqeue otpions.C ONSUMRE_NAMEc an onyl be sepcifie dwhen edqueuign froma normla queu ecreatde for umltipl econsuemrs.

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

Speciyf onlyt he message i din th edequeeu optinos to edqueuea messgae fro man execptionq ueue.

update : 19-08-2017

ORA-25243 - CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
ORA-25243 - CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string

  • ora-12451 : label not designated as USER or DATA
  • ora-19210 : column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string'
  • ora-26501 : RepAPI operation failure
  • ora-37139 : (XSCCOMP14) Cannot AGGREGATE workspace object using AGGMAP workspace object because you can not AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a PROTECT clause.
  • ora-38493 : feature not enabled : Expression Filter index
  • ora-02458 : HASHKEYS must be specified for a HASH CLUSTER
  • ora-10578 : Can not allow corruption for managed standby database recovery
  • ora-26035 : Error attempting to encrypt or decrypt column
  • ora-36804 : (XSTBLFUNC02) The OLAP_TABLE function encountered an error while parsing the LIMITMAP.
  • ora-28271 : No permission to read user entry in LDAP directory service.
  • ora-01306 : dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
  • ora-26056 : Requested direct path operation on a view is not supported.
  • ora-28154 : Proxy user may not act as client 'string'
  • ora-06510 : PL/SQL: unhandled user-defined exception
  • ora-13904 : The file has been dropped and recreated during the procedure call.
  • ora-28132 : Merge into syntax does not support security policies.
  • ora-07200 : slsid: oracle_sid not set.
  • ora-38860 : cannot FLASHBACK DATABASE during instantiation of a logical standby
  • ora-28031 : maximum of string enabled roles exceeded
  • ora-25331 : cannot downgrade because there are commit-time queue tables
  • ora-30749 : column string not enabled to store objects of type string.string
  • ora-18009 : one or more outline system tables do not exist
  • ora-30750 : cannot enable column string to store objects of type string.string
  • ora-37602 : (XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace string. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-01526 : error in opening file 'string'
  • ora-16160 : Cannot change protected standby database configuration
  • ora-28101 : policy already exists
  • ora-31029 : Cannot bind to unsaved resource
  • ora-00122 : cannot initialize network configuration
  • ora-02330 : datatype specification not allowed
  • 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.