QSM-02056: correlated variable and outer join in mv

QSM-02056: correlated variable and outer join in mv

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 the correlated variables or outer joins.

QSM-02055: mv references a packed object table or view

QSM-02055: mv references a packed object table or view

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 the packed object tables or views.

QSM-02054: DISTINCT clause in select list in mv

QSM-02054: DISTINCT clause in select list in mv

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.

QSM-02053: collection subquery in mv

QSM-02053: collection subquery in mv

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.

QSM-02052: subquery using a select list in mv

QSM-02052: subquery using a select list in mv

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.

QSM-02051: subquery using the NOT EXISTS clause in mv

QSM-02051: subquery using the NOT EXISTS clause in mv

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

Action: Re-phrase the query to avoid the use of the NOT EXITS clause.

QSM-02050: subquery using the ALL clause in mv

QSM-02050: subquery using the ALL clause in mv

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.

QSM-02049: subquery using the ANY clause in mv

QSM-02049: subquery using the ANY clause in mv

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.

QSM-02048: outer join in mv

QSM-02048: outer join in mv

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.

QSM-02047: window function in mv

QSM-02047: window function in mv

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.

QSM-02045: START WITH clause in mv

QSM-02045: START WITH clause in mv

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.

QSM-02044: ORDER BY clause in mv

QSM-02044: ORDER BY clause in mv

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

Action: Remove the ORDER BY clause.

QSM-02042: view or subquery in from list

QSM-02042: view or subquery in from list

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 in the FROM list.

QSM-02041: nested aggregate function

QSM-02041: nested aggregate function

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.

QSM-02040: top level query contains GSets and the key is too long for rewrite

QSM-02040: top level query contains GSets and the key is too long for rewrite

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.

QSM-02039: top level mv query uses grouping sets

QSM-02039: top level mv query uses grouping sets

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

Action: Re-phrase the query to avoid use of grouping sets.

QSM-02038: Partition Change Tracking (PCT) is enabled

QSM-02038: Partition Change Tracking (PCT) is enabled

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

Action: No action is needed.

QSM-02037: cannot evaluate constant expression at compile time

QSM-02037: cannot evaluate constant expression at compile time

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 a compile-time non-constant expressions in filter conditions.

QSM-02036: in-list present in mv

QSM-02036: in-list present in mv

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.

QSM-02035: no filter conditions are present in the HAVING clause

QSM-02035: no filter conditions are present in the HAVING clause

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.

QSM-02034: no joins are present in the HAVING clause

QSM-02034: no joins are present in the HAVING clause

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.

QSM-02033: no filter conditions are present in the WHERE clause

QSM-02033: no filter conditions are present 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.

Action: Add a filter condition.

QSM-02032: no joins are present in the WHERE clause

QSM-02032: no joins are present in the WHERE clause

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.

QSM-02031: materialized view cannot support any type of query rewrite

QSM-02031: materialized view cannot support any type of query rewrite

Cause: of the problem.

Action: Examine the other messages and documentation to determine the

QSM-02030: reduced precision specified for prebuilt mv

QSM-02030: reduced precision specified for prebuilt mv

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.

QSM-02029: PL or SQL function invocation

QSM-02029: PL or SQL function invocation

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

Action: Re-phrase the query to avoid use of PL or SQL functions.

QSM-02028: group by CUBE

QSM-02028: group by CUBE

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.

QSM-02027: group by ROLLUP

QSM-02027: group by ROLLUP

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.

QSM-01619: equivalence cannot be used in ENFORCED integrity mode

QSM-01619: equivalence cannot be used in ENFORCED integrity mode

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

Action: none

QSM-01618: equivalence, string, is enabled for text match rewrite only

QSM-01618: equivalence, string, is enabled for text match rewrite only

Cause: This equivalence was created for text match rewrite only

Action: none

QSM-01617: equivalence definition is disabled

QSM-01617: equivalence definition is disabled

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

Action: none

QSM-01610: a lossy join in equivalence, string, between tables, string, not found in query

QSM-01610: a lossy join in equivalence, string, between tables, string, not found in query

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

Action: none

QSM-01602: equivalence, string, requires join back to table, string, on column, string

QSM-01602: equivalence, string, requires join back to table, string, on column, string

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.

Action: none

QSM-01601: rollup(s) took place on equivalence, string

QSM-01601: rollup(s) took place on equivalence, string

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.

Action: none

QSM-01584: equivalence, string, has anchor, string, not found in query

QSM-01584: equivalence, string, has anchor, string, not found in query

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

