ORA-24067: exceeded maximum number of subscribers for queue string

Cause : An attemptw as mdae toa dd nwe subcsribesr to hte spceifie,d butt he nmuber fo subcsribesr fort his uqeue ahs execededt he mxaimumn umbe r(102)4 of usbscrbiers lalowe dper uqeue.

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

Remoev exitsing usbscrbiers ebforet ryin gto add news ubscirbers.

update : 21-08-2017
ORA-24067

ORA-24067 - exceeded maximum number of subscribers for queue string
ORA-24067 - exceeded maximum number of subscribers for queue string

  • ora-24400 : error occured while creating connections in the pool
  • ora-38764 : flashback not started; datafile string enabled threads are different
  • ora-24052 : cannot propagate object type payloads with LOB attributes to an 8.0 release
  • ora-06970 : X.25 Driver: remote host is unknown
  • ora-15177 : cannot operate on system aliases
  • ora-01593 : rollback segment optimal size (string blks) is smaller than the computed initial size (string blks)
  • ora-38730 : Invalid SCN/TIMESTAMP expression.
  • ora-24048 : cannot create QUEUE_TABLE, user does not have access to AQ object types
  • ora-16710 : the resource guard is out of memory
  • ora-23383 : registration for materialized view repgroup "string"."string" failed at site string
  • ora-30437 : all job queue processes have stopped running
  • ora-31513 : unsupported column type specified in change table
  • ora-31401 : change source string is not an existing change source
  • ora-31463 : logfile location string is an empty directory
  • ora-32008 : error while processing parameter update at instance string
  • ora-30929 : ORDER SIBLINGS BY clause not allowed here
  • ora-04067 : not executed, string does not exist
  • ora-06774 : TLI Driver: error sending break mode
  • ora-13156 : table to be registered string.string is not empty
  • ora-12921 : database is not in force logging mode
  • ora-12669 : Shared server: outbound protocol does not support proxies
  • ora-02706 : osnshs: host name too long
  • ora-03243 : destination dba overlaps with existing control information
  • ora-13202 : failed to create or insert into the SDO_INDEX_METADATA table
  • ora-01412 : zero length not allowed for this datatype
  • ora-30019 : Illegal rollback Segment operation in Automatic Undo mode
  • ora-24781 : branches don't belong to the same global transaction
  • ora-32406 : cannot alter partitioning for existing materialized view log
  • ora-15013 : diskgroup "string" is already mounted
  • ora-31440 : change set string is empty and cannot be advanced
  • 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.