ORA-24065: propagation for QUEUE string and DESTINATION string already disabled

Cause : A DISABLE_SCHEDULE_PROPAGATION command was issued for a queue and destination pair whose propagation schedule already was disabled.

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

Make sure the QUEUE and DESTINATION are correct when you issue the DISABLE_SCHEDULE_PROPAGATION command.

update : 28-05-2017
ORA-24065

ORA-24065 - propagation for QUEUE string and DESTINATION string already disabled
ORA-24065 - propagation for QUEUE string and DESTINATION string already disabled

  • ora-16723 : setting AlternateLocation property conflicts with the redo transport setting
  • ora-30175 : invalid type given for an argument
  • ora-28507 : error in data dictionary view string
  • ora-32027 : There is no string column with the matching type in string.string.
  • ora-24355 : attempt to store a negative number in an Unsigned Display type.
  • ora-29538 : Java not installed
  • ora-31406 : change source string is referenced by a change set
  • ora-30384 : specified column name does not exist in the attribute
  • ora-12920 : database is already in force logging mode
  • ora-29657 : class defined in EXTERNAL NAME clause is used in another subtype
  • ora-02733 : osnsnf: database string too long
  • ora-13287 : can't transform unknown gtype
  • ora-23448 : duplicate user parameter value
  • ora-29381 : plan/consumer_group string referred to by another plan and cannot be deleted
  • ora-00366 : log string of thread string, checksum error in the file header
  • ora-22913 : must specify table name for nested table column or attribute
  • ora-12639 : Authentication service negotiation failed
  • ora-19163 : XP0004 - XQuery type mismatch: argument type mismatch: expected - 'string' got - 'string' for function 'string'
  • ora-32307 : must use FROM ONLY clause when referencing an object table
  • ora-37084 : Output valueset string must match string's dimensionality
  • ora-39704 : permission to modify component registry entry denied
  • ora-29312 : changes by release string cannot be used by release string, type: string
  • ora-09819 : Number exceeds maximum legal value
  • ora-25307 : Enqueue rate too high, flow control enabled
  • ora-36978 : (XSRELGID01) workspace object must be a self-relation.
  • ora-01251 : Unknown File Header Version read for file number string
  • ora-23400 : invalid materialized view name "string"
  • ora-30678 : too many open connections
  • ora-13411 : subset results in null data set
  • ora-19903 : test recovery not allowed when recovering to new incarnation
  • 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.