QSM-02176: MV with UNION ALL in a view is too complex
- 1 Answers
- 2484 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: If a materialized view has a view whose definition
involves a UNION ALL query, then the materialized view's
defining query cannot have any clauses other than SELECT or
FROM. Other clauses such as WHERE, HAVING, CONNECT BY, or
GROUP BY are not allowed. Further more, the FROM clause
should have only one item.
Action: Remove any clauses besides SELECT and FROM from the
materialized view's defining query.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-29294: A data error occurred during compression or uncompression.
PLS-00598: comparison of object with NULL using "string" is not allowed
ORA-31603: object "string" of type string not found in schema "string"
ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
SQL-02103: Inconsistent cursor cache. Out of range cursor cache reference
ORA-19644: datafile string: incremental-start SCN is prior to resetlogs SCN string
ORA-09956: scgcm: unexpected lock status condition
ORA-07476: slsget: cannot get mapped memory statistics.
NZE-28782: data source is not allocated
DRG-11603: URL store: payment required to access string
PROT-00707: Cluster registry integrity check failed
ORA-15066: offlining disk "string" may result in a data loss
Oracle Errors 
