Hi,
and you should add an
db2 archive log for database <dbname>
before exiting from your batch. DB2 restore discards of all the logs in the log path before attempting to retrieve the last log from the userexit, which means you may lose the log rollforward is depending on unless it has been archived in the first place.
Something like this might have happened to you.
Johann
Quote:
Originally posted by cchattoraj
The backup statement given is for an offline backup (ie does not contain the online keyword). Then it does make sense that you do a rollforward ... stop.
In db2 you do not have to force off applications for an online backup and the backup statement in this case would be
db2 backup db dia online to '/data/arraya/bck'
While an online backup is in progress, users can query and update the database, but cannot do things which require exclusive locks (like autoloads)
|