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 : 29-06-2017

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-22812 : cannot reference nested table column's storage table
  • ora-30554 : function-based index string.string is disabled
  • ora-21709 : cannot refresh an object that has been modified
  • ora-36165 : (XSAGGCNTPROP) Variable workspace object cannot have both an AGGCOUNT and the $COUNTVAR property.
  • ora-02705 : osnpol: polling of communication channel failed
  • ora-15032 : not all alterations performed
  • ora-31074 : XML comment length string exceeds maximum string
  • ora-33018 : (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string.
  • ora-36670 : (XSDPART08) workspace object is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions.
  • ora-00475 : TRWR process terminated with error
  • ora-03112 : a server linked as single-task cannot use SQL*Net
  • ora-02175 : invalid rollback segment name
  • ora-01203 : wrong incarnation of this file - wrong creation SCN
  • ora-30946 : XML Schema Evolution warning: temporary tables not cleaned up
  • ora-30103 : 'string' contains an illegal integer radix for 'string'
  • ora-19689 : cannot have more than one %F in control file autobackup format(string) for string
  • ora-01523 : cannot rename data file to 'string' - file already part of database
  • ora-04082 : NEW or OLD references not allowed in table level triggers
  • ora-12326 : database string is closing immediately; no operations are permitted
  • ora-16030 : session specific change requires a LOG_ARCHIVE_DEST_n destination
  • ora-01568 : cannot set space quota on PUBLIC
  • ora-40222 : data mining model export failed, job name=string, error=string
  • ora-39172 : Cannot remap transportable tablespace names with compatibility of string.
  • ora-07612 : $GETUAI failed in retrieving the user's clearance level
  • ora-07578 : szprv: $FIND_HELD failure
  • ora-35021 : (QFCHECK08) The EIF file definition of workspace object has some partitions that are not present in the existing Analytic Workspace object.
  • ora-16258 : marking index unusable due to a constraint violation
  • ora-12079 : materialized view options require COMPATIBLE parameter to be string or greater
  • ora-06263 : NETNTT: out of memory in pi_connect
  • ora-24950 : unregister failed, registeration not found
  • 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.