All the tables referenced by the query are updatable.

The optimizer does not consider materialized views for a SELECT statement that is inherently updatable, or is explicitly declared in an updatable cursor. This situation can occur when using Interactive SQL, which utilizes updatable cursors by default for SELECT statements.

The statement is a simple DML statement that uses optimizer bypass and is optimized heuristically. However, you can force cost-based optimization of any SELECT statement using the FORCE OPTIMIZATION option of the OPTION clause.

For queries contained inside stored procedures and user-defined functions, the query's execution plan has been cached. The database server may cache the execution plans for these queries so that they can be reused. For this class of queries, the query execution plan is cached after execution. The next time the query is executed, the plan is retrieved and all the phases up to the execution phase are skipped.

contains only one query block

contains only one FROM clause

does not contain any of the following constructs or specifications:

• GROUPING SETS
• CUBE
• ROLLUP
• subquery
• derived table
• UNION
• EXCEPT
• INTERSECT
• materialized views
• DISTINCT
• TOP
• FIRST
• self-join
• recursive join
• FULL OUTER JOIN

(optionally) contains a GROUP BY clause, and a HAVING clause, provided the HAVING clause does not contain subselects or subqueries.

the materialized view must be enabled for use by the database server

the materialized view must be enabled for use in optimization

the materialized view must be initialized (populated with data)

values for some critical options used to create the materialized views must match the options for the connection executing the query

last refresh of the materialized view cannot have exceeded the staleness threshold set for the materialized_view_optimization database option