Materialized View: A Question [message #336854] |
Tue, 29 July 2008 04:17  |
handii
Messages: 4 Registered: July 2008 Location: India
|
Junior Member |
|
|
Hi,
There is one Legacy database DB1 and other Oracle Applications Database DB2. I created a Read-Only Materialized View in Legacy Database DB1 which fetches the data from Oracle Apps Database DB2 Tables.
Now my question is,
When there will be a downtime for oracle Applications Database DB2 then will new Materialized View be accessible in Legacy Database DB1?
Regards and Thanks in Advance!!
P2
|
|
|
|
|
|
|
Re: Materialized View: A Question [message #337302 is a reply to message #337200] |
Wed, 30 July 2008 08:48   |
handii
Messages: 4 Registered: July 2008 Location: India
|
Junior Member |
|
|
Hi Michel,
Thanks for your response.
What do you mean by a 'JOB is not broken'?
We have following Refresh method for our Materialized view,
REFRESH COMPLETE
START WITH TO_DATE('29-JUL-2008 00:00:00','dd-mon-yyyy hh24:mi:ss')
NEXT SYSDATE + 1
So as per your reponse, Can I assume that after the system is restored, on next MIDNIGHT, our Materialized View will be refreshed?
Regards,
Pranit
[Updated on: Wed, 30 July 2008 08:48] Report message to a moderator
|
|
|
|
Re: Materialized View: A Question [message #337312 is a reply to message #337303] |
Wed, 30 July 2008 09:07   |
handii
Messages: 4 Registered: July 2008 Location: India
|
Junior Member |
|
|
Ok, then my question is,
will the BROKEN column in dba_jobs table be updated to 'N' when the interfacing instance (where Referenced tables exist) is down for refresh or some other reason.
Just to remind, in my question I asked that my materialized View is on a different instance than the instance where referenced tables are lying.
Hope I am clear or let me know.
Thanks!
Pranit
|
|
|
|
Re: Materialized View: A Question [message #337320 is a reply to message #337312] |
Wed, 30 July 2008 10:03  |
 |
Michel Cadot
Messages: 68737 Registered: March 2007 Location: Saint-Maur, France, https...
|
Senior Member Account Moderator |
|
|
BROKEN just indicates that either the job was set to broken, either it fails more X times (I currently don't remember X, I think it is 16).
It BROKEN is Y Oracle will no more try to execute the job until you explicitly set it to N or you manually successfully execute the job.
Regards
Michel
|
|
|