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 |
ORA-31672: Worker process string died unexpectedly.
ORA-00261: log string of thread string is being archived or modified
ORA-16723: Setting AlternateLocation property conflicts with the log transport setting.
QSM-01061: illegal query expression
ORA-12811: PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string
ORA-16812: apply service not running on the apply instance recorded by the broker
ORA-00385: cannot enable Very Large Memory with new buffer cache parameters
ORA-28654: table and partition not overflow compatible
ORA-22130: buffer size [string] is less than the required size [string]
LSX-00220: "~1S" is wrong length, should be ~2d
ORA-16003: standby database is restricted to read-only access
PLS-01708: In searched DELETE, UPDATE or INSERT, table must not appear in FROM clause of subqueries in search condition