ORA-32824: schedule exists for source string and destination string

Cause : An attempt was made to create a propagation schedule when one already exists for the specified source and destination pair.

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

Specify a different source and destination pair, or remove the schedule using that pair and retry the operation.

update : 19-08-2017

ORA-32824 - schedule exists for source string and destination string
ORA-32824 - schedule exists for source string and destination string

  • ora-16956 : Only SELECT or DML statements are supported for test execute.
  • ora-13129 : HHCODE column string not found
  • ora-25293 : Lob attributes must be null for buffered operations
  • ora-31153 : Cannot create schema URL with reserved prefix "http://xmlns.oracle.com/xdb/schemas/"
  • ora-01374 : _log_parallelism_max greater than 1 not supported in this release
  • ora-16037 : user requested cancel of managed recovery operation
  • ora-13603 : The specified parameter string cannot be fetched as a numeric value for task or object string.
  • ora-09925 : Unable to create audit trail file
  • ora-19278 : Invalid value: (string) for type: (string)
  • ora-13222 : failed to compute supercell for geometry in string
  • ora-31690 : Process name buffer size must be specified and must be greater than 0.
  • ora-13755 : invalid "SQL Tuning Set" name
  • ora-03112 : a server linked as single-task cannot use SQL*Net
  • ora-27147 : post/wait reset failed
  • ora-24788 : cannot switch to specified transaction (server type)
  • ora-12066 : invalid CREATE MATERIALIZED VIEW command
  • ora-36342 : (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL | STATUS ] [ AGGREGATES | CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]
  • ora-14610 : Lob attributes not specified for lob column string for subpartition string
  • ora-37130 : (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because you must specify AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over base workspace object.
  • ora-13783 : invalid tuning scope
  • ora-04076 : invalid NEW or OLD specification
  • ora-28235 : algorithm not available
  • ora-13141 : invalid RANGE window definition
  • ora-09760 : osnpui: cannot send break message
  • ora-16245 : paging in transaction string, string, string
  • ora-24042 : no propagation schedule exists for QUEUE string and DESTINATION string
  • ora-32035 : unreferenced query name defined in WITH clause
  • ora-36648 : (XSDUNION09) Concat dimension workspace object is already defined as UNIQUE.
  • ora-01306 : dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
  • ora-02761 : File number to be canceled is negative.
  • 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.