QSM-02037: cannot evaluate constant expression at compile time
Answer Posted / guest
Cause: The capability in question is not supported when the
materialized view uses a compile-time non-constant
expression in a filter condition in the WHERE or HAVING
clauses. For example, WHERE X=1 uses a compile-time constant
expression in a filter condition. WHERE
X=MY_PLSQL_FUNCTION() uses a compile-time non-constant
expression in a filter condition.
Action: Re-phrase the query to avoid the use of a
compile-time non-constant expressions in filter conditions.
Please add more information about this Error
Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
IMG-02003: 2FF03 - incorrect color histogram feature specification
ORA-26028: index string.string initially in unusable state
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............
IMP-00064: Definition of LOB was truncated by export
ORA-26027: unique index string.string partition string initially in unusable state
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
ORA-26029: index string.string partition string initially in unusable state
ORA-26079: file "string" is not part of table string.string
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-26094: stream format error: input column overflow
ORA-16626: failed to enable specified object
NZE-28868: Peer certificate chain check failed.
ORA-26032: index string.string loading aborted after string keys
IMP-00070: Lob definitions in dump file are inconsistent with database.