ORA-26536: refresh was aborted because of conflicts caused
by deferred transactions
- 1 Answers
- 2168 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 |
ORA-33218: (CINSERT04) %K is not a valid value for the workspace object dimension. Values for this dimension can have at most number significant digits after rounding to number decimal places.
ORA-30690: timeout occurred while registering a TCP/IP connection for data traffic detection
ORA-02239: there are objects which reference this sequence
ORA-15072: command requires at least string failure groups, specified only string
RMAN-08514: archive log filename=string recid=string stamp=string
ORA-29535: source requires recompilation
ORA-31110: Action failed as resource string is locked by name
ORA-13115: [string]_EDGE$ table does not exist
ORA-00315: log string of thread string, wrong thread # string in header
DRG-10827: open_con must be performed before count_last
DRG-51313: timeout while waiting for DML or optimize lock
ORA-27062: could not find pending async I/Os
Oracle Errors 
