Cause: The Summary Advisor external procedure initialization process failed.

Cause: A OCI callback routine reported an error

Cause: Summary Advisor failed to allocate the necessary memory.

Cause: An internal error occurred.

Cause: A syntax error occurred.

Cause: The fact-filter is not specified, and there are no fact-tables in the warehouse. A fact-table is a table having foreign-key constraints to one or more of the dimension-tables in the data warehouse.

Cause: The database does not have any dimensions

Cause: The system metadata does not contain statistics on one or more tables or columns. The Advisor needs cardinalities of all fact-tables, and of the level-keys of all dimensions in the data warehouse.

Cause: The indicated parameter has an invalid value

Cause: The system metadata does not contain statistics on one or more materialized views. The Advisor needs cardinalities of all materialized views in the data warehouse.

Cause: The tables specified in the fact-filter are not valid fact-tables. A fact-table must have foreign-key constraints to one or more of the dimension-tables in the data warehouse.

Cause: The summaries specified in the retention-list are not valid.

Cause: One or both of the workload tables are missing. The two workload tables which should be present in the user's schema are V_192216243_F_5_E_14_8_1 and V_192216243_F_5_E_15_8_1; the former is mapped to WORK$_IDEAL_MVIEW and the latter to WORK$_MVIEW_USAGE. The workload tables are created by the Oracle Trace Formatter when the data-collection-file (oraclesm.dat) is formatted by the user.

Cause: The specified space limit is greater than the size of must-retain summaries.

Cause: The operation has been cancelled by the user

Cause: The run has encountered an illegal value in the status field of the mview$_adv_log table. This could be internal error or an application error.

Cause: The current database has a compatibility setting that is earlier than the supported server version.

Cause: The current database has has not be created or upgraded to support Java stored procedures. Summary Advisor requires Java stored procedures.

Cause: The current database has has not be created or upgraded to support Summary Advisor. Summary Advisor requires several Java stored procedures.

Cause: SQL Access Advisor detected a severe error while accessing the advisor repository.

Cause: The user attempted to set a task parameter using invalid data.

Cause: Access Advisor could not create the script or report due to a file system error.

Cause: The user specified correct option keywords, but entered a combination that is not supported within Access Advisor.

Cause: The user attempted to set a task parameter using invalid data.

Cause: The user attempted to execute a advisor task that requires a workload.

Cause: The user attempted to save workload data into an existing workload that already contains data without specifying APPEND or REPLACE.

Cause: The user attempted to modify or delete a workload that is currently being used by another task.

Cause: The user attempted to delete invalid workload reference from the task.

Cause: The user attempted to access a workload parameter that is does not exist for the specified workload. The parameter may be misspelled or the user selected a parameter that is not supported by the particular advisor.

Cause: The user attempted to add a new SQL statement with an invalid username.

Cause: The user attempted to store data in the repository with an invalid import mode.

Cause: The user attempted to store data in the repository with an invalid priority.

Cause: The user attempted to import an advisor workload from an invalid or non-existent Summary Advisor workload.

Cause: The user attempted to import an advisor workload from a user who may not access to the table.

Cause: The user attempted to import an advisor workload from a user table that does not contain the required column.

Cause: The user attempted to import an advisor workload from a table that is not accessible.

Cause: The user attempted to create an entry in a workload collection without specifying a SQL statement.

Cause: The user attempted to collect a workload from the SQL without having authorization.

Cause: The user provided a invalid SEARCH argument to an Access Advisor workload operation. A search condition must be a valid SQL search condition using only the column names specified in the procedure documentation.

Cause: The user attempted to access a SQL statement that does not exist in the workload.

Cause: The user attempted to add a workload reference to a task when the task already contains the reference.

Cause: The user attempted to add a workload statement that contains table references that are either system-specified or user-specified invalid tables.

Cause: The user attempted to add a workload statement that contains invalid SQL syntax or an invalid column reference.

Cause: The task or workload parameter contains a name that is either too long or does not exist in the database.

Cause: While executing, the specified task found no valid SQL statements to analyze. Possible causes are: an empty workload, table filtering, or username filtering.

Cause: The user attempted to add a workload statement that contains one or more invalid identifier for the parsing user.

Cause: The user attempted to import a workload from an external table; however, the table does not contain all of the required columns.

Cause: The user attempted to create a directive that is not currently supported.

Cause: The user attempted to create a report or script in a file that cannot be written or created.

Cause: The user attempted to add a directive that cannot operate with an existing directive.

Cause: While attempting to execute a task, Access Advisor checks for exclusive access to all of the referenced workloads. If any cannot be reserved, then the execution fails.

Cause: The user attempted to set a task parameter using invalid data.

Cause: The user attempted to set a task parameter using invalid date formatting directives.

Cause: The user attempted to set a task parameter using invalid date formatting.

Cause: The user attempted to set a task parameter using an invalid username or table specification.

Cause: The user attempted to add an invalid directive to the current task.

Cause: The user attempted to add a directive that contains an empty or invalid object name.

Cause: The user attempted to add a directive that contains an empty or invalid tablespace name.

Cause: The user attempted to use the DBMS_ADVISOR.IMPLEMENT_TASK procedure to implement a SQL Access Advisor recommendation that cannot be implemented due to its complexity.

Cause: The user attempted to use the DBMS_ADVISOR.IMPLEMENT_TASK procedure to implement a SQL Access Advisor recommendation that cannot be implemented because it requires additional scripting information from the user.

Cause: The user attempted to change or delete a workload that is referenced by an active task.

Cause: The user attempted to add a workload statement that contains an invalid statement type. Supported statement types are INSERT, DELETE, UPDATE, SELECT and MERGE.

Cause: The user attempted to add a workload statement that contains a table without statistics. Access Advisor requires all referenced tables to have valid statistics.

Cause: The user specified a SQL Tuning Set that has not been defined in the SQL Tuning Set repository.

Cause: The user attempted to manually add a workload statement that failed a filter test. Manual statements must meet the same filtering guidelines as imported statements.

Cause: The user attempted to collect a workload from a SQL Tuning Set repository that has not yet been implemented or enabled.

Cause: The user attempted to add a workload statement that references a table with missing statistics.

Cause: The user attempted to reference an Access Advisor workload using a name that does not exist in the Advisor repository.

Cause: The user attempted to create the specified workload using a name that already exists in the Advisor repository. Task names must be unique to the database user.

Cause: The user has attempted to import a workload from an external table that does not exist or cannot be accessed.

Cause: The user has specified an invalid workload name.

Cause: The user has specified an invalid username.

Cause: While performing IMPLEMENT_TASK, a specific action operation failed.

Cause: While performing EXECUTE_TASK, the user specified a STORAGE_CHANGE value that is incompatible with the type of workload data.

Cause: While performing EXECUTE_TASK, the user specified a STORAGE_CHANGE value that leaves no space for mandatory access structures, such as primary key indexes.

Cause: The user has specified an invalid value when attempting to change a recommendation attribute.

Cause: While performing EXECUTE_TASK, the user specified a STORAGE_MODE of TOTAL, but failed to set the DEF_MVIEW_OWNER and DEF_INDEX_OWNER to valid owner names.

Cause: Though the ANALYSIS_SCOPE parameter supports several options, some combination are not supported.

Cause: The user attempted to set a task parameter using multiple keywords.

