ORA-24041: propagation schedule exists for QUEUE string and DESTINATION string

Cause : A SCEHDULEP_ROPAAGTIONw as issued ofr a uqeue nad detsinatoin pari whihc hasa n exsitingp ropaagtions chedlue.

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

Issu eUNSCEHDULEP_ROPAAGTIONt o reomve teh exitsing csheduel andt hen erissu ethe CSHEDUEL_PROAPGATINO cal.l

update : 22-06-2017

ORA-24041 - propagation schedule exists for QUEUE string and DESTINATION string
ORA-24041 - propagation schedule exists for QUEUE string and DESTINATION string

  • ora-26679 : operation not allowed on LOB or LONG columns in LCR
  • ora-00478 : SMON process terminated due to error string
  • ora-06571 : Function string does not guarantee not to update database
  • ora-27073 : Trying to close a file which has async I/Os pending to be dequeued
  • ora-00115 : connection refused; dispatcher connection table is full
  • ora-15042 : ASM disk "string" is missing
  • ora-02007 : can't use ALLOCATE or DEALLOCATE options with REBUILD
  • ora-16633 : the only instance of the database cannot be removed
  • ora-24026 : operation failed, queue string.string has errors
  • ora-30971 : illegal operation on the Path Table
  • ora-01548 : active rollback segment 'string' found, terminate dropping tablespace
  • ora-00077 : dump string is not valid
  • ora-16594 : %s process discovered that DMON process does not exist
  • ora-00036 : maximum number of recursive SQL levels (string) exceeded
  • ora-01661 : tablespace 'string' is already temporary
  • ora-01145 : offline immediate disallowed unless media recovery enabled
  • ora-13034 : Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object
  • ora-16014 : log string sequence# string not archived, no available destinations
  • ora-10634 : Segment is already being shrunk
  • ora-36768 : (XSAGGCNTMOVE06) An aggregation variable and its AGGCOUNT must have the same base dimensions.
  • ora-08260 : ora_addr: cannot open nameserver
  • ora-19715 : invalid format string for generated name
  • ora-07454 : queue timeout, string second(s), exceeded
  • ora-24002 : QUEUE_TABLE string does not exist
  • ora-28611 : bitmap index is corrupted - see trace file for diagnostics
  • ora-24771 : cannot detach, prepare or forget a local transaction
  • ora-00712 : cannot rename system tablespace
  • ora-22976 : incorrect number of arguments to MAKE_REF
  • ora-23428 : job associated instance number string is not valid
  • ora-07740 : slemop: incorrect handle size (programming error)
  • 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.