ORA-31514: change set string disabled due to capture error

Cause : This change set has encountered a capture error and was disabled.

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

Contact the change set's publisher to request that the capture error be resolved. Subscriptions using this change set cannot be activated or have their subscription windows extended or purged until the capture error is resolved.

update : 24-08-2017

ORA-31514 - change set string disabled due to capture error
ORA-31514 - change set string disabled due to capture error

  • ora-28515 : cannot get external object definitions from string
  • ora-31187 : Cannot Add Node 'string' (type='string') to Simple Type Node 'string'
  • ora-02446 : CREATE TABLE ... AS SELECT failed - check constraint violated
  • ora-31402 : unrecognized parameter string
  • ora-32587 : Cannot drop nonexistent string supplemental logging
  • ora-00310 : archived log contains sequence string; sequence string required
  • ora-00318 : log string of thread string, expected file size string doesn't match string
  • ora-32031 : illegal reference of a query name in WITH clause
  • ora-02436 : date or system variable wrongly specified in CHECK constraint
  • ora-16191 : Primary log shipping client not logged on standby
  • ora-06973 : X.25 Driver: invalid buffer size
  • ora-31096 : validation failed for schema
  • ora-26049 : Unscoped REF column has non-existent table name.
  • ora-36628 : (XSAGMODLIST03) MODEL workspace object could not be added to AGGMAP workspace object.
  • ora-14623 : Value string does not exist in subpartition string
  • ora-01293 : mounted database required for specified LogMiner options
  • ora-30019 : Illegal rollback Segment operation in Automatic Undo mode
  • ora-23603 : STREAMS enqueue aborted due to low SGA
  • ora-33223 : (CMOVE03) You cannot move a session-only dimension value.
  • ora-09871 : TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf.
  • ora-00473 : ARCH process terminated with error
  • ora-34360 : (MXDSS15) number other users writing
  • ora-12734 : Instant Client Light: unsupported client national character set string
  • ora-23470 : invalid status
  • ora-36837 : (XSLMGEN07) Dimension string.string!string is missing a COLUMNNAME property value
  • ora-30378 : MV_CAPABILITIES_TABLE is not compatible with Oracle version
  • ora-09946 : File name too long for buffer
  • ora-23308 : object string.string does not exist or is invalid
  • ora-14506 : LOCAL option required for partitioned indexes
  • ora-10580 : Can not modify datafile header during test recovery
  • 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.