In today's project, you need to create a materialized view for multi-table join and refresh it once every two minutes.
Oracle ORA-02063 error Solution
As shown in:
The refresh method of my refresh statement is force. This method will first try to use the fast method (incremental refresh) for refresh, and will not use the complete method (full refresh) for refresh.
However, to refresh in fast mode, you need to create logs on the base table (so that the fast-Refresh mode can provide incremental basis ), my target table is on a remote machine (I have replaced the part of the DBlink table connected to the remote table with the local Test1 and Test2 tables) and is not our system, we do not want to create logs on the above, so the force here will actually be refreshed in complete mode...
In addition, the refresh clause uses the with primary key option to generate a primary key materialized view. That is, the materialized view is based on the primary key of the PRIMARY table rather than the ROWID (corresponding to the ROWID clause ).
The syntax for creating refresh statements for materialized views is as follows:
[Refresh [fast | complete | force]
[On demand | commit]
[Start with date] [next date]
[With {primary key | rowid}]
========================================================== ==============================
I wrote another materialized view based on the connection's fast refresh method, but there is an error:
It seems that the refresh method can only be based on single-table queries, rather than multi-table join queries.
Oracle materialized view creation reports ORA-00942 error resolution
Refresh the materialized view of Oracle stored procedures
Use of Oracle Materialized View
Materialized View for two-way synchronization of Oracle database tables
Oracle materialized view application notes