QSM-02037: cannot evaluate constant expression at compile time
Answer / 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 |
DRG-12500: stoplist string already exists
ORA-15183: ASMLIB initialization error [string]
ORA-07454: queue timeout, string second(s), exceeded
ORA-27023: skgfqsbi: media manager protocol error
ORA-25156: old style outer join (+) cannot be used with ANSI joins
TNS-12570: TNS:packet reader failure
ORA-19761: block size string is not valid for change tracking file
NNL-00283: Next cache checkpoint occurs in string
TNS-01047: Old Parameter File string
ORA-02258: duplicate or conflicting NULL and/or NOT NULL specifications
ORA-06702: TLI Driver: cannot allocate context area
ORA-13225: specified index table name is too long for a spatial index