DBA_MVIEWS Shows COMPILATION_ERROR in COMPILE_STATUS Column
(Doc ID 1414046.1)
Last updated on NOVEMBER 07, 2023
Applies to:
Oracle Database Cloud Service - Version N/A and laterOracle Database - Standard Edition - Version 9.2.0.6 to 11.2.0.3 [Release 9.2 to 11.2]
Oracle Database - Enterprise Edition - Version 9.2.0.6 to 11.2.0.3 [Release 9.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Symptoms
<Internal_Only* ***
The values of the COMPILE_STATUS column in DBA_MVIEWS are as follows:
- VALID
- NEEDS_COMPILE
- COMPILATION_ERROR
The first two are normal behavior. The compile_status will be 'VALID' right after a refresh but before there is DML on the primary table; it will be 'NEEDS_COMPILE' after there has been DML on the primary table.
The status of 'COMPILATION_ERROR', however, is not expected. This note is intended for a general audience, as an initial starting point for beginning diagnosis of the 'COMPILATION_ERROR' status.
Changes
A materialized view (mview) refresh has occurred, and the COMPILE_STATUS in DBA_MVIEWS now shows as 'COMPILATION_ERROR'.
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 |