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-12509: TNS:listener failed to redirect client to service handler
ORA-31671: Worker process string had an unhandled exception.
ORA-34164: (MXCGVAR01) A dimension used to define a local string variable cannot be located. Execution cannot continue.
RMAN-00567: Recovery Manager could not print some error messages
ORA-22335: The client cannot work with an altered type
ORA-02057: 2PC: string: bad two-phase recovery state number string from string
RMAN-06420: some files could not be proxy restored - aborting restore
ORA-26510: materialized view name: 'string' is greater than max. allowed length of string bytes
ORA-39145: directory object parameter must be specified and non-null
SQL*Loader-00121: Invalid skip_unusable_indexes option
NZE-29194: no CRL found in cache
NID-00126: Database should have no datafiles in unknown state