Action: none

QSM-01582: Joining equivalence, string, with table, string, not possible

QSM-01582: Joining equivalence, string, with table, string, not possible

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

Action: none

QSM-01572: equivalence, string, and query have different joins between tables, string

QSM-01572: equivalence, string, and query have different joins between tables, string

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

Action: none

QSM-01567: equivalence, string, cannot support the query measure, string

QSM-01567: equivalence, string, cannot support the query measure, string

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: none

QSM-01565: equivalence, string, cannot compute measure, string, in the query

QSM-01565: equivalence, string, cannot compute measure, string, in the query

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

Action: none

QSM-01533: query rewritten with equivalence, string

QSM-01533: query rewritten with equivalence, string

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

Action: none

QSM-01526: query rewrite is disabled for equivalence, string

QSM-01526: query rewrite is disabled for equivalence, string

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

Action: Enable this equivalence using alter_rewrite_equivalence procedure from package, dbms_advanced_rewrite.

QSM-01522: a more optimal equivlanece than string was used to rewrite

QSM-01522: a more optimal equivlanece than string was used to rewrite

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.

Action: none

QSM-01509: equivalence, string, matched query text

QSM-01509: equivalence, string, matched query text

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

Action: none

QSM-01336: the materialized view you specified (string) was not used to rewrite the query

QSM-01336: the materialized view you specified (string) was not used to rewrite the query

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.

Action: none

QSM-01335: query rewrite not possible because query has an LOB column

QSM-01335: query rewrite not possible because query has an LOB column

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

Action: none

QSM-01334: query rewrite not possible because query has a hidden or nested table column

QSM-01334: query rewrite not possible because query has a hidden or nested table column

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

Action: none

QSM-01333: query rewrite not possible because query has an ADT column

QSM-01333: query rewrite not possible because query has an ADT column

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

Action: none

QSM-01332: query rewrite not possible because query has a named array type column

QSM-01332: query rewrite not possible because query has a named array type column

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

Action: none

QSM-01321: query rewrite not possible because materialized view string has TRUSTED constraints in ENFORCED integrity mode

QSM-01321: query rewrite not possible because materialized view string has TRUSTED constraints in ENFORCED integrity mode

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

Action: Alter materialized view such that it has the ENFORCED CONSTRAINTS ALTER MATERIALIZED VIEW lamp;lt;lamp;nbsp;mvlamp;gt; REFRESH USING ENFORCED CONSTRAINTS

QSM-01316: window function could not be computed from materialized view string

QSM-01316: window function could not be computed from materialized view string

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

Action: none

QSM-01308: number of OR s in query exceeded the maximum value string

QSM-01308: number of OR s in query exceeded the maximum value string

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).

Action: none

QSM-01307: Partition Containment Tracking (PCT) rewrite is not allowed

QSM-01307: Partition Containment Tracking (PCT) rewrite is not allowed

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

Action: none

QSM-01304: query rewrite not possible because query is using flashback

QSM-01304: query rewrite not possible because query is using flashback

Cause: Query rewrite does not support flashback.

Action: none

QSM-01303: query rewrite not possible because query references a remote table string

QSM-01303: query rewrite not possible because query references a remote table string

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

Action: none

QSM-01299: query rewrite not possible because materialized view string is partially stale

QSM-01299: query rewrite not possible because materialized view string is partially stale

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: (1) Change the selection criteria of the request to restrict the query to only the fresh portion of the materialized view, or (2) ALTER {SYSTEM|SESSION} QUERY_REWRITE_INTEGRITY = STALE_TOLERATED or (3) refresh the materialized view.

QSM-01091: cost based optimizer found query rewrite is more expensive

QSM-01091: cost based optimizer found query rewrite is more expensive

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: none

QSM-01090: no query rewrite after view merging

QSM-01090: no query rewrite after view merging

Cause: Internal session parameter _QUERY_REWRITE_1 is set to FALSE

Action: Change session parameter with ALTER SESSION command.

QSM-01089: an inline view in the query does not have a materialized view

QSM-01089: an inline view in the query does not have a materialized view

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.

Action: none

QSM-01087: query grouping on a column that cannot be derived from materialized view, string

QSM-01087: query grouping on a column that cannot be derived from materialized view, string

Cause: Query is grouping on undetermined columns.

Action: none

QSM-01086: dimension(s) not present or not used in ENFORCED integrity mode

QSM-01086: dimension(s) not present or not used in ENFORCED integrity mode

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: none