Thought of that. When a backup exceeds the durration or starts to late
to fit in the window it blows out an error.
Thus spake Peter DrakeUnderkoffler (veritas AT ratgut DOT com):
> "Robert L. Harris" wrote:
> >
> > Very odd one.
> >
> > I have an RMAN schedule (Oracle database hot backup). It runs
> > flawless with exceptions when the DBA's are screwing with something. It
> > ran great over the weekend. This morning it didn't run. It was
> > scheduled to run. There were no errors. From what we can tell it
> > litereally looks like it wasn't scheduled to run, no errors in the job
> > monitor, no entry in the job monitor, no errors or logs on the Oracle
> > side either.
> >
> > Has anyone seen anything like this?
> >
> > Robert
> >
> > :wq!
> > ---------------------------------------------------------------------------
> > Robert L. Harris | Micros~1 :
> > Senior System Engineer | For when quality, reliability
> > at RnD Consulting | and security just aren't
> > \_ that important!
> > DISCLAIMER:
> > These are MY OPINIONS ALONE. I speak for no-one else.
> > FYI:
> > perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
> >
> > _______________________________________________
> > Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
> Could be the duration time for that schedule and class. If you
> have a bpsched log directory setup, you should see something in there.
>
> Thanks
> Peter
:wq!
---------------------------------------------------------------------------
Robert L. Harris | Micros~1 :
Senior System Engineer | For when quality, reliability
at RnD Consulting | and security just aren't
\_ that important!
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
FYI:
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
|