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-01416: Use of <id> (<value>...) here
ORA-24909: call in progress. Current operation cancelled
ORA-01152: file string was not restored from a sufficiently old backup
ORA-29807: specified operator does not exist
ORA-07562: sldext: extension must be 3 characters
ORA-24144: rules engine internal error, arguments: [string], [string]
ORA-39310: illegal clean_failed_clone() call: it only applys to failed clones
QSM-01127: query rewritten with multiple MVs
ORA-30686: no dispatcher accepted TCP/IP connection request
ORA-30374: materialized view is already fresh
DRG-12437: highlight table release failed
ORA-09985: SGA definition file could not be read