Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-23402: refresh was aborted because of conflicts caused
by deferred txns
- 1 Answers
- 4342 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-19300: Error occurred in uri processingstring
ORA-12902: default temporary tablespace must be SYSTEM or of TEMPORARY type
ORA-01936: cannot specify owner when creating users or roles
ORA-13334: LRS segments not connected
ORA-29933: object being disassociated has some user defined statistics stored
ORA-06117: NETTCP: unable to create ORASRV: quota exceeded
ORA-32336: cannot use USING NO INDEX to create materialized view "string"."string"
ORA-36206: (XSAGOP04R) In AGGMAP workspace object, REMOPERATOR string must be MIN, MAX, FIRST, LAST, HFIRST or HLAST.
PCC-02132: CMD-LINE: Could not allocate memory
ORA-39301: schema does not exist or is in use
PLS-00513: PL/SQL function called from SQL must return value of legal SQL type
ORA-01724: floating point precision is out of range (1 to 126)
Oracle Errors 
