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 : 30-04-2017

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

  • ora-29348 : You must specify the datafiles to be plugged in
  • ora-09753 : spwat: invalid process number.
  • ora-38700 : Limit of string flashback database logs has been exceeded.
  • ora-26015 : Array column string in table string is not supported by direct path
  • ora-22992 : cannot use LOB locators selected from remote tables
  • ora-01218 : logfile member is not from the same point-in-time
  • ora-23387 : replication parallel push dequeue error
  • ora-24357 : internal error while converting from to OCIDate.
  • ora-32005 : error while parsing size specification [string]
  • ora-26036 : subpartition load specified but table string is not subpartitioned
  • ora-30490 : Ambiguous expression in GROUP BY ROLLUP or CUBE list
  • ora-30117 : syntax error at 'string' at the start of input
  • ora-30462 : unsupported operator: string
  • ora-37150 : line string, column string, string
  • ora-25140 : %s space policy cannot be specified for the string extent management
  • ora-02730 : osnrnf: cannot find user logon directory
  • ora-13417 : null or invalid layerNumber parameter
  • ora-28592 : agent control utility: agent SID not set
  • ora-31069 : Cannot apply typed changes to non-schema-based XMLType nodes
  • ora-28231 : no data passed to obfuscation toolkit
  • ora-01083 : value of parameter "string" is inconsistent with that of other instances
  • ora-30025 : DROP segment 'string' (in undo tablespace) not allowed
  • ora-37011 : (XSACQUIRE_LOCKED) Object workspace object is locked by another user.
  • ora-07252 : spcre: semget error, could not allocate semaphores.
  • ora-14071 : invalid option for an index used to enforce a constraint
  • ora-12407 : unauthorized operation for policy string
  • ora-33298 : (AWUPG01) Analytic Workspace string is already in the newest format allowed by the current compatibility setting
  • ora-09790 : sllfcf: unable to close file.
  • ora-07279 : spcre: semget error, unable to get first semaphore set.
  • ora-04077 : WHEN clause cannot be used with table level triggers
  • 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.