Cause: While executing GET_TASK_SCRIPT, an attempt was made to fetch a script having too many recommendations. The limit has been set in order to avoid possible performance and out-of-memory errors.

Cause: The user attempted to execute an unsupported advisor operation.

Cause: When query rewrite is disabled, no query rewrite will take place.

Cause: Query rewrite did not occur because the OPTIMIZER_MODE was set to RULE.

Cause: If query contains any data definition operations, no query rewrite will take place.

Cause: Internal session parameter _QUERY_REWRITE_2 is set to FALSE

Cause: Current prcess is a kxfx slave

Cause: During query rewrite, certain view query blocks cannot be rewritten.

Cause: When query contains a NOREWRITE hint, no query rewrite will take place for that query block.

Cause: If a query or part of it has any DML update operations, no query rewrite will take place.

Cause: The query was rewritten using a materialized view, because query text matched the definition of the materialized view

Cause: If the materialized view does not reference the base tables found in the query, it cannot be used for rewrite

Cause: When using a stored outline, a rewrite hint is required for query rewrite

Cause: If a query contains a SAMPLE clause, query rewrite will not take place

Cause: If the query contains nested aggregates, CONNECT BY clause, or START WITH clause, query rewrite will not take place

Cause: If the top-level operator in the WHERE clause is an OR and there is more than one table in the FROM list, then query rewrite will not take place.

Cause: No query rewrite, if there is no valid column in the GROUP BY clause.

Cause: No query rewrite, if the query contained any DISTINCT aggregates other than COUNT, MIN, MAX or ANY_VALUE.

Cause: Argument of each aggregrate in the query needs to be convertible into a canonical form for query rewrite.

Cause: Materialized join view is more expensive for rewrite than using the base table

Cause: There doesn't exist any materialized view in the dataware house that can be used to rewrite this query.

Cause: Materialized view is probably disabled or stale.

Cause: There is a rewrite hint list specified in the query, but this materialized view is not among the hinted ones.

Cause: Query Rewrite always chooses the most optimal materialized view based on certain parameters, such as cardinality of the materialized view, number of joins etc. The materialized view specified was found to be less optimal.

Cause: Materialized view probably has some metadata errors.

Cause: Materialized view probably has some metadata errors.

Cause: The specified materialized view is not found in the database.

Cause: Query rewrite could not use this materialized view, because query rewrite was not enabled for it.

Cause: Materialized view probably has some metadata errors.

Cause: Materialized view cannot be used for query rewrite while it is being refreshed

Cause: A stale materialized view cannot be used for query rewrite when the query rewrite integrity mode is set to ENFORCED.

Cause: A materialized view with PL/SQL functions in its definition cannot be used for query rewrite when query rewrite integrity is set to ENFORCED.

Cause: A stale materialized view cannot be used for query rewrite when the query rewrite integrity mode is set to TRUSTED.

Cause: There was no associated metadata for the materialized view.

Cause: The specified materialized view was used to rewrite the given query.

Cause: One or more hierarchical relationship(s) in the table(s) could not be established.

Cause: Any row level security policy that may exist on a base-table prevents exact text match query rewrite.

Cause: Clearing the columns after view merging failed due to some reasons - bug??

Cause: Join graph allocation and initialization failed, possibly due to one or more undetermined operand(s) in the query expression.

Cause: One or more logical operator(s) in the query predicates could not be processed, possibly due to invalid operator(s).

Cause: Query cannot be rewritten if any predicate contains a selection on the right hand side of an outer join.

Cause: Query rewrite will not take place if the joins in the query and the materialized view do not have any match.

Cause: If a measure (such as SUM, AVERAGE) in the query cannot be matched or computed from the materialized view, it will not be used for rewrite.

Cause: If there is a lossy join in the materialized view that doesn't exist in the query, query rewrite will not take place.

Cause: Query Rewrite will not occur if a join back is required to a table that appears to the right hand side of a semi or anti-join.

Cause: Query Rewrite will not occur if a join back to a table is required to find any missing columns.

Cause: Query Rewrite will not occur if a join back is required on a column that is referenced by a sub-query.

Cause: Query Rewrite can occur by means of a complex join back only during a MAV rewrite.

Cause: Query Rewrite requires joining back to a level of a dimension to find a missing information.

Cause: If there is a semi join in the query, then Query Rewrite will create (select distinct pk-list, ref-col from mjv) where pk-list is the list of rowids/pk of all mjv tables that don't correspond to a right side of a semi-join and ref-col are their columns. Query Rewrite will not occur if a join from the materialized view cannot match the semi-join from the query.

Cause: A column in the query cannot be computed from the materialized view.

Cause: No query rewrite if a window function is present on a column that requires a roll-up to compute a measure.

Cause: A join present in the materialized view requires validated primary/foreign key constraints in ENFORCED query rewrite integrity mode.

Cause: A join present in the materialized view requires RELY mode to be set on the primary/foreign key constraints.

Cause: There are no common joins between the query and the the materialized view

Cause: Join graph allocation and initialization failed, possibly due to one or more undetermined operand(s).

Cause: Some SELECT statements which are part of a DDL expression may be eligible for rewrite. These include CREATE AS SELECT and CREATE OUTLINE statements. The given query expression is a DDL expression, which doesn't fall in this category.

Cause: Current DML is being done using an updatable view, so it is not eligible for rewrite.

Cause: A GROUP BY column in the query is not present in the GROUP BY clause of of the materialized view. This usually requires a join back to a third table.

Cause: An illegal HAVING clause has been specified in the query.

Cause: When a HAVING clause has a subquery, then any references to the tables in the outer query should only reference the tables in the GROUP BY clause.

Cause: An illegal query was specified. Specifically one of the following criteria was not satisfied: (a) All (non-constant, non-aggregate) SELECT expressions in the query should be made up of group expressions. (b) All column references in the HAVING clause should come from the GROUP BY expressions. (c) If there is an ORDER BY clause, then all column references should come from the GROUP BY or SELECT clause, depending on whether the query selects DISTINCT.

Cause: Query rewrite is not possible if query has any manual partitions.

Cause: Query rewrite is not allowed if query references any dictionary tables/views.

Cause: Query rewrite is not allowed if query references any fixed tables/views

Cause: If the materialized view cannot compute a measure in the query using the measures in its definition, then query rewrite will not occur.

Cause: Query rewrite will not occur, if the materialized view cannot provide all the columns that the query has

Cause: An attempt was made to push a grouping function through an expression specified in the query to transform a measure. Query rewrite will not occur if this measure transformation failed.

Cause: An attempt was made to load a dimension from the dataware house, but there were no dimensions present.

Cause: An attempt to locate an object that is part of a join failed.

Cause: An equivalence class manager is required to compute the transitive closure for the columns in an equivalence class.

Cause: All lossy joins in the materialized view must be present in the query for query rewrite to occur.

Cause: Anchors, if any, in the MV and query match. But the joins between these anchors in the MV and query are different.

Cause: Query rewrite may not be possible if the materialized view has some joins that query does not have

Cause: Query rewrite may not be possible if the query has some joins that the materialized view does not have between the same pair of tables.

Cause: The specified aggregate function is not found in the materialized view.

Cause: To support an MJV rewrite, we require a materialized join view.

Cause: If a query column, which is not present in the materialized view, can be obtained by a rollup within the materialized view, then it should group at a higher level than the materialized view.

