ELAPSED TIME IN DBA_MVREF_RUN_STATS MUCH LESS THAN ACTUAL MVIEW REFRESH TIME
(Doc ID 2627744.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterInformation in this document applies to any platform.
Goal
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.
Run the following mview refresh:
EXEC DBMS_MVIEW.REFRESH('<<<mview_name>>>', method => '?');
...it completes after 291 seconds.
But looking at the refresh stats:
SELECT * FROM DBA_MVREF_STATS WHERE mv_name = '<<<mview_name>>>' ORDER BY refresh_id DESC;
it shows only 189 seconds were taken. Why the difference of ~100 seconds?
Solution
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
| Goal |
| Solution |
| References |