QSM-02025: no aggregate functions

QSM-02025: no aggregate functions

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.

QSM-02024: no GROUP BY clause

QSM-02024: no GROUP BY clause

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.

QSM-02023: nested cursor

QSM-02023: nested cursor

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.

QSM-02022: aggregate selections

QSM-02022: aggregate selections

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.

QSM-02021: set operator encountered in mv

QSM-02021: set operator encountered in mv

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

Action: Re-phrase the query to avoid the use of set operators.

QSM-02020: container column not in SELECT list with NOT NULL constraint

QSM-02020: container column not in SELECT list with NOT NULL constraint

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.

QSM-02019: mv references another mv in FROM clause

QSM-02019: mv references another mv in FROM 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).

Action: Re-phrase the query to avoid reference to the other materialized view.

QSM-02018: subquery present in the WHERE clause

QSM-02018: subquery present in the WHERE 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.

QSM-02017: subquery present in the HAVING clause

QSM-02017: subquery present in the HAVING clause

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.

QSM-02016: clustered table in FROM list

QSM-02016: clustered table in FROM list

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.

QSM-02015: Index Organized Table (IOT) present in FROM list

QSM-02015: Index Organized Table (IOT) present in FROM list

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.

QSM-02014: GROUP BY expression other than a column

QSM-02014: GROUP BY expression other than a column

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.

QSM-02013: SELECT list includes a RAW data type expression

QSM-02013: SELECT list includes a RAW data type expression

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.

QSM-02012: a CONNECT BY clause is present

QSM-02012: a CONNECT BY clause is present

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.

QSM-02011: a HAVING clause is present

QSM-02011: a HAVING clause is present

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

Action: Remove the HAVING clause.

QSM-02010: join predicate with operator other than equals (=)

QSM-02010: join predicate with operator other than equals (=)

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.

Action: Re-phrase the query to avoid the non-equijoin.

QSM-02009: non-inner join

QSM-02009: non-inner join

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

Action: Re-phrase the query using an inner join. Remove any outer joins.

QSM-02008: non-join filter condition in WHERE or HAVING clause

QSM-02008: non-join filter condition in WHERE or HAVING clause

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.

Action: Remove the selection filter expression.

QSM-02007: multiple instances of the same table or view

QSM-02007: multiple instances of the same table or view

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. For instance,

QSM-02006: subquery in FROM list

QSM-02006: subquery in 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.