QSM-02176: MV with UNION ALL in a view is too complex
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 |
PLS-00568: cannot access rows from a non-nested table item
ORA-19562: file string is empty
ORA-23417: unknown materialized view type: string
ORA-10647: Tablespace other than SYSTEM, string, string not found in read only mode
ORA-01229: data file string is inconsistent with logs
ORA-01191: file string is already offline - cannot do a normal offline
ORA-31630: a job name is required to attach a job for user string
ORA-28652: overflow segment attributes cannot be specified
ORA-27414: Invalid BY value type
ORA-01237: cannot extend datafile string
NNL-00004: invalid command argument "string"
ORA-09317: szprv: insufficient privileges