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 |
TNS-00127: Missing Connection Manager name in TNSNET.ORA
ORA-32007: internal
ORA-30556: functional index is defined on the column to be modified
ORA-12497: maximum combined categories exceeds string
ORA-38713: Flashback Database logging is already turned on.
PROC-00006: User does not have permission to perform a cluster registry operation on this key.
ORA-26687: no instantiation SCN provided for "string"."string" in source database "string"
RMAN-06194: target database instance not started
ORA-29321: too many datafiles added since the point-in-time
ORA-26024: SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable
ORA-29311: export dump file was not generated by this database, string does not match
DRG-11121: failed to read from file string