1 problem:
As mentioned above, a materialized view for timed refresh is created in my project. This materialized view is based on the query of a table with two remote machines connected to the left.
For the previous article "materialized views of Oracle [periodic refresh] [connection-based]", see
It looks like this:
Create materialized view VIEW_NAMErefresh clause asselect (...) from Table1 @ DBLINK_NAME t1 left join Table2 @ DBLINK_NAME t2on t1.id = t2.sid
At the beginning, Table 1 had only a few dozen pieces of data. This materialized view can be created and updated regularly.
Later, when the data size of Table1 increases to 0.34 million, the materialized view will not be updated, and finally re-execute the materialized view to find the [ORA-02063: preceding line from DBLINK_NAME] error.
2. Think about the solution process:
After an error was reported, I found that the focus was on the location t2, and that someone next to me was using the PL_ SQL software to connect to the remote database and open the table t2, then I think it may be because the database table deadlock causes this materialized view to be unable to be executed.
Then turn off PL_ SQL and find that this problem still exists... As a matter of fact, I think it is a bit naive. How can select statements compete with PL_ SQL software... Unless it is an update or insert statement, it is possible.
Then I continued to try and found:
(1) Remove the left link and use DBLINK alone to query t1 to create a materialized view, or use DBLINK alone to query t2 to create a materialized view;
(2) Keep the left join and only execute the select statement section in the create materialized view statement (that is, the table connecting two dblinks on the left). This error is returned;
It can be seen that this error has nothing to do with the materialized view, and it must be related to the left join ....
3. solution:
Later I checked the Internet and found someone said it may be because the password was not enclosed in double quotes when creating DBlink, it will lead to the ORA-02063 error... You must give it a try tomorrow.
(For more details, see continue to read the highlights on the next page :)
ORA-01172, ORA-01151 error handling
ORA-00600 [2662] troubleshooting
Troubleshooting for ORA-01078 and LRM-00109
Notes on ORA-00471 Processing Methods
ORA-00314, redolog corruption, or missing Handling Methods
Solution to ORA-00257 archive logs being too large to store