| Materialised view won't refresh [message #645725] |
Mon, 14 December 2015 04:47  |
 |
brown_zzz
Messages: 39 Registered: August 2012 Location: United Kingdom
|
Member |
|
|
I have a materialised view that isn't refreshing and I can see this from the last refresh date on all_mviews, the underlying data has definitely changed. Looking at all_mviews table, the view is created as force refresh on commit. The columns from all_mviews are:
OWNER MVIEW_NAME CONTAINER_NAME QUERY_LEN UPDATABLE UPDATE_LOG MASTER_ROLLBACK_SEGCRD V_GEN_CONTACT2 V_GEN_CONTACT2 2436 N NULL NULL
MASTER_LINK REWRITE_ENABLED REWRITE_CAPABILITY REFRESH_MODE REFRESH_METHOD
NULL Y GENERAL COMMIT FORCE
BUILD_MODE FAST_REFRESHABLE LAST_REFRESH_TYPE LAST_REFRESH_DATE STALENESS
IMMEDIATE DIRLOAD_DML COMPLETE 19-NOV-15 IMPORT
AFTER_FAST_REFRESH UNKNOWN_PREBUILT UNKNOWN_PLSQL_FUNC UNKNOWN_EXTERNAL_TABLENA N N N
UNKNOWN_CONSIDER_FRESH UNKNOWN_IMPORT UNKNOWN_TRUSTED_FD COMPILE_STATE USE_NO_INDEX STALE_SINCE
N Y N VALID N 09-DEC-15
Not sure what the "import" value for the "staleness" columns means.
What is very strange is that the all_mviews column refresh_mode = COMMIT but when I look at the mview definition in SQLdeveloper (by clicking on the SQL tab for the mview) it says "REFRESH FORCE ON DEMAND" as part of the view definition, the "details" tab matches all_mviews and has a value of "COMMIT" for refresh mode.
Obviously I can force a refresh but this doesn't explain the problem.
Thanks for any help
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|