Oracle Database Errors or Warnings from Error ORA-12048 to ORA-12059
ORA-12048: error encountered while refreshing materialized view “string”.”string”
Cause: Some problem occurs during refresh of multiple materialized views in atomic mode. The materialized view whose refresh failed has raised this error.
Action: Examine the other messages on the stack to find the refresh problem.
ORA-12051: ON COMMIT attribute is incompatible with other options
Cause: ON COMMIT refresh attribute, incompatible with other refresh options such as automatic periodic refresh, was specified.
Action: Specify only valid options.
ORA-12052: cannot fast refresh materialized view string.string
Cause: Either ROWIDs of certain tables were missing in the definition or the inner table of an outer join did not have UNIQUE constraints on join columns.
Action: Specify the FORCE or COMPLETE option. If this error is got during creation, the materialized view definition may have be changed. Refer to the documentation on materialized views.
ORA-12053: this is not a valid nested materialized view
Cause: The list of objects in the FROM clause of the definition of this materialized view had some dependencies upon each other.
Action: Refer to the documentation to see which types of nesting are valid.
ORA-12054: cannot set the ON COMMIT refresh attribute for the materialized view
Cause: The materialized view did not satisfy conditions for refresh at commit time.
Action: Specify only valid options.
ORA-12055: materialized view definition contains cyclic dependencies with existing materialized views
Cause: The materialized view query definition introduced a cyclic dependency with existing materialized view.
Action: Modify the materialized view query definition.
ORA-12056: invalid REFRESH method
Cause: The NEVER REFRESH option may not be used under the following conditions:
* The materialized view is updatable
* The materialized view refreshes ON COMMIT
* Automatic refresh options are specified
Action: For updatable materialized views, reissue the SQL command using REFRESH FORCE, REFRESH FAST, or REFRESH COMPLETE. For read-only materialized views, reissue the SQL command using ON DEMAND.
ORA-12057: materialized view “string”.”string” is INVALID and must complete refresh
Cause: The status of the materialized view was INVALID and an attempt was made to fast refresh the materialized view.
Action: Perform a complete refresh of the materialized view. Check the value of the STATUS column in dba_mviews, all_mviews, or user_mviews to verify that the materialized view is VALID after the complete refresh.
ORA-12058: materialized view cannot use prebuilt table
Cause: An attempt was made to use the prebuilt tables.
Action: Reissue the SQL command using BUILD IMMEDIATE or BUILD DEFERRED.
ORA-12059: prebuilt table “string”.”string” does not exist
Cause: The specified prebuilt table did not exist.
Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table exists.
Above are list of Oracle Database Errors or Warnings from Error ORA-12048 to ORA-12059 received while performing certain operation against Oracle Database or related products.
What are Oracle Database Error Messages?
Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Database 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.