ORA-32343: let MVIEW engine know that it is IMPORT from 9i or earlier
Cause: N/A
Action: Set this event only under the supervision of Oracle development. Not for general purpose use
https://support.oracle.com/
http://www.oracle.com/
Category Archives: ORA Database Error Messages
ORA-32342: The EXPLAIN_MVIEW facility failed to explain the materialized view statement
ORA-32342: The EXPLAIN_MVIEW facility failed to explain the materialized view statement
Cause: An error exists in the materialized view definition. As a result, the materialized view statement could not be explained
Action: Check the syntax of the statement. If it is a CREATE MATERIALIZED VIEW statement, then also check the PARAMETERs specified for the materialized view
ORA-32341: The EXPLAIN_MVIEW facility failed to explain the materialized view “string”.”string”
ORA-32341: The EXPLAIN_MVIEW facility failed to explain the materialized view "string"."string"
Cause: The dependent object(s) of the materialized view may have changed. The materialized view may no longer be valid
Action: Execute ALTER MATERIALIZED VIEW COMPILE and to determine the status of the materialized view in catalog views
ORA-32340: cannot tune the materialized view definition
ORA-32340: cannot tune the materialized view definition
Cause: Due to constructs in the materialized view definition, it could not be tuned to be fast-refreshable or rewriteable
Action: Execute DBMS_MVIEW.EXPLAIN_MVIEW to determine the cause
ORA-32339: cannot alter materialized view with the PMOP
ORA-32339: cannot alter materialized view with the PMOP
Cause: the materialized view is not allowed to have destructive PMOPS such as DROP, TRUNCATE and EXCHANGE (sub)partition. The UGA flag of i_am_a_refresh should be set first
Action: execute set_i_am_a_refresh first before alter materialized view with the PMOP
ORA-32338: on commit refresh grab all the detailed tables
ORA-32338: on commit refresh grab all the detailed tables
Cause: an event is set to let on-commit MV refresh to grab all the detailed tables, no matter whether they have modified or not
Action: none
ORA-32337: cannot alter materialized view with pending changes refresh on commit
ORA-32337: cannot alter materialized view with pending changes refresh on commit
Cause: There are some pending changes in the detail tables
Action: Execute an on-demand refresh on the materialized view to synchronize the data between the materialized view and the detail tables and then issue an ALTER MATERIALIZED VIEW statement
ORA-32336: cannot use USING NO INDEX to create materialized view “string”.”string”
ORA-32336: cannot use USING NO INDEX to create materialized view "string"."string"
Cause: The USING NO INDEX option was specified to create an updatable primary key based materialized view, an index-organized materialized view or an object-id materialized view
Action: Do not use the USING NO INDEX option to create an updatable primary key based materialized view, an index-organized materialized view or an object-id materialized view
ORA-32335: dimension must have at least one level
ORA-32335: dimension must have at least one level
Cause: An level-less dimension is not allowed
Action: Do not drop the only level of a dimension
ORA-32334: cannot create prebuilt materialized view on a table already referenced by a MV
ORA-32334: cannot create prebuilt materialized view on a table already referenced by a MV
Cause: the table on which the materialized view is created as prebuilt is already referenced by a materialized view
Action: create the materialized view on a different table