| Post fast/complete refresh COMPILE_STATE=NEEDS_COMPILE [message #209857] |
Mon, 18 December 2006 03:29 |
blazingrock4u
Messages: 30
Registered: March 2006
Location: India
|
Member |
|
|
To reduce load on my master tables I've created a materialized view on my base tables (mv is also on the same db).
The materilaizd view which is of type REFRESH FORCE ON DEMAND. I've got MV logs in place. As per my need I want to refresh this Mat. view. And currently I am doing it thru a hourly job using: dbms_mview.refresh('mat_vw','F'). And sometimes if required I may go for a complete refresh: dbms_mview.refresh('mat_vw','C').
After every fast/complete refresh of my materialized view ALL_MVIEW's column COMPILE_STATE=NEEDS_COMPILE.
Is this normal?
Yes, I understand:
"NEEDS_COMPILE - Some object upon which the materialized view depends has changed (other than normal DML changes). An ALTER MATERIALIZED VIEW...COMPILE statement is required to validate this materialized view."
Even though I am not compiling the mat.view manually, I still am able to do SELECT on the mat.view without any errors. If I leave the Mat.view with COMPILE_STATE=NEEDS_COMPILE or STATUS=NEEDS_COMPILE, will it harm my code anyway or will it cause an issue in long-run?
Do I have to really worry about COMPILE_STATE=NEEDS_COMPILE?
If yes, then, how should i overcome this situation. (I am not allowed to add triggers on my db because of performance issue).
What role does it play and how will it effect me if i ignore it. Same is the case with STATUS=NEEDS_COMPILE???
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
