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 : 25-09-2017

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

  • ora-32625 : illegal dimension in cell reference predicate
  • ora-13778 : no new name or owner specified for "SQL Tuning Set"
  • ora-29506 : invalid query derived from USING clause
  • ora-36639 : (XSDUNION18) UNIQUE cannot be applied to this concat dimension because leaves workspace object and workspace object share the value number.
  • ora-13705 : There was a instance shutdown/startup between the snapshots in the range [string, string].
  • ora-00112 : value of string is null
  • ora-28113 : policy predicate has error
  • ora-00057 : maximum number of temporary table locks exceeded
  • ora-08007 : Further changes to this block by this transaction not allowed
  • ora-23611 : tablespace "string" has more than one data file
  • ora-38471 : ROWIDs for table aliases cannot be null
  • ora-14037 : partition bound of partition "string" is too high
  • ora-31668 : Timeout before worker process string finished initialization.
  • ora-28341 : cannot encrypt constraint column(s) with salt
  • ora-31609 : error loading file "string" from file system directory "string"
  • ora-22870 : ALTER TYPE with REPLACE option a non-object type
  • ora-19609 : %s is from different backup set: stamp string count string
  • ora-30048 : Internal event for IMU auto-tuning
  • ora-12417 : database object "string" not found
  • ora-36198 : (XSAGGR33) The AGGREGATE operator string does not require a weight, but ARGS variable workspace object specified workspace object as a weight.
  • ora-38765 : Flashed back database cannot be opened read-only.
  • ora-22615 : attribute is not a collection
  • ora-01597 : cannot alter system rollback segment online or offline
  • ora-13706 : Invalid value "string" specified for parameter "string" in "string" analysis mode.
  • ora-00087 : command cannot be executed on remote instance
  • ora-25240 : message ID and dequeue condition/correlation ID specified in dequeue options
  • ora-12481 : effective label not within program unit clearance range
  • ora-13518 : Invalid database id (string)
  • ora-25145 : allocation policy already specified
  • ora-31059 : Cannot insert root XML document node if it already exists
  • 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.