Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
Cause: The Summary Advisor external procedure initialization process failed.
Action: Contact Oracle Support Services.
Cause: An OCI callback routine reported an error
Action: Contact Oracle Support Services.
Cause: Summary Advisor failed to allocate the necessary memory.
Action: Contact Oracle Support Services.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
Cause: A syntax error occurred.
Action: Correct syntax error if possible or contact Oracle Support Services.
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.
Action: Check whether:
Cause: The database does not have any dimensions.
Action: Create the dimensions in your warehouse.
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.
Action: Run ANALYZE on the tables and summaries in the warehouse to collect statistics.
Cause: The indicated parameter has an invalid value.
Action: Supply a value in the proper range.
Cause: The system metadata does not contain statistics on one or more summaries. The Advisor needs cardinalities of all summaries in the data warehouse.
Action: Run ANALYZE on the tables and summaries in the warehouse to collect statistics.
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.
Action: Check whether:
Cause: The summaries specified in the retention-list are not valid.
Action: Check:
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.
Action: Check whether the Formatter succeeded in formatting the data collection. Sometimes the V_192216243_F_5_E_14_8_1 (that is, WORK$_IDEAL_MVIEW) may not be created whereas the other table is created. The most likely cause of this is the initialization parameters needed to invoke mview-rewrite are not enabled. Check your documentation for all the initialization parameters which need to be set for mview-rewrite to occur. Another possibility is no GROUP BY queries were issued during the time the data was collected, in which case, run the Trace collection for a longer time to get a representative sampling of the queries issued in the data warehouse.
Cause: The specified space limit is greater than the size of must-retain summaries.
Action: Reduce the number of must-retain summaries or increase the space limit.
Cause: The operation has been cancelled by the user.
Action: No action required.
Cause: The run has encountered an illegal value in the status field of the mview$_adv_log table. This could be an internal error or an application error.
Action: Contact Oracle Support Services.
Cause: The current database has a compatibility setting that is earlier than the supported server version.
Action: Adjust the COMPATIBLE instance parameter to 8.1.0.0 or higher.
Cause: The current database has not been created or upgraded to support Java stored procedures. Summary Advisor requires Java stored procedures.
Action: Connect to the database as a user with SYSDBA privileges. Execute the ORACLE_HOME/javavm/install/initjvm.sql script. Next, execute the ORACLE_HOME/rdbms/admin/initqsma.sql script.
Cause: The current database has not been created or upgraded to support Summary Advisor. Summary Advisor requires several Java stored procedures.
Action: Connect to the database as a user with SYSDBA privileges. Execute the ORACLE_HOME/rdbms/admin/initqsma.sql script.
Cause: When query rewrite is disabled, no query rewrite will take place.
Action: Enable query rewrite with ALTER SESSION SET QUERY_REWRITE ENABLE command.
Cause: Query rewrite will not occur when OPTIMIZER_GOAL is set to rule based.
Action: Change optimizer goal with ALTER SESSION SET OPTIMIZER_GOAL = "goal" command, where goal can be one of "CHOOSE", "FIRST_ROWS" or "ALL_ROWS".
Cause: If query contains any data definition operations, no query rewrite will take place. Note that some SELECT statements which are part of a DDL expression may be eligible for rewrite. These include CREATE AS SELECT and CREATE OUTLINE statements.
Action: No action required.
Cause: When query contains a NOREWRITE hint, no query rewrite will take place for that query block.
Action: Remove the NOREWRITE hint from the query.
Cause: If a query has any SELECT FOR UPDATE operations, no query rewrite will take place.
Action: No action rquired.
Cause: The query was rewritten using a materialized view, because query text matched the materialized view text.
Action: No action required.
Cause: Either the materialized view does not reference the base tables found in the query or it was found to be ineligible by query rewrite.
Action: No action required.
Cause: When using a stored outline, a rewrite hint is required for query rewrite.
Action: No action required.
Cause: If a query contains a SAMPLE clause, query rewrite will not take place.
Action: No action required.
Cause: If the query contains nested aggregates, CONNECT BY clause, or START WITH clause, query rewrite will not take place.
Action: No action required.
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.
Action: No action required.
Cause: No query rewrite, if there is no valid column in the GROUP BY clause.
Action: No action required.
Cause: No query rewrite, if the query contains any DISTINCT aggregates other than COUNT, MIN, or MAX.
Action: No action required.
Cause: Unless a REWRITE hint is used or cost based rewrite is turned on,a single base table is not replaced with a materialized join view as this will likely be larger.
Action: No action required.
Cause: There doesn't exist any materialized view that can be used to rewrite this query.
Action: Consider creating a new materialized view.
Cause: Materialized view is probably disabled or stale.
Action: Consider refreshing the materialized view or enabling it for rewrite.
Cause: There is a rewrite hint list specified in the query, but this materialized view is not among the hinted ones.
Action: Include this materialized view in the rewrite hint list.
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 specified materialized view was found to be less optimal.
Action: To force using a materialized view, consider using a rewrite hint.
Cause: The specified materialized view is not found in the database.
Action: Check the spelling or create a new materialized view.
Cause: Query rewrite could not use this materialized view, because query rewrite was not enabled for it.
Action: Enable query rewrite for the materialized view with ALTER MATERIALIZED VIEW "mv" ENABLE QUERY REWRITE command, where "mv" is the name of the materialized view.
Cause: Materialized view cannot be used for query rewrite while it is being refreshed.
Action: Rerun the query, after the refresh operation is completed.
Cause: A stale materialized view cannot be used for query rewrite when the query rewrite integrity mode is set to ENFORCED.
Action: Refresh the materialized view or alter the rewrite integrity mode with ALTER SESSION QUERY_REWRITE_INTEGRITY = STALE TOLERATED command.
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.
Action: Consider running the query in STALE TOLERATED mode.
Cause: A stale materialized view cannot be used for query rewrite when the query rewrite integrity mode is set to TRUSTED.
Action: Refresh the materialized view or alter the rewrite integrity mode with ALTER SESSION QUERY_REWRITE_INTEGRITY = STALE TOLERATED command.
Cause: There was no associated metadata for the materialized view.
Action: Check the spelling and re-run the query.
Cause: The specified materialized view was used to rewrite the given query.
Action: No action required.
Cause: One or more hierarchical relationship(s) in the table(s) could not be established.
Action: Consider adding a level in the dimension to provide the missing intra-table relationships.
Cause: Query cannot be rewritten if any predicate contains a selection on the right hand side of an outer join.
Action: No action required.
Cause: Query rewrite will not take place if the joins in the query and the materialized view do not have any match.
Action: No action required.
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.
Action: No action required.
Cause: If there is a lossy join in the materialized view that doesn't exist in the query, query rewrite will not take place.
Action: No action required.
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.
Action: No action required.
Cause: Query Rewrite will not occur if a join back to a table is required to find any missing columns.
Action: No action required.
Cause: Query Rewrite will not occur if a join back is required on a column that is referenced by a sub-query.
Action: No action required.
Cause: Query Rewrite can occur by means of a complex join back only during a MAV rewrite.
Action: No action required.
Cause: Query Rewrite requires joining back to a level of a dimension to find a missing information.
Action: Consider creating a dimension.
Cause: A column in the query cannot be computed from the materialized view.
Action: Consider creating a dimension to supply the missing information.
Cause: No query rewrite if a window function is present on a column that requires a roll-up to compute a measure.
Action: No action required.
Cause: A join present in the materialized view requires validated primary/foreign key constraints in ENFORCED query rewrite integrity mode.
Action: Validate the constraint or change the integrity mode with ALTER SESSION SET QUERY_REWRITE_INTEGRITY = STALE_TOLERATED command.
Cause: A join present in the materialized view requires RELY mode to be set on the primary/foreign key constraints.
Action: Set the RELY mode with ALTER TABLE <table> MODIFY CONSTRAINT <constraint> RELY command. Alternatively validate the constraint with ALTER TABLE <table> VALIDATE CONSTRAINT <constraint>.
Cause: Join graph allocation and initialization failed, possibly due to one or more undetermined operand(s).
Action: No action required.
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.
Action: No action required.
Cause: Current DML is being done using an updatable view, so it is not eligible for rewrite.
Action: No action required.
Cause: A GROUP BY column in the query is not present in the GROUP BY clause of the materialized view. This usually requires a join back to a third table.
Action: No action required.
Cause: An illegal HAVING clause has been specified in the query.
Action: Correct the query syntax and run the query again.
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.
Action: Correct the error in the syntax and rerun the query.
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.
Action: Correct the error in the syntax and rerun the query.
Cause: Query rewrite is not possible if query has any manual partitions.
Action: No action required.
Cause: Query rewrite is not allowed if query references any dictionary tables or views.
Action: No action required.
Cause: Query rewrite is not allowed if query references any fixed tables or views.
Action: No action required.
Cause: If the materialized view cannot compute a measure in the query using the measures in its definition, then query rewrite will not occur.
Action: No action required.
Cause: Query rewrite will not occur, if the materialized view cannot provide all the columns that the query has.
Action: No action required.
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.
Action: No action required.
Cause: An attempt was made to load a dimension, but there were no dimensions present.
Action: No action required.
Cause: An attempt to locate an object that is part of a join failed.
Action: No action required.
Cause: All lossy joins in the materialized view must be present in the query for query rewrite to occur.
Action: No action required.
Cause: Anchors, if any, in the MV and query match, but the joins between these anchors in the MV and query are different.
Action: No action required.
Cause: Query rewrite may not be possible if the materialized view has some joins that query does not have
Action: No action required.
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.
Action: No action required.
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.
Action: No action required.
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.
Action: Consider refreshing the materialized view chaning the rewrite integrity mode to STALE_TOLERATED.
Cause: This dimension table has authorization or compilation problems.
Action: No action required.
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.
Action: No action required.
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.
Action: Consider building a dimension-table to provide the missing information.
Cause: During the query rewrite transformation, the original query was possibly transformed into an inline view.
Action: No action required.
Cause: A table in a materialized view is an anchor, if it is not joined to any other table, or 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.
Action: No action required.
Cause: There are no primary key or foreign key constraints between these tables. Query rewrite is still possible if the lossy join between the above tables also appears in the query.
Action: No action required.
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.
Action: No action required.
Cause: Query is grouping on undetermined columns.
Action: No action required.
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.
Action: No action required.
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.
Action: No action required.
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.
Action: No action required.
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.
Action: No action required.
Cause: If materialized aggregate view contains grouping sets, then it must also contain the grouping_id() function. This function must contain all columns in the MV GROUP BY.
Action: No action required.
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.
Action: No action required.
Cause: Materialized view with grouping sets has more that 64 different keys in its GROUP BY. No rewrite is supported.
Action: No action required.
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.
Action: Change the selection criteria in the request query to be at least as restrictive as the selection criteria in the materialized view, or drop and recreate the materialized view using less restrictive selection criteria.
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.
Action: Change the selection criteria of the request to restrict the query to only the fresh portion of the materialized view, ALTER {SYSTEM|SESSION} QUERY_REWRITE_INTEGRITY = STALE_TOLERATED, or refresh the materialized view.
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.
Action: Change the selection criteria in the request query to be at least as restrictive as the selection criteria in the materialized view, or drop and recreate the materialized view using less restrictive selection criteria.
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.
Action: No action required.
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 materialized view.
Action: No action required.
Cause: Query rewrite does not support query with remote tables.
Action: No action required.
Cause: Query rewrite does not support flashback.
Action: No action required.
Cause: The capability in question is not supported on a materialized view that has a clustered container table.
Action: Recreate the materialized view using a conventional container table.
Cause: The capability in question is not supported when the materialized view uses the DISTINCT qualifier on an aggregate function.
Action: Remove the DISTINCT qualifier.
Cause: The capability in question is not supported when the materialized view contains an aggregate function invocation nested within an outer expression.
Action: Re-phrase the expression such that the aggregate function invocation is not nested.
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.
Action: Include all GROUP BY expressions in the output select list.
Cause: The capability in question is not supported when a named view appears in the FROM list.
Action: Remove the named view from the FROM list.
Cause: The capability in question is not supported when a subquery appears in the FROM list.
Action: Remove the subquery from 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.
Action: Re-phrase the query to avoid multiple instances of the same table.
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 clause.
Action: Remove the selection filter expression.
Cause: The capability in question is only supported with inner joins.
Action: Re-phrase the query using an inner join. Remove any outer joins.
Cause: The capability in question is not supported when the materialized view uses a relationship operator other than equals ("=") in a join in the WHERE clause. This is known as a non-equijoin.
Action: Re-phrase the query to avoid the non-equijoin.
Cause: The capability in question is not supported when the materialized view uses a HAVING clause.
Action: Remove the HAVING clause.
Cause: The capability in question is not supported when the materialized view uses a CONNECT BY clause.
Action: Re-phrase the query to avoid use of the CONNECT BY clause.
Cause: The capability in question is not supported when the materialized view uses RAW data type in an expression.
Action: Remove the reference to the RAW 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.
Action: Re-phrase the query to use only simple column expressions 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.
Action: Remove the reference to the Index-Organized Table.
Cause: The capability in question is not supported when the materialized view references a clustered table in the FROM list.
Action: Remove the reference to the 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.
Action: Re-phrase the query to avoid the subquery in the HAVING clause.
Cause: The capability in question is not supported when the materialized view uses a subquery in the WHERE clause.
Action: Re-phrase the query to avoid the subquery in the WHERE clause.
Cause: The capability in question is not supported when the materialized view is nested (that is, when it references another materialized view in its FROM list).
Action: Re-phrase the query to avoid reference to the other materialized view.
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.
Action: Disable or remove the NOT NULL constraint.
Cause: The capability in question is not supported when the materialized view uses set operators such as UNION, UNION ALL, MINUS, and so on.
Action: Re-phrase the query to avoid the use of set operators.
Cause: The capability in question is not supported when the materialized view uses an aggregate expression in the HAVING clause.
Action: Re-phrase the query to avoid the use of an aggregate in the HAVING clause.
Cause: The capability in question is not supported when the materialized view uses a nested cursor expression.
Action: Re-phrase the query to avoid use of a nested cursor expression.
Cause: The capability in question is not supported when the materialized view does not use a GROUP BY clause.
Action: Re-phrase the query to use a GROUP BY clause.
Cause: The capability in question is not supported when the materialized view uses no aggregate functions.
Action: Re-phrase the query to use 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.
Action: Re-phrase the query to avoid use of the non-AND conjunction.
Cause: The capability in question is not supported when the materialized view uses the ROLLUP operator in the GROUP BY clause.
Action: Re-phrase the query to avoid use of the ROLLUP operator.
Cause: The capability in question is not supported when the materialized view uses the CUBE operator in the GROUP BY clause.
Action: Re-phrase the query to avoid use of the CUBE operator.
Cause: The capability in question is not supported when the materialized view invokes a PL/SQL function.
Action: Re-phrase the query to avoid use of PL/SQL functions.
Cause: The capability in question is not supported when the materialized view is created with the WITH REDUCED PRECISION clause.
Action: DROP the materialized view and re-create it without using the WITH REDUCED PRECISION clause.
Cause: The materialized view cannot be used with query rewrite.
Action: Examine the other messages and documentation to determine the cause of the problem.
Cause: The capability in question is not supported when the materialized view includes no join conditions in the WHERE clause.
Action: Re-phrase the query to include a join.
Cause: The capability in question is not supported when the materialized view includes no filter selection conditions in the WHERE clause.
Action: Add a filter condition.
Cause: The capability in question is not supported when the materialized view includes no joins in the HAVING clause.
Action: Re-phrase the query to include a join.
Cause: The capability in question is not supported when the materialized view includes no filter condition in the HAVING clause.
Action: Re-phrase the query to include a join.
Cause: The capability in question is not supported when the materialized view uses an IN list.
Action: Re-phrase the query to avoid the use of IN lists.
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 compile-time non-constant expressions in filter conditions.
Cause: The Partition Change Tracking (PCT) capability is supported for this materialized view.
Action: No action required.
Cause: The capability in question is not supported when the materialized view uses grouping sets.
Action: Re-phrase the query to avoid the use of grouping sets.
Cause: The capability in question is not supported when the materialized view uses a grouping set with too many keys.
Action: Reduce the number of grouping set 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.
Action: Re-phrase the query to avoid the nested aggregate function invocation.
Cause: The capability in question is not supported when the materialized view references a view or subquery in the FROM list.
Action: Re-phrase the query to avoid the use of views or subqueries in the FROM list.
Cause: The capability in question is not supported when the materialized view includes an ORDER BY clause.
Action: Remove the ORDER BY clause.
Cause: The capability in question is not supported when the materialized view includes a START WITH clause.
Action: Re-phrase the query to avoid the use of the START WITH clause.
Cause: The capability in question is not supported when the materialized view uses a window function.
Action: Re-phrase the query to avoid the use of window functions.
Cause: The capability in question is not supported when the materialized view uses an outer join.
Action: Re-phrase the query to avoid the use of outer joins.
Cause: The capability in question is not supported when the materialized view uses the ANY clause with a subquery.
Action: Re-phrase the query to avoid the use of the ANY clause.
Cause: The capability in question is not supported when the materialized view uses the ALL clause with a subquery.
Action: Re-phrase the query to avoid the use of the ALL clause.
Cause: The capability in question is not supported when the materialized view uses the NOT EXISTS clause with a subquery.
Action: Re-phrase the query to avoid the use of the NOT EXISTS clause.
Cause: The capability in question is not supported when the materialized view uses a select list.
Action: Re-phrase the query to avoid the use of a select list.
Cause: The capability in question is not supported when the materialized view uses a collection subquery.
Action: Re-phrase the query to avoid the use of collection subqueries.
Cause: The capability in question is not supported when the materialized view uses the DISTINCT clause in the select list.
Action: Re-phrase the query to avoid the use of the DISTINCT clause.
Cause: The capability in question is not supported when the materialized view references a packed object table or view.
Action: Re-phrase the query to avoid the use of packed object tables or views.
Cause: The capability in question is not supported when the materialized view uses a correlated variable and an outer join.
Action: Re-phrase the query to avoid the use of correlated variables or outer joins.
Cause: The capability in question is not supported when the materialized view references the ROWNUM function.
Action: Re-phrase the query to avoid the use of 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.
Action: Re-phrase the query to avoid the use of set operators or set the compatibility mode to 9.0 or higher.
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.
Action: Re-phrase the query to avoid the occurrence of duplicate rows in the materialized view.
Cause: The capability in question is not supported when the materialized view contains joins.
Action: Re-phrase the query to avoid the use of the joins.
Cause: The capability in question is not supported when the materialized view uses the GROUP BY clause.
Action: Re-phrase the query to avoid the use of the GROUP BY clause.
Cause: The capability in question is not supported when the materialized view uses an aggregate function.
Action: Re-phrase the query to avoid the use of aggregate functions.
Cause: The capability in question is not supported when the materialized view uses a subquery.
Action: Re-phrase the query to avoid the use of subqueries.
Cause: The capability in question is not supported because an attempt to create the materialized view would result in an error.
Action: Examine the associated Oracle error code in the RELATED_NUM column and the Oracle error text in the RELATED_TEXT column and address the problem.
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.
Action: Add the partition key or a PMARKER function reference to the select list (and the GROUP BY clause, if present).
Cause: The capability in question is not supported when the relation in question is not a partitioned table.
Action: Change the query to reference a partitioned table.
Cause: The capability in question is not supported when the table in question is partitioned on a multi-column key.
Action: Re-phrase the query to reference a table partitioned on a single column key.
Cause: The capability in question is not supported when the table in question uses certain types of partitioning.
Action: Re-phrase the query to reference a table that uses a type of partitioning that is supported for this capability.
Cause: An internal Oracle error has occurred.
Action: Contact Oracle Support Services.
Cause: The capability in question is not supported because one or more of the requirements for this capability have not been satisfied.
Action: Examine the relevant nested materialized view documentation in the Oracle9i Data Warehousing Guide and address the problem.
Cause: Fast refresh is supported for RepAPI materialized views only if it is also a primary key materialized view.
Action: Re-design the materialized view to be a primary key materialized view.
Cause: The capability in question is not supported when the materialized view uses a heterogeneous link.
Action: Re-design the materialized view to avoid the use of the heterogeneous links.
Cause: The capability in question is not supported when the materialized view references a synonym.
Action: Re-phrase the query to avoid the use of synonyms.
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.
Action: Perform a complete refresh of the materialized view.
Cause: The capability in question is not supported when the relevant materialized view log omits new values.
Action: Re-create the materialized view log using the NEW VALUES clause.
Cause: The capability in question is not supported when the relevant materialized view log omits ROWIDs.
Action: Re-create the materialized view log using the ROWID clause.
Cause: The capability in question is not supported when the relevant materialized view log omits primary keys.
Action: Re-create the materialized view log using the PRIMARY KEY clause.
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.
Action: Re-create the materialized view log and include all columns referenced in the select list.
Cause: The capability in question is not supported because of a problem with the materialized view log.
Action: Examine the relevant materialized view log and fast refresh documentation in the Oracle9i Data Warehousing Guide and address the problem.
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.
Action: Either re-phrase the query to avoid such a PL/SQL function or modify the PL/SQL function to avoid state maintenance and change its declaration accordingly.
Cause: The capability in question is not supported when the materialized view uses the DISTINCT clause in this context.
Action: Re-phrase the query to avoid the use of the DISTINCT clause.
Cause: The capability in question is not supported when the materialized view uses the MIN or MAX function.
Action: Re-phrase the query to avoid the use of the MIN or MAX functions.
Cause: The capability in question is not supported when the materialized view omits any grouping expressions from the select list.
Action: Include all GROUP BY expressions in 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.
Action: Re-phrase the query to avoid the use of the expressions that are not simple column references.
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.
Action: Re-phrase the query to avoid the use of such expressions.
Cause: The capability in question is not supported when the materialized view references a sequence number.
Action: Re-phrase the query to avoid the reference to sequence numbers.
Cause: The capability in question is not supported when the materialized view uses an object REF clause.
Action: Re-phrase the query to avoid the use of an object REF clause.
Cause: The capability in question is not supported when the materialized view references a view.
Action: Re-phrase the query to avoid references to views.
Cause: The capability in question is not supported when the materialized view references a remote table or view in the FROM list.
Action: Re-phrase the query to avoid references to remote tables or views.
Cause: The capability in question is not supported when the materialized view references a synonym in the FROM list.
Action: Re-phrase the query to avoid the reference to the synonym.
Cause: The capability in question is not supported when the materialized view references an object in the SYS schema.
Action: Re-phrase the query to avoid the reference to 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.
Action: Re-phrase the query to avoid the use of aggregates in filter conditions 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.
Action: Re-phrase the query to avoid the use of filter conditions in the WHERE or HAVING clauses.
Cause: The capability in question is not supported when the materialized view uses these types of joins.
Action: Re-phrase the query to avoid the use of 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.
Action: Re-phrase the query to avoid the use of such expressions.
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.
Action: Either re-phrase the query to avoid the include a GROUP BY clause or an aggregate function, or set compatibility mode to 9.0 or higher.
Cause: The capability in question is not supported when the materialized view references a remote object and is refreshed ON COMMIT.
Action: Re-phrase the query to avoid the reference to the remote object or alter the materialized view to be refreshed ON DEMAND.
Cause: The capability in question is not supported when the materialized view references multiple remote objects that reside at different remote instances.
Action: Re-phrase the query to avoid the use of multiple master sites.
Cause: The capability in question is not supported when the materialized view uses grouping sets but omits the relevant GROUPING_ID or GROUPING functions.
Action: Re-phrase the query to include the relevant GROUPING_ID or GROUPING functions.
Cause: The capability in question is not supported when the materialized view redundantly references grouping sets.
Action: Re-phrase the query to avoid the use of the redundant grouping sets.
Cause: An internal Oracle error has occurred.
Action: Contact Oracle Support Services.
Cause: The capability in question is not supported when the compatibility mode is less than 9.0.
Action: Set the compatibility mode to 9.0 or higher.
Cause: The capability in question is not supported when the materialized view uses a set operator in this context.
Action: Re-phrase the query to avoid the use of the set operator.
Cause: The capability in question is not supported when the compatibility mode is less than 8.1.
Action: Set the compatibility mode to 8.1 or higher.
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.
Action: Re-create the materialized view as a primary key materialized view.
Cause: The capability in question is not supported when the materialized view references an object type in the WHERE clause.
Action: Re-phrase the query to avoid the reference to the object type.
Cause: The capability in question is not supported when the materialized view uses a subquery in a join in this way.
Action: Examine the relevant replication documentation concerning subquery materialized views and address the problem.
Cause: The capability in question is not supported when the materialized view references a remote site that does not support rowids.
Action: Re-phrase the query to avoid the reference to the remote site.
Cause: The capability in question is not supported when the materialized view uses certain constructs and references an older version, remote Oracle instance.
Action: Re-phrase the query to avoid the use of the construct or upgrade the 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.
Action: Examine the relevant primary key materialized view replication documentation and address the problem.
Cause: The capability in question is not supported when the materialized view uses a complex join or filter condition.
Action: Re-phrase the query to simplify the join or filter condition.
Cause: The capability in question is not supported when the materialized view references certain, complex expressions.
Action: Re-phrase the query to simplify the expression.
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.
Action: Add the SUM function to the select list.
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.
Action: Add the COUNT function to the select list.
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.
Action: Add the MIN function to the select list.
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.
Action: Add the MAX function to the select list.
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.
Action: Add the AVG function to the select list.
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.
Action: Add the VARIANCE function to the select list.
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.
Action: Add the STDDEV function to the select list.
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.
Action: Add an invocation of the same aggregate function on the square of the same argument (that is, the argument multiplied by itself).
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.
Action: Add the indicated aggregate function to the select list.
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).
Action: Add the SUM function on the square of the argument.
Cause: The EXPLAIN_MV analysis engine has failed to capture the reason why the given capability is not possible.
Action: Contact Oracle Support Services.
Cause: The materialized view query omits COUNT(*) from the select list.
Action: Add COUNT(*) to the select list.
Cause: SUM(expr) occurs in the select list without a corresponding COUNT(expr).
Action: Add COUNT(expr) to the select list.
Cause: One or more aggregate functions are present in the select list but a GROUP BY clause is not used.
Action: Add a GROUP BY clause.
Cause: A GROUP BY clause is used but no aggregate functions are present in the select list.
Action: Add an aggregate function to the select list.
Cause: REFRESH_FAST_AFTER_ONETAB_DML is disabled for the same reason that REFRESH_FAST_AFTER_INSERT is disabled.
Action: Correct the problem with REFRESH_FAST_AFTER_INSERT.
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.
Action: Specify a complete date format string.
Cause: You have specified a many to many join in your materialized view while running in less than 9.0 compatibility mode.
Action: Set your compatibility mode to 9.0 or higher or restructure the materialized view query.
Cause: You have specified a materialized view that uses some combination of the following in combination with the REFRESH ON COMMIT option while running in less than 9.0 compatibility mode:
Action: Set your compatibility mode to 9.0 or higher or restructure the materialized view query.
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.
Action: Restructure the materialized view query such that the respective sides of the UNION operator have identical select lists.
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.
Action: Set compatibility mode to 9.0 or higher or restructure the materialized view query.
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.
Action: Restructure the materialized view query.
Cause: You have specified a materialized view that references a view or a subquery in the top level FROM list but does not include aggregation. The indicated capability is not supported for this type of materialized view.
Action: Restructure the materialized view query.
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.
Action: Restructure the materialized view query to remove the offending view or the complex construct in the view.
Cause: REFRESH_FAST_AFTER_ANY_DML is disabled for the same reason that REFRESH_FAST_AFTER_ONETAB_DML is disabled.
Action: Correct the problem with REFRESH_FAST_AFTER_ONETAB_DML.
Cause: The fast refresh cannot be performed because the master table does not contain a materialized view log.
Action: Use the CREATE MATERIALIZED VIEW LOG statement to create a materialized view log on the master table.
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.
Action: A complete refresh is required before the next fast refresh. Add object id columns to the materialized view log, if required.
Cause: A materialized view using the UNION operator was specified and the tables on each side of the UNION operator do not match. Fast refresh is not supported in this context.
Action: Restructure the materialized view query such that the respective sides of the UNION operator have the same table.
Cause: Fast refresh is not supported if a materialized view having the UNION operator contains a join operation.
Action: Rewrite the materialized view query without the join.
Cause: If there are outer joins, unique constraints must exist on the join columns of the inner table. Otherwise, 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.
Action: Add a UNION ALL marker column to each query block in the UNION ALL query defining the materialized view.
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.
Action: Check each query block in the UNION ALL to ensure it is either a materialized view with joins or aggregates.
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.
Action: Remove any clauses besides SELECT and FROM from the materialized view's defining query.
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.
Action: Use SELECT * when defining a materialized view with a UNION ALL in a view.
Cause: The materialized view has a view whose definition involves a UNION ALL query that does not satisfy the requirements for fast refresh.
Action: Check that the defining query of the view being referenced in the materialized view satisfies conditions for fast refresh of a UNION ALL materialized view.
Cause: The setting of the COMPATIBLE initialization parameter is less than 9.2.0.
Action: Set COMPATIBLE to 9.2.0 or higher.
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.
Action: Add a primary key constraint to the base table, or create the materialized view as Rowid MV by specifying the WITH ROWID option. If the materialized view is a Rowid MV, then it should be able to do complete refresh and even fast refresh, given that the materialized view log on the master table has a rowid.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
