Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-23402: refresh was aborted because of conflicts caused
by deferred txns
- 1 Answers
- 4413 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: There are outstanding conflicts logged in the
DefError table at the materialized view's master.
Action: 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).
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-27144: attempt to kill process failed
DRG-12900: Operation:string for index: string has already been started
ORA-14253: table is not partitioned by Composite Range method
LPX-00316: invalid value ~S for ~S attribute ~S
ORA-38449: table "string" does not exist or is not accessible
ORA-26675: cannot create Streams capture process string
NNO-00119: line string: server not authoritative for name "string", data ignored
ORA-16025: parameter string contains repeated or conflicting attributes
TNS-12612: TNS:connection is busy
DRG-50701: error in listener.get_cmd()
ORA-02267: column type incompatible with referenced column type
RMAN-06751: ASM file string cannot be proxy backed up.
Oracle Errors 
