Free Online Dictionary
ORA-26536
| ORACLE Data Base Messages | Download this dictionary |
ORA-26536
ORA-26536: Message 26536 not found; product=RDBMS73; facility=ORA
| Oracle8 Server Error Messages | Download this dictionary |
ORA-26536
refresh was aborted because of conflicts caused by deferred transactions
Section: 26500-26999 Replication
Notes: This section lists messages generated by replicatiuon.
- Refresh with REFRESH_AFTER_ERRORS, even if there are conflicts in the master site's DEFERROR table. If you proceed even with existing conflicts, an updatable snapshot's changes could appear to be temporarily lost. A refresh that succeeds after the conflicts are resolved should restore the changes.
Provided by PB for Oracle Professional.
Section: 26500-26999 Replication
Notes: This section lists messages generated by replicatiuon.
Cause: There are outstanding conflicts logged in the DEFERROR table at the snapshot's master site.
Action: Do one of the following:
- Resolve the conflicts in the master DEFERROR table and refresh again after the table is empty.- Refresh with REFRESH_AFTER_ERRORS, even if there are conflicts in the master site's DEFERROR table. If you proceed even with existing conflicts, an updatable snapshot's changes could appear to be temporarily lost. A refresh that succeeds after the conflicts are resolved should restore the changes.
Provided by PB for Oracle Professional.
| Oracle Error Messages - Description, Cause and Action | Download this dictionary |
ORA-26536
26536, 00000, "refresh was aborted because of conflicts caused by deferred transactions"
*Cause: There are outstanding conflicts logged in the DEFERROR table at
the snapshot'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 snapshot's changes appearing to be temporarily lost,
until a refresh succeeds after the conflicts are resolved.
*Cause: There are outstanding conflicts logged in the DEFERROR table at
the snapshot'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 snapshot's changes appearing to be temporarily lost,
until a refresh succeeds after the conflicts are resolved.
You think you have ethics...
Take the survey NOW!
