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

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

  • ora-08111 : a partitioned index may not be coalesced as a whole
  • ora-31484 : source database version must be at least 9.2.0.6 or greater
  • ora-19881 : Corrupted space bitmap for datafile string, block string backup aborted
  • ora-01596 : cannot specify system in string parameter
  • ora-24064 : propagation for QUEUE string and DESTINATION string already enabled
  • ora-22610 : error while adding a scalar to the image handle
  • ora-14121 : MODIFY DEFAULT ATTRIBUTES may not be combined with other operations
  • ora-25141 : invalid EXTENT MANAGEMENT clause
  • ora-01374 : _log_parallelism_max greater than 1 not supported in this release
  • ora-25258 : cannot register for notifications on an 8.0 style exception queue
  • ora-07265 : sppst: semop error, unable to increment semaphore.
  • ora-27547 : Unable to query IPC OSD attribute string
  • ora-12429 : label list range exceeded
  • ora-14297 : Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-31530 : could not find published column string for CDC subscriber view string.string
  • ora-09955 : scgcan: unexpected return status when canceling a lock
  • ora-19657 : cannot inspect current datafile string
  • ora-12513 : TNS:service handler found but it has registered for a different protocol
  • ora-38488 : attribute set already assigned to the column storing expressions
  • ora-34279 : (MXDCL37) CONCAT can only be used when defining a DIMENSION.
  • ora-02327 : cannot create index on expression with datatype string
  • ora-37050 : (XSMLTDCL06) You cannot use the RELATION command with workspace object because analytic workspace string is attached in MULTI mode.
  • ora-02396 : exceeded maximum idle time, please connect again
  • ora-19572 : cannot process file string, file is being being resized
  • ora-24774 : cannot switch to specified transaction
  • ora-07426 : spstp: cannot obtain the location of dbs directory.
  • ora-29513 : referenced class name too long
  • ora-01926 : cannot GRANT to a role WITH GRANT OPTION
  • ora-25268 : didnt dequeue in browse mode with get signature option
  • ora-25255 : incorrect subscription string 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.