The following is the cause of this error:
There are outstanding conflicts logged in the DefError table at the materialized view's master.
Action you can take to resolve this issue: 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).
Tags: Database, Microsoft, Oracle, SQL, Software, DBMS, Error Messages, Directory
Disclaimer:Pak/ed and the contributors are not responsible for any errors contained and are not liable for any damages resulting from the use of this material. Disclaimer
Home Disclaimer Advertise Contact Privacy Policy
Copyright © 2004-16 Paked.com. All rights reserved.
Note: Site best viewed at 1024 x 768 or higher screen resolution