ORA-26536: refresh was aborted because of conflicts caused
by deferred transactions
- 1 Answers
- 2422 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 site.
Action: Resolve the conflicts in the master DEFERROR table
and refresh again after the table is empty. Alternatively,
refresh with REFRESH_AFTER_ERRORS, even if there are
conflicts in the master's DEFERROR table. Proceeding despite
conflicts can result in 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 |
DRG-12607: only ctxsys can create MULTI_COLUMN preferences
QSM-01100: containment check failed for mv, string
ORA-27491: repeat_interval and start_date cannot both be NULL
NCR-03028: NCRO: Partner refused request for sender-makes-right.
ORA-36714: (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
ORA-02843: Invalid value for kernel flag
PCC-00095: Missing PROGRAM, SUBROUTINE, FUNCTION, or BLOCK DATA statement
NNO-00260: loading configuration data from checkpoint file "string"
ORA-01208: data file is an old version - not accessing current version
PCB-00109: Unable to open generated source file "string"
ORA-39038: Object path "string" is not supported for string jobs.
ORA-25533: FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified
Oracle Errors 
