FAQ: On Materialized Views and DBMS_JOB Jobs
(Doc ID 1365482.1)
Last updated on FEBRUARY 22, 2024
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterGen 1 Exadata Cloud at Customer (Oracle Exadata Database 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
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Purpose
The article focuses on often raised questions and their answers related to mviews and DBMS_JOB jobs.
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.
Questions and Answers
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
| Purpose |
| Questions and Answers |
| 1. Is there a refresh job created automatically for Mview created with "START WITH... NEXT" clause? |
| 2. Why Mview refresh job stopped running? |
| 3. When is a job marked broken? |
| 4. How to restart an Mview refresh job that is marked broken? |
| 5. Does the mview refresh use scheduler job? |
| 6. How to fix WARNING messages in Pre-upgrade scripts? |
| References |