Cause: The materialized view's kglobsta field has KGLSINV bit set.

Cause: If any dependent tables of a materialized view undergoes a DML operation, query rewrite may be restricted depending on the query rewrite integrity mode for the session. In this situation, query rewrite will take place only if the rewrite integrity mode is STALE_TOLERATED.

Cause: This dimension table has authorization or compilation problems.

Cause: In order to obtain a missing column, the materialized view needs to join back to the above table. But it lacks the primary key or rowid for the table.

Cause: A column in the query is not found in the summary. To obtain the column, a join back of materialized view to the table by means of either the primary key, foreign key or rowid of the table is required. The specified materialized view does not have the primary key, foreign key or rowid of the table to perform the join operation.

Cause: During the query rewrite transformation, orignal query was possibly transformed into an inline view.

Cause: A table in a materialized view is an anchor, (a) if it is not joined to any other table or (b) joined to other tables but each of its joins is either lossy or lossless with the above table being child-side table. If an anchor which is present in the materialized view is not found in the query, then query rewrite will not take place.

Cause: There are no primary key, foreign key constraints between these tables. But query rewrite is still possible if the lossy join between the above tables also appear in the query

Cause: Query rewrite does not use dimensions in ENFORCED query rewrite integrity mode. If a suitable dimension is present, consider chaning the current integrity mode to either TRUSTED or STALE_ TOLERATED by using ALTER SESSION SET QUERY_REWRITE_INTEGRITY = command.

Cause: Query is grouping on undetermined columns.

Cause: General query rewrite is not possible if an inline view in the query does not have a matching materialized view in the meta data.

Cause: Internal session parameter _QUERY_REWRITE_1 is set to FALSE

Cause: When cost based optimizer is ON, cost of the rewritten cursor is compared to the cursor generated without query rewrite, and the cheaper one is chosen for execution.

Cause: Materialized join view tries to rewrite a semi-join (IN sub-query) and the primary keys or rowids of left tables of semi-joins are missing from MJV.

Cause: Materialized join view has outer join while the query inner join. For rewrite to succeed MV must have an anti-join marker like the rowid or primary key of the right tables of outer join

Cause: Materialized join view has outer join while the query inner join. For rewrite to succeed MV must have an anti-join marker like the rowid or primary key of the right tables of outer join

Cause: If materialized aggregate view contains grouping sets, then it also must contain the grouping_id() function. This function must contain all columns in the MV GROUP BY.

Cause: Materialized view with grouping sets contains duplicates and no rewrite is supported for it. For example, GROUP BY GROUPING SET ((a), (a)) is not supported for rewrite.

Cause: Materialized view with grouping sets has more that 64 different keys in its GROUP BY. No rewrite is supported then.

Cause: The materialized view contains a selection condition in the WHERE or HAVING clause that is more restrictive than the corresponding selection condition in the request query.

Cause: The materialized view is partially stale. It is stale with respect to one or more partitions in one or more of its detail tables. The request query references one or more such detail partitions.

Cause: The materialized view contains a selection condition in the WHERE or HAVING clause that is more restrictive than the corresponding selection condition in the request query.

Cause: If query's GROUP BY has one of the higher levels of columns found in the materialized view, then the lower level columns in the materialized view will be rolled up to compute the desired results.

Cause: A column in the query does not appear in the materialized view. Query rewrite will try to obtain this column from the base table, by doing a join back to that column with the MV.

Cause: Query rewrite does not support query with remote tables.

Cause: Query rewrite does not support flashback.

Cause: In order to obtain a missing column, the materialized view needs to join back to the above table. But it lacks the primary key or rowid for the table.

Cause: Query is requesting some data from the MV that are stale with respect to some partitions in the base tables due to some updates.

Cause: Query rewrite is disabled for PCT through a session parameter

