Refresh Times Are Changing for Materialized Views (MV's)
(Doc ID 1595601.1)
Last updated on FEBRUARY 21, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A 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 a Materialized View (MV) is created with the 'START WITH' and 'NEXT' option, then n automated refresh is performed at the indicated intervals:
After the MV is created, it can happen that the timing for the refresh may have changed compared to the original definition.
Changes
The refresh of the MV was not possible at the normal times. Possible reasons are that the database was down at the time or busy with something else.
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 |