I think a "db2 archive log for database db_name.." could resolve your
problem
"aj" <ro****@mcdonalds.com> a écrit dans le message de
news:10*************@news.supernews.com...
DB2 v8 FP5
Red Hat AS/EL 2.1
For disaster recovery purposes (I'm in FL), I am utilizing a custom
DB2 userexit to FTP logical logs to an alternate site in prep for a
potential restore and roll forward.
I am a former Informix DBA, and in Informix I could issue an
"onmode -l" (thats an "el") command to force the database to the
next logical log.
Is there such a command in DB2? How do I force DB2 to complete
the current logical log and go on to the next one?
Any help appreciated.
aj
