ORA-25247: %s is not a recipient of specified message

Cause : The consumer name specified in the dequeue options is not a recipient of the message specified by the message id.

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

Ensure that the agent specified by the consumer name is a recipient of the message specified by the message id.

update : 30-05-2017
ORA-25247

ORA-25247 - %s is not a recipient of specified message
ORA-25247 - %s is not a recipient of specified message

  • ora-39701 : database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE
  • ora-13050 : unable to construct spatial object
  • ora-19525 : temporary file for the clone database must be renamed
  • ora-27065 : cannot perform async vector I/O to file
  • ora-24171 : creation properties are only for internal use
  • ora-23602 : Invalid streams process type string
  • ora-16642 : db_unique_name mismatch
  • ora-13404 : invalid ultCoordinate parameter
  • ora-31113 : XDB configuration may not be updated with non-schema compliant data
  • ora-24356 : internal error while converting from to COBOL display type.
  • ora-30750 : cannot enable column string to store objects of type string.string
  • ora-00300 : illegal redo log block size string specified - exceeds limit of string
  • ora-08189 : cannot flashback the table because row movement is not enabled
  • ora-26672 : timeout occurred while stopping STREAMS process string
  • ora-38495 : data type for the stored attribute string is inconsistent.
  • ora-23395 : object "string"."string" of type "string" does not exist or is invalid
  • ora-27214 : skgfrsfe: file search failed
  • ora-00965 : column aliases not allowed for '*'
  • ora-29936 : NULL association is allowed only with a column or an index
  • ora-02722 : osnpui: cannot send break message to orapop
  • ora-07484 : snlkput: cannot convert(put) lock.
  • ora-30350 : specified dimension attribute does not exist
  • ora-22855 : optional name for LOB storage segment incorrectly specified
  • ora-39094 : Parallel execution not supported in this database edition.
  • ora-23497 : repgroup name cannot be null
  • 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-39754 : FULL PARTITIONED OUTER JOIN is not supported
  • ora-12435 : invalid audit success: string
  • ora-00262 : current log string of closed thread string cannot switch
  • ora-28221 : REPLACE not specified
  • 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.