Materialized View Stat Entries Accumulated Into USER_MVREF_RUN_STAT View, Even When COLLECTION_LEVEL is NONE
(Doc ID 2409928.1)
Last updated on APRIL 30, 2021
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Standard Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
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.
Mview-refresh-statistics gathering is an mview feature that is new in 12.2. Currently the mechanism collects information for the purpose of diagnostics/reporting. In future versions, these statistics may also be used to improve refresh performance.
The issues is: even after setting collection_level to NONE, when executing dbms_mview_stats.set_mvref_stats_params. Stats Entries will be accumulated into user_mvref_run_stats View every time when materialized view refreshed.
Here is the test case:
1. We start from a clean situation:
Now the MV has been dropped and the run stats entry is still there.
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