Interested to Buy Any Domain ? << Click Here >> for more details...
QSM-02176: MV with UNION ALL in a view is too complex
- 1 Answers
- 2965 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 |
RMAN-06708: short write while writing file "string". Wrote string bytes instead of string bytes
DRG-11445: rowid value is invalid: string
ORA-14167: only one subpartition may be moved
ORA-23333: column string is already part of a column group
PCC-02384: Missing array length specifier
PLS-00417: unable to resolve "string" as a column
ORA-38707: Media recovery is not enabled.
NNL-01010: Forwarding contexts allocated: number
ORA-16004: backup database requires recovery
ORA-21607: memory cartridge service handle not initialized
ORA-31604: invalid string parameter "string" for object type string in function string
ORA-37040: (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or internal partition workspace object is locked by another user.
Oracle Errors 
