|
We just had a major issue with a materialized view (aka snapshot) job running for over two months without end.
This actually caused a loss of revenue for our company, as this job generated data which reported customer service usage.
I can remember an old 8.1.5 but where an network outage would cause these jobs to hang, but this was supposedly fixed.
The only solution I can see is to generate a script which validates that a job in dba_jobs_running is not there over a certain Period of time. The issue with this is that that “period of time” may be ill-defined. The refresh interval stored in dba_mviews is a relative date/time calculation, and does not lend it self to comparative testing.
I can provide more detail on this dilemma if anyone needs them.
Any ideas?
Michael Fontana Sr. DBA NTT/Verio |
<<image001.gif>>
The previous attachment was filtered out by the ListGuru mailing software at fatcity.com because binary attachments are not appropriate for mailing lists. If you want a copy of the attachment which was removed, contact the sender directly and ask for it to be sent to you by private E-mail.
This warning is inserted into all messages containing binary attachments which have been removed by ListGuru. If you have questions about this message, contact [EMAIL PROTECTED] for clarification.
<<image002.gif>>
