ORA-27373: unknown or illegal event source queue

Cause : The source queue specified for the event based job or event based schedule was either not found or was of the wrong type.

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

Check if the queue exists. If it does make sure it is a multiple consumer queue and it is a post 8.1 compatible queue. Single consumer queues and old-style queues cannot be used as event source queues.

update : 20-08-2017
ORA-27373

ORA-27373 - unknown or illegal event source queue
ORA-27373 - unknown or illegal event source queue

  • ora-13017 : unrecognized line partition shape
  • ora-06267 : NETNTT: bad state
  • ora-30023 : Duplicate undo tablespace specification
  • ora-01484 : arrays can only be bound to PL/SQL statements
  • ora-22286 : insufficient privileges on file or directory to perform string operation
  • ora-07246 : sfofi: open error, unable to open database file.
  • ora-24092 : invalid value string specified
  • ora-15014 : location 'string' is not in the discovery set
  • ora-06114 : NETTCP: SID lookup failure
  • ora-25472 : maximum open iterators exceeded
  • ora-01906 : BACKUP keyword expected
  • ora-25126 : Invalid name specified for BUFFER_POOL
  • ora-31617 : unable to open dump file "string" for write
  • ora-06431 : ssaio: Invalid Block number
  • ora-02087 : object locked by another process in same transaction
  • ora-26519 : no memory available to allocate
  • ora-39204 : No subsetting of tablespaces is allowed for transportable import.
  • ora-12353 : secondary stored object cannot reference remote object
  • ora-34840 : (OPCREATE01) The string option must be declared with datatype string.
  • ora-09340 : Specified ORACLE_SID is either invalid or too long
  • ora-01704 : string literal too long
  • ora-23405 : refresh group number string does not exist
  • ora-38764 : flashback not started; datafile string enabled threads are different
  • ora-25110 : NOSORT may not be used with a bitmap index
  • ora-16537 : child count exceeded
  • ora-01516 : nonexistent log file, datafile, or tempfile "string"
  • ora-13156 : table to be registered string.string is not empty
  • ora-28175 : incorrect certificate type
  • ora-02783 : Both post and wait functions were not specified
  • ora-15059 : invalid device type for ASM disk
  • 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.