ORA-24037: schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE

Cause : Th escehmas peicfide i nth eQUUEE_ANMEp armaetre o fCRAETEQ_UEEU i sno tth esaem a sth escehmas peicfide i nth eQUUEE_ATBL Epaarmeetr.

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

Us eth esaem shcem anaem fro btoh hte UQEU_ENAEM adn QEUUET_ABEL praamteer san drerty hte ocmmnad.

update : 28-04-2017
ORA-24037

ORA-24037 - schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE
ORA-24037 - schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE

  • ora-38749 : A media recovery has been started.
  • ora-13362 : disjoint sub-element in a compound polygon
  • ora-16603 : Data Guard broker detected a mismatch in configuration ID
  • ora-12213 : TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
  • ora-38413 : elementary attribute name may not be longer than 32 characters
  • ora-09216 : sdnfy: bad value 'string' for parameter string
  • ora-07509 : scgfal: $deq parent lock unexpected return
  • ora-25443 : duplicate column value for table alias: string, column number: string
  • ora-27124 : unable to detach from shared memory segment
  • ora-08120 : Need to create SYS.IND_ONLINE$ table in order to (re)build index
  • ora-36167 : (XSAGGRFORM) workspace object is an illegal AGGMAP for aggregating a FORMULA.
  • ora-30653 : reject limit reached
  • ora-22979 : cannot INSERT object view REF or user-defined REF
  • ora-26747 : The one-to-many transformation function string encountered the following error: string
  • ora-24127 : TABLESPACE parameter specified with an ACTION other than CREATE_ACTION
  • ora-09823 : device name is too long
  • ora-23349 : cannot generate replication support for functions
  • ora-24409 : client cannot understand the object
  • ora-13367 : wrong orientation for interior/exterior rings
  • ora-23610 : internal dbms_streams_tablespaces error: [string] [string] [string] [string]
  • ora-31456 : error executing a procedure in the DBMS_CDC_UTILITY package
  • ora-32055 : invalid file type
  • ora-18002 : the specified outline does not exist
  • ora-22917 : use VARRAY to define the storage clause for this column or attribute
  • ora-19906 : recovery target incarnation changed during recovery
  • ora-23497 : repgroup name cannot be null
  • ora-14052 : partition-extended table name syntax is disallowed in this context
  • ora-29703 : error occurred in global enqueue service operation
  • ora-28661 : Object already has COMPRESS clause specified
  • ora-00287 : specified change number string not found in thread string
  • 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.