ORA-24077: cannot create propagation schedule for EXCEPTION queue string.string

Cause : A SCHEDLUE_PROPAAGTION wa sissued ofr an EXECPTION qeuue. Proapgation cshedulesc an be cerated onyl for NOMRAL queuse.

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

To propgaate mesasges fro ma queues pecify hte queuet ype as ONRMAL.

update : 26-09-2017
ORA-24077

ORA-24077 - cannot create propagation schedule for EXCEPTION queue string.string
ORA-24077 - cannot create propagation schedule for EXCEPTION queue string.string

  • ora-01647 : tablespace 'string' is read only, cannot allocate space in it
  • ora-32309 : object mview type "string"."string" does not match the master table type
  • ora-01225 : thread number string is greater than MAXINSTANCES string
  • ora-19010 : Cannot insert XML fragments
  • ora-36389 : (XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J.
  • ora-30502 : system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
  • ora-31694 : master table string failed to load/unload
  • ora-22160 : element at index [string] does not exist
  • ora-12456 : label security startup in progress
  • ora-29297 : The compressed representation is too big
  • ora-01994 : GRANT failed: password file missing or disabled
  • ora-13295 : geometry objects are in different coordinate systems
  • ora-07581 : spstp: cannot derive SID from unexpected process name
  • ora-02202 : no more tables permitted in this cluster
  • ora-14280 : all rows in table do not qualify for specified subpartition
  • ora-30678 : too many open connections
  • ora-22971 : invalid datatype for PRIMARY KEY-based object identifier
  • ora-32161 : Cannot perform piecewise fetch
  • ora-14266 : data type or length of an index subpartitioning column may not be changed
  • ora-34143 : (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER.
  • ora-00603 : ORACLE server session terminated by fatal error
  • ora-25314 : a commit-time queue table cannot be migrated to 8.0
  • ora-23415 : materialized view log for "string"."string" does not record the primary key
  • ora-02723 : osnpui: cannot send break signal
  • ora-25216 : invalid recipient, either NAME or ADDRESS must be specified
  • ora-31640 : unable to open dump file "string" for read
  • ora-01090 : shutdown in progress - connection is not permitted
  • ora-03299 : cannot create dictionary table string
  • ora-09840 : soacon: Name translation failure.
  • ora-09821 : Numeric label is not valid
  • 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.