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

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

  • ora-29964 : missing ADD or DROP keyword
  • ora-14132 : table cannot be used in EXCHANGE
  • ora-36847 : (XSLMGEN17) AW name is blank
  • ora-00977 : duplicate auditing option
  • ora-28543 : Error initializing apply connection to non-Oracle system
  • ora-30348 : ADD and DROP cannot both be specified
  • ora-13153 : invalid high water mark specified
  • ora-40253 : no target counter examples were found
  • ora-10943 : trace name context forever
  • ora-06312 : IPA: Incorrect outgoing service name supplied
  • ora-13043 : failed to read metadata from the _SDOLAYER table
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-37050 : (XSMLTDCL06) You cannot use the RELATION command with workspace object because analytic workspace string is attached in MULTI mode.
  • ora-24168 : rule string.string cannot have default evaluation context
  • ora-27044 : unable to write the header block of file
  • ora-33008 : (XSAGDNGL03) The relation workspace object is not a relation over a base dimension of AGGMAP workspace object.
  • ora-35578 : (SQLOUT11) SQL cursor 'number' cannot be used with CURRENT OF syntax
  • ora-01522 : file 'string' to be renamed does not exist
  • ora-28662 : IOT index and overflow segments must share the same LOGGING attribute
  • ora-16777 : unable to find the destination entry of a standby database in V$ARCHIVE_DEST
  • ora-06902 : CMX: cannot attach to cmx subsystem
  • ora-30555 : global index partitioning key is an expression
  • ora-29317 : datafile string does not exist
  • ora-09974 : skxfidini: Error Initializing SDI Channel
  • ora-32806 : value for string is too long, maximum length is string
  • ora-33084 : (XSAGDNGL42) In AGGMAP workspace object, you cannot qualify the dimensioned valueset workspace object.
  • ora-13777 : invalid list of attribute names
  • ora-23502 : valid directory for offline instatiation is not specified
  • ora-33315 : (XSDELDENTANON) You cannot delete workspace object while looping over unnamed composite workspace object.
  • ora-15121 : ASM file name 'string' contains an invalid diskgroup name
  • 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.