SQL & PL/SQL

Our customer is encountering a UI exception when accessing a specific page in
our application. We have determined the source of the problem, but do not
understand why it is occurring. A self-contained, generic replication
scenario has been created for your needs.

1. Run the four create table statements
2. The select statement can be executed successfully
3. Run the create materialized view statement.
4. Running the select statement now results in an ORA -1417 error.
5. If the MV is dropped, the select statement is run successfully.

The MV's select statement was written such that it shouldn't be used when executing the 'SELECT t0.*' statement.

I understand what normally causes a 1417 error, but this statement does not
fall into that category. The question we have is why would a MV, with a
select statement that does not even exist in the application, cause a 1417
error on a select statement that does not violate the outer join principles.

The select query is as follows:


SELECT t0.*
@ FROM table1 t0,
@ table2 t1,
@ table2 t3,
@ table3 t2,
@ table4 t4
@ WHERE t0.e = t1.J(+)
@ AND t1.J = t2.C(+)
@ AND t1.J = t4.E(+)
@ AND t2.C = t3.J(+)
@ .
@ CREATE MATERIALIZED VIEW mv1
@ ENABLE QUERY REWRITE
@ AS SELECT description FROM table2