Use of DBMS_MVIEW.EXPLAIN_MVIEW package in Oracle Materialized View

DBMS_MVIEW.EXPLAIN_MVIEW can analyze three different materialized view codes:
1. defined query 2. a create materialized view Statement 3. An existing MATERIALIZED VIEW
The procedure is as follows: www.2cto.com
1. Run the table creation statement SQL> @ F: \ oracle \ product \ 10.2.0 \ db_1 \ RDBMS \ ADMIN \ utlxmv for the table mv_capabilities_table used by dbms_mview.explain_mview in advance. SQL statement. If this statement is not executed, the report does not exist when the package is run.
2. Clear the records in the TABLE to view the analysis information. truncate table mv_capabilities_table;
3. Run the dbms_mview.explain_mview package. The parameters in the package can be materialized views, query statements, and CREATE materialized view statements. Begin www.2cto.com dbms_mview.explain_mview ('select. id, B. name,. rowid a_rowid, B. rowid B _rowid FROM comp1 a, comp2 B WHERE. id = B. id'); end ;/
4. View analysis results or error reports select MSGTXT from mv_capabilities_table where capability_name = 'refresh _ FAST_AFTER_INSERT '; or select * from mv_capabilities_table; Tips :( 1) the materialized view does not support standard external join Writing of SQL92 when determining whether refresh is supported. You need to change it to the Oracle (+) method. (2) Quick refresh of materialized views that contain external links cannot efficiently use materialized view logs. Therefore, even quick refresh, the performance may be poor. From nisjlvhudy's column