DBA_MVIEWS Shows STALENESS Value of UNKNOWN After Refresh
(Doc ID 757537.1)
Last updated on APRIL 07, 2020
Applies to:
Oracle Database Backup Service - Version N/A and laterOracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
Symptoms
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
When we use a function on a view which is used in an mview, or when a function is part of the mview itself, after mview refresh staleness becomes unknown, despite compile_state remains valid
Everything works fine if no function is used, so function may cause staleness to not know real status
Mview works fine, and refresh raises no issue, but staleness still shows same status.
Changes
TEST CASE:
----------
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |