At 08:31 07/24/03, you wrote:

> >At 02:25 07/24/03, you wrote:
> >>Scott,
> >>
> >> >> First time gbak encounters such an error it will stop operation and
> > > >> the rest of the backup file is unrestored.
> >
> >Well, I'm not a developer, but other RDBMSs I have worked with, just spew
> >out an error log for such tripe, and continue on their merry way with the
> >next record in line.
>
>It is possible to get yourself into various states with Oracle as
>well where you can no longer import a batch you've exported. Oracle
>has an option to Import Ignore Errors which allows you to then go in
>and work with the data for recovery.
>
>Throwing a warning and moving on would be an acceptable option (at
>least for me).

Yeah, maybe a switch in gbak to choose to allow to continue on data
errors. Sometimes any recovery is better than none, especially after a
disaster. I always have multiple copies, multiple locations, daily, of the
live database. Therefore, if I could at least get a partial recovery of
the most current data, then I might be able to piece together the rest.