On 6 Dec, 13:11, "jshen...._at_gmail.com" <jshen...._at_gmail.com> wrote:
> On 12月6日, 上午3时04分, Frank van Bortel <frank.van.bor..._at_gmail.com>
> wrote:
>
>
>
>
>
> > jshen...._at_gmail.com wrote:
> > >>> There had been refresh failures before. At those failure time, I
> > >>> cound determine refresh failure by " select job, failures, last_sec,
> > >>> next_sec from user_jobs".
> > >> Hmmm - does not sound like a stable system. Ever found
> > >> out what causes these errors?
>
> > > No. Usually it just fails, we do not keep the alert.log . To my
> > > experience, there has been 4 times of refresh failure this year.
>
> > And why do you think errors on jobs will end up
> > in the alert log file?
> > They should be logged by the pl/sql block that is executed
> > when the MV refreshes.
>
> > Manually executing the procedure, that is called by the
> > job will reveal the error.
>
> > > In fact, there is NO error on refresh failure in alert.log . Before
> > > failure happened,
> > > there has been several Archive failure log in alert.log, but there
> > > exist successful archive after failure log.
>
> I did execute those job manually, but it succeeded without updating
> snapshot
>
>
>
> > > Those Error looks like :
>
> > > Sun Dec 2 03:10:27 2007
> > > ARC0: Beginning to archive log# 13 seq# 361643
> > > ARC0: Failed to archive log# 13 seq# 361643
> > > ARC0: Beginning to archive log# 15 seq# 361644
> > > ARC0: Failed to archive log# 15 seq# 361644
>
> > Dangerous - should be an entry in a trace file, explaining
> > why the archiver failed - disk full?
>
> but, there is no record in trace file or other place.- Hide quoted text -
>
> - Show quoted text -
When last did you reboot the server? Some servers need re-booted
after 400 odd days.
Shabble
Received on Thu Dec 06 2007 - 07:17:39 CST
