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 |
ORA-25140: %s space policy cannot be specified for the string extent management
ORA-14079: illegal option for a partition marked Index Unusable
ORA-00311: cannot read header from archived log
NPL-00102: missing stream functions in ASN.1 context initialization
SQL*Loader-00709: Internal error calling SLTS layer: string failed
TNS-00293: Trace File Name : string
ORA-13900: missing or invalid parameter string
ORA-02478: merge into base segment would overflow MAXEXTENTS limit
ORA-09853: snyRemovePort: bad return code from request.
ORA-39020: invalid mode type string
ORA-07596: sptpa: $GETJPIW failure
ORA-00321: log string of thread string, cannot update log file header