ORA-25251: exceeded maximum number of recipients for message

Cause : An attempt was made to issue an ENQUEUE call that exceeded the the maximum number (1024) of recipients per message.

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

Reduce the number of recipients to 1024 or less, and retry the call.

update : 21-08-2017

ORA-25251 - exceeded maximum number of recipients for message
ORA-25251 - exceeded maximum number of recipients for message

  • ora-00028 : your session has been killed
  • ora-07287 : sksagdi: unsupported device for log archiving.
  • ora-15185 : Could not close dynamic library string, error [string]
  • ora-23415 : materialized view log for "string"."string" does not record the primary key
  • ora-13790 : invalid value for time limit
  • ora-01329 : unable to truncate required build table
  • ora-24000 : invalid value string, string should be of the form [SCHEMA.]NAME
  • ora-26736 : Data Pump error
  • ora-19227 : XP0007 - fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content.
  • ora-09761 : pw_destroyPorts: server call pws_stop_instance failed.
  • ora-24016 : cannot create QUEUE_TABLE, user string does not have execute privileges on QUEUE_PAYLOAD_TYPE string.string
  • ora-09957 : Unable to send termination request to IMON
  • ora-27477 : "string.string" already exists
  • ora-29896 : Length of PARAMETER string longer than string characters
  • ora-01022 : database operation not supported in this configuration
  • ora-19854 : error obtaining connect string from target
  • ora-33443 : (ESDREAD14) Discarding compiled code for workspace object because analytic workspace string is not attached.
  • ora-28028 : could not authenticate remote server
  • ora-02490 : missing required file size in RESIZE clause
  • ora-38957 : Target database not compatible
  • ora-12737 : Instant Client Light: unsupported server character set string
  • ora-29886 : feature not supported for domain indexes
  • ora-22851 : invalid CHUNK LOB storage option value
  • ora-27071 : unable to seek to desired position in file
  • ora-24045 : invalid agent address string, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]
  • ora-19689 : cannot have more than one %F in control file autobackup format(string) for string
  • ora-16006 : audit_trail destination incompatible with database open mode
  • ora-13497 : %s
  • ora-31180 : DOM Type mismatch in invalid PL/SQL DOM handle
  • ora-37115 : New OLAP API history is 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.