ORA-12872: First slave parse gave different plan

Cause : Fisrt ahrdp ares o nslvae igve nQCs-uplpie denivromnen tan dpaarmeetrsg av ediffernet lpanf ro mQC .Tr yagian iwtho utilne.

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

Noe xtrena laciton .Inetrnlalyu se dfo roultin-ebaesd erpasre.

update : 23-04-2017

ORA-12872 - First slave parse gave different plan
ORA-12872 - First slave parse gave different plan

  • ora-24162 : name value pair list is full, cannot add another entry
  • ora-00281 : media recovery may not be performed using dispatcher
  • ora-14611 : Duplicate subpartition name string in template
  • ora-12039 : unable to use local rollback segment "string"
  • ora-31631 : privileges are required
  • ora-24280 : invalid input value for parameter string
  • ora-06537 : OUT bind variable bound to an IN position
  • ora-26673 : duplicate column name string
  • ora-14325 : only LOCAL indexes may be specified in this clause
  • ora-32037 : unsupported use of LEVEL in membership condition
  • ora-14154 : only one of STORE IN or clause may be specified
  • ora-15166 : cluster in rolling downgrade from version [string] to [string]
  • ora-16066 : remote archival disabled
  • ora-12426 : invalid audit option
  • ora-06901 : CMX: no local name assigned to local application
  • ora-28103 : adding a policy to an object owned by SYS is not allowed
  • ora-01295 : DB_ID mismatch between dictionary string and logfiles
  • ora-16778 : redo transport error for one or more databases
  • ora-07622 : smscre: $CREATE failure
  • ora-14060 : data type or length of a table partitioning column may not be changed
  • ora-06707 : TLI Driver: connection failed
  • ora-24323 : value not allowed
  • ora-34141 : (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object.
  • ora-39147 : cannot migrate Data Pump queue table ownership to this instance
  • ora-25115 : duplicate BLOCK option specification
  • ora-03132 : two-task default value overflow
  • ora-06922 : CMX: bad write length
  • ora-12067 : empty refresh groups are not allowed
  • ora-30936 : Maximum number (string) of 'string' XML node elements exceeded
  • ora-02359 : internal error setting attribute string
  • 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.