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 : 30-04-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-39952 : only numbers can be specified as range values
  • ora-19563 : %s header validation failed for file string
  • ora-26080 : file "string" is not part of table string.string partition string
  • ora-32761 : Turn off Temp LOB Ref Count Feature
  • ora-29267 : illegal call
  • ora-07564 : sldext: wildcard in filename or extension
  • ora-14515 : only one aubpartition name can be specified
  • ora-24360 : Type Descriptor Object not specified for Object Bind/Define
  • ora-01605 : missing numbers in clause "string" of string
  • ora-13336 : failure in converting standard diminfo/geometry to LRS dim/geom
  • ora-13044 : the specified tile size is smaller than the tolerance
  • ora-29388 : plan/consumer_group string is part of more than one top-plan
  • ora-24195 : attemp to retrieve the name list of a map message with size exceeding 1024
  • ora-24152 : cannot drop evaluation context string.string with dependents
  • ora-03293 : Cluster to be truncated is a HASH CLUSTER
  • ora-10618 : Operation not allowed on this segment
  • ora-08413 : invalid compiler type in FORMAT parameter at string
  • ora-27123 : unable to attach to shared memory segment
  • ora-25457 : evaluation function string returns failure
  • ora-00370 : potential deadlock during kcbchange operation
  • ora-10262 : Don't check for memory leaks
  • ora-16023 : system string destination cannot be the same as session string destination
  • ora-02345 : cannot create a view with column based on CURSOR operator
  • ora-07460 : cannot set the RESOURCE_MANAGER_PLAN parameter
  • ora-23609 : unable to find directory object for directory string
  • ora-30514 : system trigger cannot modify tablespace being made read only
  • ora-29879 : cannot create multiple domain indexes on a column list using same indextype
  • ora-09818 : Number is too large
  • ora-32131 : bind data type cannot be changed
  • ora-25473 : cannot store string in rule action context
  • 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.