QSM-02174: the materialized view does not have a UNION ALL
marker column
Answer Posted / guest
Cause: For a materialized view with UNION ALL to be fast
refreshable, it must have a UNION ALL marker column. This is
a constant column, at the same ordinal position in each
query block and must have distinct values in each query block.
Action: Add a UNION ALL marker column to each query block in
the UNION ALL query defining the materialized view.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
ORA-26027: unique index string.string partition string initially in unusable state
How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?
ORA-26030: index string.string had string partitions made unusable due to:
ORA-26084: direct path context already finished
ORA-16626: failed to enable specified object
ORA-26079: file "string" is not part of table string.string
In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.
ORA-16516: The current state is invalid for the attempted operation.
ORA-26095: unprocessed stream data exists
ORA-26029: index string.string partition string initially in unusable state
NZE-28868: Peer certificate chain check failed.
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
ORA-26032: index string.string loading aborted after string keys