ORA-23402: refresh was aborted because of conflicts caused by deferred txns

Cause : There are outstanding conflicts logged in the DefError table at the materialized view's master.

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

Resolve the conflicts in the master DefError table and refresh again after the table is empty. Alternatively, refresh with refresh_after_errors set to TRUE, which will proceed with the refresh even if there are conflicts in the master's DefError table. Proceeding despite conflicts can result with an updatable materialized view's changes appearing to be temporarily lost (until a refresh succeeds after the conflicts are resolved).

update : 17-08-2017
ORA-23402

ORA-23402 - refresh was aborted because of conflicts caused by deferred txns
ORA-23402 - refresh was aborted because of conflicts caused by deferred txns

  • ora-06305 : IPA: Illegal message type
  • ora-39957 : invalid warning category
  • ora-23418 : cannot unregister the propagator who is currently in use
  • ora-14019 : partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
  • ora-39023 : Version string is not supported.
  • ora-01294 : error occurred while processing information in dictionary file string, possible corruption
  • ora-30339 : illegal dimension attribute name
  • ora-12531 : TNS:cannot allocate memory
  • ora-00479 : RVWR process terminated with error string
  • ora-07685 : sou2os: supervisor stack set error
  • ora-25222 : enqueue failed, complete sender info. not provided for a queue supporting non-repudiation
  • ora-15097 : cannot SHUTDOWN ASM instance with connected RDBMS instance
  • ora-30074 : GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE not allowed
  • ora-22064 : invalid NLS parameter string [string]
  • ora-26005 : Invalid handle for direct path load
  • ora-13284 : failure to copy geometry object for conversion in place
  • ora-26746 : DDL rule "string"."string" not allowed for this operation
  • ora-31463 : logfile location string is an empty directory
  • ora-27472 : invalid metadata attribute string
  • ora-02729 : osncon: driver not in osntab
  • ora-19259 : XQ0039 - duplicate parameter name string in function declaration
  • ora-33315 : (XSDELDENTANON) You cannot delete workspace object while looping over unnamed composite workspace object.
  • ora-32742 : Hang analysis initialize failed
  • ora-31068 : updateXML expected data format [string] instead of [string]
  • ora-26019 : Column string in table string of type string not supported by direct path
  • ora-39065 : unexpected master process exception in string
  • ora-19269 : XQ0049 - variable string defined multiple times
  • ora-22972 : NULL value not allowed in PRIMARY KEY-based object identifier
  • ora-31648 : Timeout before master process string finished initialization.
  • ora-13032 : Invalid NULL SDO_GEOMETRY object
  • 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.