Materialised view log
Gopikrishnan Samyappan, September 14, 2018 - 9:59 am UTC
Thanks for this help!
Can you please explain me when the materialized log must be used ?
If suppose i have two schemas schemaA and schemaB. Creating materialized view using REFRESH FAST on SchemaB based on master table in schemaA required materialized log in SchemaA?
Regards,
Gopikrishnan
September 16, 2018 - 2:59 am UTC
The need for a materialized log, and what it contains, depends mainly on the SQL and refresh type that will be used to refresh the materialized view.
But we document all the usage models, and restrictions here:
https://docs.oracle.com/cd/E11882_01/server.112/e25554/basicmv.htm#i1007299 Also, search this site for DBMS_MVIEW.EXPLAIN_MVIEW for examples on how to test your mviews for refresh compatibility.
MV
Gopi Krishnan Samyappan, September 23, 2018 - 5:30 pm UTC
Can you explain why we opt using index in creating materialized view? example please if any
September 26, 2018 - 12:41 am UTC
Can you explain why we opt using index in creating materialized view?
You need to clarify what you're asking here
Helpful
Rameshwar Rdevkule, April 07, 2022 - 8:49 am UTC
actually we stuck with same problem but now problem solve
we use same method which you used.
Thanks once again...
Our problem below--->
SQL> create materialized view viwww_mat_ref_with refresh force on commit as select* from worker1 where salary=500000;
create materialized view viwww_mat_ref_with refresh force on commit as select* from worker1 where salary=500000
*
ERROR at line 1:
ORA-12054: cannot set the ON COMMIT refresh attribute for the materialized view
SOLUTION---->
SQL> create materialized view vi_mat_reff refresh force on commit as select* from worker1 where salary=500000;
Materialized view created.
April 07, 2022 - 9:41 am UTC
Thanks for sharing