Cause: Query rewrite engine cannot process the query if the number of disjuncts (OR's)in the WHERE clause exceeds the maximum allowed number. The number of disjuncts in the query and the maximum allowed disjuncts are given at the end of the message in the form of (no of disjuncts in query, maximum disjuncts allowed).

Cause: There was an unmatched join on the MV, so a table involved in the join was pushed to the query delta to see if the query can be rewritten

Cause: All lossy joins in the materialized view must be present in the query for query rewrite to occur.

Cause: In order to do query rewrite with fresh partitions of an MV, the MV should have a partiton key or partition marker.

Cause: The materialized view contains a selection condition in the WHERE clause that is more restrictive than the corresponding selection condition in the request query.

Cause: The materialized view contains a selection condition in the HAVING clause that is more restrictive than the corresponding selection condition in the request query.

Cause: There was a rollup to aggregate the data on a column with a window function.

Cause: The window function in the query could not be computed from the materialized view.

Cause: This query was possibly rewritten with an equivalence which doesn't allow further rewrites.

Cause: A stale materialized view created with USING TRUSTED CONSTRAINTS clause cannot be used when the query rewrite integrity mode is set ENFORCED.

Cause: The generalized self-join algorithm could not resolve the mutliple instances, likely due to mismatch in joins or measures

Cause: The specified set operator materialized view does not have a marker column.

Cause: Query Rewrite always chooses the most optimal set operator materialized view based on parameters, such as cardinality of the set operator materialized view, number of branches that the set operator materialized view can rewrite etc. The set operator materialized view specified was found to be less optimal.

Cause: The specified set operator materialized view was used to rewrite the given query.

Cause: The query was succesfully rewritten with multiple MVs

Cause: When multimv query rewrite is disabled, no multimv query rewrite will take place.

Cause: WHen the query has this hint no multimv rewrite will be tried for this query

Cause: When only multimv query rewrite is enabled, every query block should have at least one MV in it's from clause

Cause: When the query has this hint no multimv rewrite will be done if the query has a query block with no MVs in the from clause

Cause: When the query has a column of named array type, query rewrite cannot be done

Cause: When the query has a column of ADT type, query rewrite cannot be done

Cause: When the query has a hidden or nested table column, query rewrite cannot be done

Cause: When the query has a column stored in LOB, query rewrite cannot be done

Cause: When the query has a nested table column, query rewrite cannot be done

Cause: Join back is not possible on a level marked as SKIP WHEN NULL in a dimension

Cause: Query rewrite was not allowed during materialized view validation.

Cause: Query rewrite was not allowed with a stale materialized view if join back to a base table is required.

Cause: See the other messages from explain_rewrite() for explanation"

Cause: Query rewrite could not take place because Fine Grain Auditing (FGA) was present on a base table in the query

Cause: Query rewrite could not take place because the incoming query was either a CREATE or ALTER VIEW statement

Cause: Matching objects were not found between the query and the materialized view. Materialized view may contain only editioning views.

Cause: Query rewrite did not occur because the OPTIMIZER_MODE was set to RULE.

Cause: If query contains any data definition operations, no query rewrite will take place.

Cause: Internal session parameter _QUERY_REWRITE_2 is set to FALSE

Cause: Current prcess is a kxfx slave

Cause: When query contains a NOREWRITE hint, no query rewrite will take place for that query block.

Cause: If a query or part of it has any DML update operations, no query rewrite will take place.

Cause: The query was rewritten using a materialized view, because query text matched the definition of the materialized view

Cause: If the materialized view does not reference the base tables found in the query, it cannot be used for rewrite

Cause: When using a stored outline, a rewrite hint is required for query rewrite

Cause: If a query contains a SAMPLE clause, query rewrite will not take place

Cause: If the query contains nested aggregates, CONNECT BY clause, or START WITH clause, or recursive with clause, query rewrite will not take place

Cause: If the top-level operator in the WHERE clause is an OR and there is more than one table in the FROM list, then query rewrite will not take place.

Cause: No query rewrite, if there is no valid column in the GROUP BY clause.

Cause: Materialized join view is more expensive for rewrite than using the base table

Cause: There doesn't exist any materialized view in the database that can be used to rewrite this query.

Cause: Materialized view is probably disabled or stale.

Cause: Query Rewrite always chooses the most optimal materialized view based on certain parameters, such as cardinality of the materialized view, number of joins etc. The materialized view specified was found to be less optimal.

Cause: If a measure (such as SUM, AVERAGE) in the query cannot be matched or computed from the materialized view, it will not be used for rewrite.

Cause: Query Rewrite will not occur if a join back to a table is required to find any missing columns.

Cause: Query Rewrite will not occur if a join back is required on a column that is referenced by a sub-query.

Cause: Query Rewrite can occur by means of a complex join back only during a MAV rewrite.

Cause: Query Rewrite requires joining back to level of a dimension to find missing information.

Cause: No query rewrite if a window function is present on a column that requires a roll-up to compute a measure.

Cause: Some SELECT statements which are part of a DDL expression may be eligible for rewrite. These include CREATE AS SELECT and CREATE OUTLINE statements. The given query expression is a DDL expression, which doesn't fall in this category.

Cause: Current DML is being done using an updatable view, so it is not eligible for rewrite.

Cause: Query rewrite is not allowed if query references any dictionary tables/views.

Cause: A join from the materialized view to any table that eliminates some rows should be be present in the query. Otherwise query rewrite will not occur.

Cause: Query rewrite may not be possible if the materialized view has some joins that query does not have

Cause: Query rewrite may not be possible if the query has some joins that the materialized view does not have between the same pair of tables.

Cause: If any dependent tables of a materialized view undergoes a DML operation, query rewrite may be restricted depending on the query rewrite integrity mode for the session. In this situation, query rewrite will take place only if the rewrite integrity mode is STALE_TOLERATED.

Cause: In order to obtain a missing column, the materialized view needs to join back to the above table. But it lacks the primary key or rowid for the table.

Cause: A table in a materialized view is an anchor, (a) if it is not joined to any other table or (b) joined to other tables but each of its joins is not guaranteed to provide all the rows or joined with the above table being child-side table. If an anchor which is present in the materialized view is not found in the query, then query rewrite will not take place.

Cause: Materialized view has outer join while the query has inner join. For rewrite to succeed MV must have an anti-join marker like the rowid or primary key of the right tables of outer join

Cause: If materialized view contains grouping sets, then it also must contain the grouping_id() function. This function must contain all columns in the MV GROUP BY.

Cause: Materialized view with grouping sets contains duplicates and no rewrite is supported for it. For example, GROUP BY GROUPING SET ((a), (a)) is not supported for rewrite.

Cause: Materialized view with grouping sets has more that 176 different keys in its GROUP BY. No rewrite is supported then.

Cause: The materialized view contains a selection condition in the WHERE or HAVING clause that is more restrictive than the corresponding selection condition in the request query.

Cause: The materialized view is partially stale. It is stale with respect to one or more partitions in one or more of its detail tables. The request query references one or more such detail partitions.

Cause: Query rewrite does not support query with remote tables.

Cause: Query rewrite does not support flashback.

Cause: Query rewrite is disabled for PCT through a session parameter

Cause: Query rewrite engine cannot process the query if the number of disjuncts (OR's)in the WHERE clause exceeds the maximum allowed number. The number of disjuncts in the query and the maximum allowed disjuncts are given at the end of the message in the form of (no of disjuncts in query, maximum disjuncts allowed).

Cause: The window function in the query could not be computed from the materialized view.

Cause: A stale materialized view created with USING TRUSTED CONSTRAINTS clause cannot be used when the query rewrite integrity mode is set ENFORCED.

Cause: When the query has a column of named array type, query rewrite cannot be done

Cause: When the query has a column of ADT type, query rewrite cannot be done

Cause: When the query has a hidden or nested table column, query rewrite cannot be done

Cause: When the query has a column stored in LOB, query rewrite cannot be done

Cause: A materialized view specified by the user in the input was not used to rewrite the query, either because query rewrite failed or another more optimal materialized view was used to rewrite.

Cause: Query has an inline view with an aggregate. Such inline views cannot be matched to any inline views in materialized views.

Cause: Query's inline view does not have a match with any inline views in the materialized view

Cause: There is a mismatch between the joins in the query and materialized view inline views

Cause: When query block has a table involved in full outer join, query rewrite cannot be done

Cause: The general inline view rewrite could not take place because the query had remote objects

Cause: The general inline view rewrite was not supported with this WHERE clause construct

Cause: The general inline view rewrite could not take place because there were subqueries

Cause: General inline view rewrite cannot take place with nested inline views

Cause: No materialized view inline views were found to match with a query inline view

Cause: An inline view in the query contained an invalid WHERE clause predicate

Cause: Certain inline views are unsupported in general inline view rewrite

Cause: Certain inline views are unsupported in general inline view rewrite

Cause: There were no matching objects between the query inline view and materialized view inline views

Cause: Query inline view's and materialized view inline view's SELECT list items did not match.

Cause: Query rewrite's integrity mode should be set to stale_tolerated for query rewrite to occur on queries with remote objects

Cause: Query rewrite was disabled internally for queries referencing remote objects.

Cause: Multi-MV rewrite not possible for queries referencing remote objects.

Cause: Query rewrite against cube-organized materialized views was not possible because the OLAP option was off.

Cause: Query is rewritten with a stale materialized view by doing on-query computation

Cause: The query was rewritten using an equivalence, because query text matched the source statement for this equivalence.

Cause: Query Rewrite always chooses the most optimal equivalence based on certain parameters, such as cardinality of the equivalence, number of joins etc. The equivalence view specified was found to be less optimal.

Cause: Query rewrite could not use this equivalence, because this equivalence was created as disabled.

Cause: The specified equivalence was used to rewrite the given query.

Cause: If a measure in the query cannot be computed using the measures in the equivalence, then query rewrite will not occur.

Cause: An attempt was made to push a grouping function through an expression specified in the query to transform a measure. Query rewrite will not occur if this measure transformation failed.

Cause: Anchors, if any, in the equivalenceand query match. But the joins between these anchors in the equivalence and query are different.

Cause: A column in the query is not found in the equivalence. To obtain the column, a join back of equivalence to the table by means of either the primary key, foreign key or rowid of the table is required. But join backs are not allowed for equivalence rewrite

Cause: If an anchor which is present in the equivalence is not found in the query, then query rewrite will not take place.

Cause: If query's GROUP BY has one of the higher levels of columns found in the equivalence, then the lower level columns in the equivalence will be rolled up to compute the desired results.

Cause: A column in the query does not appear in the equivalence. Query rewrite will try to obtain this column from the base table, by doing a join back to that column with a materialized view. But join backs are not allowed for equivalence rewrite as the required constraints are not guaranteed to be found on the tables in the destination statement of the equivalence.

Cause: All lossy joins in the equivalence must be present in the query for query rewrite to occur.

Cause: There is an equivalence defition that could have been probably used by query rewrite to rewrite the query. But this equivalence is disabled.

Cause: This equivalence was created for text match rewrite only

Cause: An equivalence cannot be used for query rewrite when the query rewrite integrity mode is set to ENFORCED.

Cause: Query rewrite needs to do a join back to a base table column to answer this query. But join back is not allowed for an equivalence rewrite

Cause: The query was rewritten using an equivalence because query text matched the definition of the equivalence

Cause: A table in an equivalence is an anchor, if (a) it is not joined to any other table or (b) it is joined to other tables but each of its joins is not guaranteed to provide all the rows or joined with the above table being child-side table. If an anchor which is present in the equivalence is not found in the query, then query rewrite will not take place.

Cause: The source and destination statements of this equivalence MV are possibly identical. A recursive rewrite on this equivalence can lead to an infinite loop and thus not permitted.

Cause: There was a semijoin transformation attempted on an equivalence rewrite. Currently this is not allowed

Cause: The capability in question is not supported on a materialized view that has a clustered container table.

Cause: The capability in question is not supported when the materialized view uses the DISTINCT qualifier on an aggregate function.

Cause: The capability in question is not supported when the materialized view contains an aggregate function invocation nested within an outer expression.

Cause: The capability in question is not supported when the materialized view contains a column or expression in the GROUP BY clause that is not also present in the list of output select expressions.

Cause: The capability in question is not supported when a named view appears in the FROM list.

Cause: The capability in question is not supported when a subquery appears in the FROM list.

Cause: The capability in question is not supported when the same table or view occurs more than once in the FROM list.

Cause: The capability in question is not supported when the materialized view has a selection condition (an expression not representing a join) in the WHERE or HAVING clauses.

Cause: The capability in question is only supported with inner joins.

Cause: The capability in question is not supported when the materialized uses a relationship operator other than equals ("=") in a join in the WHERE clause. This is known as a non-equijoin.

Cause: The capability in question is not supported when the materialized view uses a HAVING clause.

Cause: The capability in question is not supported when the materialized view uses a CONNECT BY clause.

Cause: The capability in question is not supported when the materialized view uses RAW data type in an expression.

Cause: The capability in question is not supported when the materialized view uses an expression other than a simple column reference in the GROUP BY clause.

Cause: The capability in question is not supported when the materialized view references an Index Organized Table in the FROM list.

Cause: The capability in question is not supported when the materialized view references a clustered table in the FROM list.

Cause: The capability in question is not supported when the materialized view uses a subquery in the HAVING clause.

Cause: The capability in question is not supported when the materialized view uses a subquery in the WHERE clause.

Cause: The capability in question is not supported when the materialized view is nested (i.e., when it references another materialized view in its FROM list).

Cause: The capability in question is not supported when the materialized view's container table has a column that does not correspond to an output expression in the select list, and that column has a NOT NULL constraint. This situation can result in problems during refresh since any new rows inserted into the materialized view will set that column to NULL.

Cause: The capability in question is not supported when the materialized view uses set operators such as UNION, UNION ALL, MINUS, etc.

Cause: The capability in question is not supported when the materialized view uses an aggregate expression in the HAVING clause.

Cause: The capability in question is not supported when the materialized view uses a nested cursor expression.

Cause: The capability in question is not supported when the materialized view does not use a GROUP BY clause.

Cause: The capability in question is not supported when the materialized view uses no aggregate functions.

Cause: The capability in question is not supported when the materialized view uses a conjunction other than AND (such as OR) in the WHERE clause.

Cause: The capability in question is not supported when the materialized view uses the ROLLUP operator in the GROUP BY clause.

Cause: The capability in question is not supported when the materialized view uses the CUBE operator in the GROUP BY clause.

Cause: The capability in question is not supported when the materialized view invokes a PL/SQL function.

Cause: The capability in question is not supported when the materialized view is created with the WITH REDUCED PRECISION clause.

Cause: The materialized view cannot be used with query rewrite.

Cause: The capability in question is not supported when the materialized view includes no join conditions in the WHERE clause.

Cause: The capability in question is not supported when the materialized view includes no filter selection conditions in the WHERE clause.

Cause: The capability in question is not supported when the materialized view includes no joins in the HAVING clause.

Cause: The capability in question is not supported when the materialized view includes no filter condition in the HAVING clause.

Cause: The capability in question is not supported when the materialized view uses an IN list.

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.

Cause: The Partition Change Tracking (PCT) capability is supported for this materialized view.

Cause: The capability in question is not supported when the materialized view use grouping sets.

Cause: The capability in question is not supported when the materialized view uses a grouping set with too many keys.

Cause: The capability in question is not supported when the materialized view nests an aggregate function invocation as an argument to another aggregate function.

Cause: The capability in question is not supported when the materialized view references a view or subquery in the FROM list.

Cause: The capability in question is not supported when the materialized view includes an ORDER BY clause.

Cause: The capability in question is not supported when the materialized view includes a START WITH clause.

Cause: The capability in question is not supported when the materialized view uses a window function.

Cause: The capability in question is not supported when the materialized view uses an outer join.

Cause: The capability in question is not supported when the materialized view uses the ANY clause with a subquery.

Cause: The capability in question is not supported when the materialized view uses the ALL clause with a subquery.

Cause: The capability in question is not supported when the materialized view uses the NOT EXISTS with a subquery.

Cause: The capability in question is not supported when the materialized view uses a select list.

Cause: The capability in question is not supported when the materialized view uses a collection subquery.

Cause: The capability in question is not supported when the materialized view uses the DISTINCT clause in the select list.

Cause: The capability in question is not supported when the materialized view references a packed object table or view.

Cause: The capability in question is not supported when the materialized view uses a correlated variable and an outer join.

Cause: The capability in question is not supported when the materialized view references the ROWNUM function.

Cause: The capability in question is not supported when the materialized view uses a set operator and the compatibility mode is less than 9.0.

Cause: The capability in question is not supported when the materialized view contains a join condition that can result in duplicate rows in the materialized view.

Cause: The capability in question is not supported when the materialized view contains joins.

Cause: The capability in question is not supported when the materialized view uses the GROUP BY clause.

Cause: The capability in question is not supported when the materialized view uses an aggregate function.

Cause: The capability in question is not supported when the materialized view uses a subquery.

Cause: The capability in question is not supported because an attempt to create the materialized view would result in an error.

Cause: The capability in question is not supported when the materialized view unless the select list (and group by list if a GROUP BY clause is present) includes the partition key or PMARKER function reference to the table in question or an expression join dependent on the partitioning column of the table in question.

Cause: The capability in question is not supported when the relation in question is not a partitioned table.

Cause: The capability in question is not supported when the table in is partitioned on a multi-column key.

Cause: The capability in question is not supported when the table in question uses certain types of partitioning.

Cause: An internal Oracle error has occurred.

Cause: The capability in question is not supported because one or more of the requirements for this capability have not been satisfied.

Cause: Fast refresh is supported for RepAPI materialized views only if it is also a primary key materialized view.

Cause: The capability in question is not supported when the materialized view uses a heterogeneous link.

Cause: The capability in question is not supported when the materialized view references a synonym, if the compatible parameter is earlier than 10.2.0.

Cause: The timestamp of the sequence number in the mv log was after the last refresh time.

Cause: The capability in question is not supported when the relevant materialized view log was created after the creation or most recent complete refresh of the materialized view.

Cause: The capability in question is not supported when the relevant materialized view log omits new values.

Cause: The capability in question is not supported when the relevant materialized view log omits ROWIDs.

Cause: The capability in question is not supported when the relevant materialized view log omits primary keys.

Cause: The capability in question is not supported when the relevant materialized view log omits columns referenced in the select list of the materialized view.

Cause: The capability in question is not supported because of a problem the materialized view log in question.

Cause: The capability in question is not supported when the materialized view references a PL/SQL function that maintains state and which may not return the same value every time it is invoked against the same set of rows.

Cause: The capability in question is not supported when the materialized view uses the DISTINCT clause in this context.

Cause: The capability in question is not supported when the materialized view uses the MIN, MAX, or ANY_VALUE function.

Cause: The capability in question was not supported when the materialized view used the approximate aggregate detail function.

Cause: The capability in question is not supported when the materialized view omits any grouping expressions from the select list.

Cause: The capability in question is not supported when the materialized view uses an expression in the select list that is not a simple column reference.

Cause: The capability in question is not supported when the materialized view uses an expression that may not return the same value each time it is invoked against the same set of rows or that may return different values depending on session parameters.

Cause: The capability in question is not supported when the materialized view references a sequence number.

Cause: The capability in question is not supported when the materialized view uses an object REF clause.

Cause: The capability in question is not supported when the materialized view references a view.

Cause: The capability in question is not supported when the materialized view references a remote table or view in the FROM list.

Cause: The capability in question is not supported when the materialized view references a synonym in the FROM list.

Cause: The capability in question is not supported when the materialized view references an object in the SYS schema.

Cause: The capability in question is not supported when the materialized view references an aggregate function in a filter condition in the HAVING clause.

Cause: The capability in question is not supported when the materialized view includes a filter condition in the WHERE or HAVING clause.

Cause: The capability in question is not supported when the materialized view uses these types of joins.

Cause: The capability in question is not supported when the materialized view includes an expression in the select list that references multiple tables or views.

Cause: The capability in question is not supported when the materialized view has no GROUP BY clause, no aggregates and compatibility mode is less than 9.0.

Cause: The capability in question is not supported when the materialized view references a remote object and is refreshed ON COMMIT.

Cause: The capability in question is not supported when the materialized view references multiple remote objects that reside at different remote instances.

Cause: The capability in question is not supported when the materialized view uses grouping sets but omits the relevant GROUPING_ID or GROUPING functions.

Cause: The capability in question is not supported when the materialized view redundantly references grouping sets.

Cause: An internal Oracle error has occurred.

Cause: The capability in question is not supported when the compatibility mode is less than 9.0.

Cause: The capability in question is not supported when the materialized view uses a set operator in this context.

Cause: The capability in question is not supported when the compatibility mode is less than 8.1.

Cause: The capability in question is not supported when the materialized view is not a primary key materialized view and uses subqueries or the union operator in this context.

Cause: The capability in question is not supported when the materialized view references an object type in the WHERE clause.

Cause: The capability in question is not supported when the materialized view uses a subquery in a join in this way.

Cause: The capability in question is not supported when the materialized view references a remote site that does not support rowids.

Cause: The capability in question is not supported when the materialized view uses certain constructs and references an older version, remote Oracle instance.

Cause: The capability in question is not supported when the materialized view fails to meet the requirements of a primary key materialized view.

Cause: The capability in question is not supported when the materialized view uses a complex join or filter condition.

Cause: The capability in question is not supported when the materialized view references certain, complex expressions.

Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the SUM function on the same argument.

Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the COUNT function on the same argument.

Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the MIN function on the same argument.

Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the MAX function on the same argument.

Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the AVG function on the same argument.

Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the VARIANCE function on the same argument.

Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the STDDEV function on the same argument.

Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of that same aggregate function on the square of the same argument.

Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of that same aggregate function on the same argument added to the same argument.

Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the SUM function on the square of the same argument (the argument multiplied by itself).

Cause: The EXPLAIN_MV analysis engine has failed to capture the reason why the given capability is not possible.

Cause: The materialized view query omits COUNT(*) from the select list.

Cause: SUM(expr) occurs in the select list without a corresponding COUNT(expr).

Cause: One or more aggregate functions are present in the select list but a GROUP BY clause is not used.

Cause: A GROUP BY clause is used but no aggregate functions are present in the select list.

Cause: REFRESH_FAST_AFTER_ONETAB_DML is disabled for the same reason that REFRESH_FAST_AFTER_INSERT is disabled.

Cause: You have specified a date conversion operation using either the default format or an incomplete format. The default date format or an incomplete format is sensitive to session settings, and therefore may not be reproducible across different environments.

Cause: You have specified a many to many join in your materialized view while running in less than 9.0 compatibility mode.

Cause: You have specified a materialized view that uses some combination of the following: joins aggregation filter conditions in the WHERE clause a remote relation in the FROM list a SUM(x) function without a corresponding COUNT(x) function an omitted COUNT(*) aggregate function a MIN() or MAX() aggregate function in combination with the REFRESH ON COMMIT option while running in less than 9.0 compatibility mode.

Cause: You have specified a materialized view using the UNION operator and the respective queries on each side of the UNION operator do not have the same select list. The RELATED_NAME column shows the alias of the first different select list item. The RELATED_NUM column shows the offset from the SELECT keyword to the start of this select list item.

Cause: You have specified a materialized view that references a subquery or named view in its top level FROM list while running in less than 9.0 compatibility mode.

Cause: You have specified a materialized view that references a subquery ore named view in its top level FROM list that could not be merged during the view merging process.

Cause: You have specified a materialized view that references an inline view or a subquery. The indicated capability is not supported for this type of materialized view.

Cause: You have a materialized view with view in the FROM clause, however it does not meet the criteria for fast refresh after view merging.

Cause: REFRESH_FAST_AFTER_ANY_DML is disabled for the same reason that REFRESH_FAST_AFTER_ONETAB_DML is disabled.

Cause: The fast refresh cannot be performed because the master table does not contain a materialized view log.

Cause: The materialized view log either does not have object id columns logged, or the timestamp associated with the object id columns is more recent than the last refresh time.

Cause: Fast refresh of materialized aggregate views and/or materialized join views are not supported if they were defined using partition extended table names.

Cause: You have specified a materialized view using the UNION operator and the tables on each side of the UNION operator do not match. Fast refresh is not supported in this context.

Cause: Fast refresh is not supported if a materialized view having the UNION operator contains a join operation.

Cause: If there are outer joins, unique constraints must exist on the join columns of the inner table. Othwerwise, the materialized view can not be fast refreshable.

Cause: For a materialized view with UNION ALL to be fast refreshable, it must have a UNION ALL marker column. This is a constant column, at the same ordinal position in each query block and must have distinct values in each query block.

Cause: For a materialized view with UNION ALL to be fast refreshable, each query block must conform to a fast refreshable materialized join view or materialized aggregate view.

Cause: If a materialized view has a view whose definition involves a UNION ALL query, then the materialized view's defining query cannot have any clauses other than SELECT or FROM. Other clauses such as WHERE, HAVING, CONNECT BY, or GROUP BY are not allowed. Further more, the FROM clause should have only one item.

Cause: If a materialized view has a view whose definition involves a UNION ALL query, then the materialized view's select list must match the underlying view's select list exactly. It must not have any expressions and must not have add/drop/reorder columns from the underlying view.

Cause: The materialized view has a view whose definition involves a UNION ALL query that does not satisfy the requirements for fast refresh.

Cause: The setting of the COMPATIBLE initialization parameter is less than 9.2.0.

Cause: The explain_mview assumes that the materialized view is going to be created as the Primary Key materialized view. A Primary Key materialized view can not be created if the base table does not have a primary key constraint.

Cause: The capability in question is not supported when the materialized view uses a SPREADSHEET clause.

Cause: The capability in question is not supported when the materialized view does not contain some expression join dependent on the partitioning key of relation in question in the select list. For definition of join dependency, please look at Oracle documentation.

Cause: The capability in question is not supported when the expression is not in the PARTITION BY clause

Cause: The capability in question is not supported when the expression is rolled up

Cause: The capability in question is not supported when the materialized view unless the select list (and group by list if a GROUP BY clause is present) includes either the partition key of or a PMARKER function reference to the table in question.

Cause: The capability in question is not supported when the materialized view has PARTITIONED OUTER JOIN.

Cause: The capability in question is not supported when the materialized view references an external table.

Cause: You have specified a materialized view that references a named view The indicated capability is not supported for this type of materialized view.

Cause: The definition of the materialized view has changed. Usually redefining the synonym or table in the definition can cause this. The materialized view can not be fast refreshed.

Cause: The capability in question is not supported when the materialized view has sql PIVOT or UNPIVOT operation.

Cause: The capability in question is not supported when the materialized view is defined on detail tables which do not have a compatible type of materialized view logs, either all timestamp based or commit SCN based.

Cause: The capability in question is not supported when the relevant materialized view log is not in consistent state due to the failure when populating the mapping table of SYS.SNAP_XCMT$.

Cause: The capability in question is not supported when the relevant materialized view is not supported to be defined on detail tables which have commit SCN based MV logs.

Cause: The capability in question is not supported when the materialized view contain CASE expressions.

Cause: The capability in question was not supported because the materialized view query contained a named view.

Cause: The capability in question was not supported because the materialized view query contained an inline view.

Cause: The capability in question was not supported because the materialized view query contained a remote table.

Cause: The capability in question was not supported because the materialized view query HAVING clause included a subquery.

Cause: The capability in question was not supported because the materialized view query WHERE clause included a subquery.

Cause: The capability in question was not supported because the materialized view query contained LEFT OUTER, RIGHT OUTER or FULL OUTER JOIN.

Cause: The capability in question was not supported because the materialized view query contained self join of self cartesian product in the query.

Cause: The capability in question was not supported because the materialized view query contained an ORDER BY clause.

Cause: The capability in question was not supported because the materialized view query contained set operand query blocks.

Cause: The capability in question was not supported because the materialized view query contained an inner query.

Cause: The capability in question was not supported because the materialized view query contained a subquery inside a select-list.

Cause: The capability in question was not supported because the materialized view contained a join condition that can result in duplicate rows in the materialized view.

Cause: The capability in question was not supported because the materialized view query was too complex.

Cause: The capability in question was not supported when the materialized view uses NOT IN with a subquery.

Cause: The capability in question was not supported when the materialized view used a MATCH_RECOGNIZE clause.

Cause: The CREATE MATERIALIZED VIEW statement that was passed into the procedure was not a valid one.

Cause: The MATERIALIZED VIEW statement could not be tuned.

Cause: The materialized view was created with the FOR UPDATE option.

Cause: The materialized view was created on a prebuilt table.

Cause: The materialized view has the capabilities that are specified in the statement.

Cause: The materialized view could not be tuned or decomposed to be fast refreshable.

Cause: The materialized view could not be tuned for supporting general rewrite.

Cause: The WHERE/HAVING was too complex for general rewrite.

Cause: There were encrypted columns in materialized view defining query.

Cause: This table has met the criteria of a fact table for the purposes of synchronous refresh.

Cause: This table has met the criteria of a dimension table for the purposes of synchronous refresh.

Cause: This table has not met the necessary criteria of a fact table or a dimension table for the purposes of synchronous refresh. Synchronous refresh requires that the defining query of a materialized view conform to either the star or snowflake schema. A table can be either a fact or dimension table.

Cause: The defining query of the materialized view (MV) conformed to the star or snowflake schema and, therefore, was eligible for synchronous refresh.

Cause: The defining query of the materialized view (MV) did not conform to the star or snowflake schema and, therfore, was not eligible for synchronous refresh.

Cause: The fact table had the indicated partitioning method and key.

Cause: The materialized view (MV) had the indicated partitioning method and key.

Cause: The analysis by synchronous refresh indicated that the partition key of the fact table functionally determined the partition key of the materialized view (MV), which is a requirement for synchronous refresh eligibility.

Cause: The analysis by synchronous refresh indicated that the materialized view (MV) passed the partition key dependency eligibility check.

Cause: The analysis by synchronous refresh indicated that the materialized view (MV) did not pass the partition key dependency eligibility check.

Cause: The analysis by synchronous refresh indicated there was a rollup relationship between the partition keys of the fact table and the materialized view (MV).

Cause: The analysis by synchronous refresh indicated that the the partition key of the materialized view (MV) was related to a column of the fact table and not to the partition key of the fact table.

Cause: The analysis by synchronous refresh indicated that the partition key of the materialized view (MV) is the same as the partition key of the fact table.

Cause: The analysis by synchronous refresh indicated that the partition key of the materialized view (MV) was related to a column of a dimension table that was not the dimension table to which the partition key of the fact table was joined.

Cause: The analysis by synchronous refresh indicated that the partition key of the materialized view (MV) was not a column related to the partition key of the fact table.

Cause: The analysis by synchronous refresh indicated that the partition key of the materialized view (MV) was related to the partition key of the fact table by a join.

Cause: This table has met the necessary criteria of both a fact table and a dimension table for the purposes of synchronous refresh. Synchronous refresh requires that the defining query of a materialized view conform to either the star or snowflake schema. A table can be either a fact or dimension table.

Cause: More than one of the base tables of the materialized view was classified as a fact table for the purposes of synchronous refresh, which requires exactly one fact table. Synchronous refresh requires that the defining query of a materialized view conform to either the star or snowflake schema. A table can be either a fact or dimension table. However, only one (and exactly one) can be fact table and the rest must be dimension tables.

Cause: The materialized view was not partitioned and therefore was not eligible for synchronous refresh.

Cause: The analysis by synchronous refresh indicated that the partition key of the materialized view (MV) was related to a table other than the fact table.

Cause: The analysis by synchronous refresh indicated that the partition key of the fact table did not appear in the joins of the materialized view (MV).

Cause: The analysis by synchronous refresh indicated that the partition key of the fact table cannot be related to the partition key of the materialized view (MV).

Cause: An attempt was made to do synchronous refresh on a table or materialized view (MV) that used an unsupported partition method.

Cause: The staging log rows to be updated or deleted were not in the base table.

Cause: The staging log rows to be inserted were in the base table.

Cause: The staging log rows to be updated had exactly the same old and new values on all columns.

Cause: The USING TRUSTED CONSTRAINTS clause was not specified in the materialized view (MV) definition. Therefore, the MV was not eligible for synchronous refresh.

Cause: The refresh option specified in the materialized view (MV) definition was not supported for synchronous refresh. The only refresh option supported for synchronous refresh is REFRESH FORCE.

Cause: The ON COMMIT refresh option specified in the materialized view definition was not supported for synchronous refresh. The only refresh option supported for synchronous refresh is ON DEMAND.

Cause: The materialized view was in an invalid state or not fresh. Synchronous refresh requires the materialized view (MV) to be in a valid and fresh state when it is registered or prepared.

Cause: ROWID was used in the defining query of the materialized view.

Cause: RAW data type was used in the defining query of the materialized view.

Cause: MIN or MAX was used in the defining query of the materialized view.

Cause: The set operator was used in the defining query of the materialized view.

Cause: OUTER JOIN was used in the defining query of the materialized view.

Cause: A subquery was used in the defining query of the materialized view.

Cause: A trigger was used in the base table for synchronous refresh.

Cause: There was no materialized view defined on the base table.

Cause: A group by CUBE, ROLLUP, or grouping-sets was used in the defining query of the materialized view.

Cause: An object was used in the defining query of the materialized view, which was not a table type.

Cause: Either EXECUTE_REFRESH or ABORT_REFRESH returned an error because there was no active operation on the specified synchronous refresh group.

Cause: Either PREPARE_REFRESH or EXECUTE_REFRESH returned an error because the specified operation was not valid for the specified synchronous refresh group.

Cause: EXECUTE_REFRESH returned an error because all possible refresh subgroups had been processed and had a status of either COMPLETE or ABORT.

Cause: Either an illegal partition operation was specified in the register partition operation or the partition name was incorrectly specified.

Cause: The staging log contained changes to rows in the partition that were being registered. These changes occur due to changes specified in the staging log of the fact table or because of updates to dimension tables.

Cause: When registering the outside table, the user supplied the incorrect owner for the outside table.

Cause: PREPARE_REFRESH failed because the staging log for the specified table was not prepared with PREPARE_STAGING_LOG. All staging logs of tables of the group must be prepared before running PREPARE_REFRESH.

Cause: The specified materialized view (MV) has already been registered. A MV can be registered only once.

Cause: REGISTER_MVIEWS failed because the staging log for the specified table belonging to the materialized view (MV) being registered did not exist. All tables on a MV are required to have staging logs created on them for the MV to be registered for synchronous refresh.

Cause: PREPARE_REFRESH found that there was no materialized view (MV) registered for synchronous refresh that contained the specified fact table as one of its base tables and the changes to the dimension tables contained updates or deletes. This error will not occur if the changes to the dimension tables contain only inserts.

Cause: PREPARE_REFRESH found that there is no materialized view (MV) registered for synchronous refresh that contained the specified fact table as one of its base tables and the staging log for that table specified changes to it. PREPARE_REFRESH supports fact tables without MV's defined on them if they meet two conditions: a) the staging log for the fact table is empty; b) the staging logs for the dimension tables in the group do not specify deletes or updates.

Cause: Either REGISTER_PARTITION_OPERATION or UNREGISTER_PARTITION_OPERATION detected that the synchronous refresh group to which the table belonged had been locked by another synchronous refresh operation.

Cause: Either REGISTER_PARTITION_OPERATION or UNREGISTER_PARTITION_OPERATION detected that the synchronous refresh group to which the table belonged had been unlocked by another synchronous refresh operation. This is an internal error.

Cause: The lock operation on the specified synchronous refresh group failed unexpectedly. This is an internal error.

Cause: The unlock operation on the specified synchronous refresh group failed unexpectedly. This is an internal error.

Cause: Either REGISTER_MVIEWS or PREPARE_REFRESH detected that the synchronous refresh group to be processed by the requested operation had been locked by another synchronous refresh operation.

Cause: Either EXECUTE_REFRESH or ABORT_REFRESH detected that the synchronous refresh group to be processed by the requested operation had been unlocked by another synchronous refresh operation. This is an unexpected condition and may indicate an internal error.

Cause: The value supplied for the specified parameter exceeded the maximum length allowed for that parameter.

Cause: The value supplied for the specified parameter was invalid.

Cause: The materialized views being registered were not defined on tables, but were defined on top of other types of objects such as views or materialized views. Synchronous refresh works only with materialized views defined on tables.

Cause: Either REGISTER_PARTITION_OPERATION or UNREGISTER_PARTITION_OPERATION detected that the partition operation name did not belong to the DROP, EXCHANGE or TRUNCATE value.

Cause: REGISTER_PARTITION_OPERATION or UNREGISTER_PARTITION_OPERATION detected that either: - This object was not registered for synchronous refresh. - The synchronous refresh group was not in the current run. - The object was not a table type.

Cause: REGISTER_PARTITION_OPERATION detected that there was already a partition maintenance operation (for example, DROP, EXCHANGE or TRUNCATE) registered on the specified partition of the base table.

Cause: REGISTER_PARTITION_OPERATION detected that there was no partition with the specified name in the base table.

Cause: REGISTER_PARTITION_OPERATION detected that the outside table schema or table name did not exist or was not valid.

Cause: REGISTER_PARTITION_OPERATION detected that the tablespace of the base table for any partition or subpartition did not match the tablespace of the outside partition table.

Cause: REGISTER_PARTITION_OPERATION detected that the outside partition table contained at least one record that was not within the partition range of the base table.

Cause: REGISTER_PARTITION_OPERATION detected the base table was not partitioned by RANGE on top.

Cause: The base table was composite-partitioned. The partition number of the outside partition did not match the number of subpartitions inside the specified partition of the base table.

Cause: UNREGISTER_PARTITION_OPERATION detected that there was no partition maintenance operation (for example, DROP, EXCHANGE and TRUNCATE) registered on the specified partition of the base table.

Cause: REGISTER_PARTITION_OPERATION detected that the partition name of the outside partition table did not match the subpartition name of base table.

Cause: There were no changes recorded for any tables in this group. The changes to a table can be provided in its staging log or by specifying partition change operations with REGISTER_PARTITION_OPERATION.

Cause: The user-specified schema of the staging log was different from the owning schema of the base table. They must be in the same schema if the schema of the staging log is specified.

Cause: This is an internal error as noted in the message.

Cause: This is an internal error related to tracing messages to the table SYNCREF_MESG. It occurs if the event 31904 is set to level 4 or 8 but the message table SYNCREF_MESG is not created in the SYS schema. Oracle does not support levels 4 and 8 in event 31904.

Cause: The base tables in the group refreshed successfully but one or more materialized views in the group did not. The status of the group for synchronous refresh operation was set to PARTIAL in this case.

Cause: The GROUP_ID specified as input to the refresh operation was not valid and does not identify a valid synchronous refresh group.

Cause: The staging log creation on the specified table failed because a table related to it by referential-integrity constraint has a materialized view which was registered for synchronous refresh with the REGISTER_MVIEWS command. Oracle requires that you first register the tables before registering any materialized view defined on them.

Cause: The specified materialized view was not registered for synchronous refresh.

Cause: The table of REGISTER_PARTITION_OPERATION did not define a foreign key constraint on its referred base table.

Cause: The table of REGISTER_PARTITION_OPERATION did not define a primary key constraint on it.

Cause: There was a complex materialized view in the synchronous refresh group.

Cause: This was an internal error in synchronous refresh.

Cause: A staging log was created on a flashback-enabled base table.