Oracle Database Errors or Warnings from Error ORA-32317 to ORA-32334
ORA-32317: cannot run a job from a job
Cause: An attempt was made to execute a job from within another job.
Action: Do not submit jobs that run other jobs.
ORA-32318: cannot rename a materialized view
Cause: Renaming a materialized view or its base table is not supported.
Action: Do not rename the base table of a materialized view.
ORA-32319: Cannot use direct loader log to FAST REFRESH materialized view “string”.”string”
Cause: The direct loader log might have been dropped
Action: Need to do complete refresh
ORA-32320: REFRESH FAST of “string”.”string” unsupported after container table PMOPs
Cause: A Partition Maintenance Operation (PMOP) has been performed on the materialized view, and no materialized view supports fast refersh after container table PMOPs.
Action: Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after PMOPs using the DBMS_MVIEW.EXPLAIN_MVIEW() API.
ORA-32321: REFRESH FAST of “string”.”string” unsupported after detail table TRUNCATE
Cause: A detail table has been truncated and no materialized view supports fast refersh after a detail table has been truncated
Action: Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after TRUNCATE using the DBMS_MVIEW.EXPLAIN_MVIEW() API.
ORA-32322: PCT refresh of “string”.”string” not allowed the sequence of DMLs/PMOPs
Cause: A table join dependent on another table on which PCT refresh is enabled has changed
Action: Use REFRESH FORCE which will pick the best possible refresh method on the materialized view
ORA-32330: invalid operation on online redefinition interim table “string”.”string”
Cause: An invalid operation was performed on an interim table which was being used for online redefinition of a table.
Action: Do not perform any unsupported operation on the interim table.
ORA-32331: type “string”.”string” is incompatible with the master site
Cause: A type used by the materialized view was found to be incompatible with its coressponding type on the master site. This could be because the type does not exist on the master site or has been evolved to a different version from that on the materialzied view site.
Action: Make sure that the types used by the materialized view are the same on both the materialized view and master sites.
ORA-32332: cannot refresh materialized view “string”.”string” as type evolution has occured
Cause: The types used by the materialized view or its master tables have been evolved.
Action: Ensure that the types used by the materialized view have been evolved to the same version at both the master and materialized sites. Then, before refreshing the materialized view, evolve the materialized view using ALTER MATERIALIZED VIEW.
ORA-32333: disable table scn update for Materialized view
Cause: an event is set for disabling table scn update to prevent deadlock situation. (bug 1376209)
Action: disable null refresh and/or base table scn update for Materialized view
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
Above are list of Oracle Database Errors or Warnings from Error ORA-32317 to ORA-32334 received while performing certain operation against Oracle Database or related products.
What are atOracle Database Error Messages?
Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.
Hope this was helpful.
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.