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-00585: declared support library for opaque type is not a library
ORA-13032: Invalid NULL SDO_GEOMETRY object
ORA-22062: invalid input string [string]
LSX-00286: duplicate key "~S" for {"~S"}"~S"
ORA-23466: flavor requires missing object "string"."string"
ORA-07285: sksaprd: volume size should not be specified for a disk file.
ORA-13214: failed to compute supercell for window object
ORA-01326: compatability of 9.0 or greater required to build into the logstream
LPX-00313: cannot construct XML comment with content: ~S
DRG-50806: failed to rollback
ORA-07210: slcpu: getrusage error, unable to get cpu time.
ORA-38445: TOP clause not allowed with no statistics