Absolutely *wonderful* . . .

I don't care how bad the database corruption gets - my maximum permitted down time is 16 hours, and I only get that on one day a week. If this process cannot be made restartable, my only recourse would be to start a new server with an empty database and start exporting data from the current one.

IBM, how about giving us a real database that we can use standard recovery tools against?

Tom Kauffman
Sr. Technical Analyst
NIBCO, Inc.

-----Original Message-----
From:   Riccardo Corona [SMTP:rcorona AT ESOC.ESA DOT DE]
Sent:   Monday, February 22, 1999 3:08 AM
To:     ADSM-L AT VM.MARIST DOT EDU
Subject:        Re: Audit db......it's completed

Great ! Only  six ( 6 !! ) days to audit the db with fix=yes.
Ok  it's not a very powerful server but according  to ibm statement  ( db
size type of machine and so on ) the  process was supposed to  run for two
or three days.
And also the log file is empty. Just luck I had a very long buffer window
and I could go back and see the whole story.
I agree with John's  method  using  > logfile instead of LOGFILE=.....
Thanks to everybody
Riccardo