If you're at V7 look at the db2 flush log (I forget the actual spelling). This allows the active log used when the online backup finished to get its transaction externalized, closed and then ready for the exit to archive out. Or, if you are not using the exit, then you'll be able to run your own scripts or commands to archive the logs. HTH, Pierre. "Henry J. Cobb" wrote: > I've been thinking that if you're doing rotating online backups (to remain > continuously up, 24x7x365.25) your script should simply delete all archive > logs older than the last backup you care to keep and it might be nice to > backup (and remove) all logs older than than the active log when the > current backup was started, once it's completed successfully. > > Henry J. Cobb [EMAIL PROTECTED] http://www.io.com/~hcobb > Any sufficiently cool technology is indistinguishable from religion. > > ===== > To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] > For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
begin:vcard n:Saint-Jacques;Pierre tel;cell:514-233-8679 tel;fax:514-737-1268 tel;work:514-737-4515 x-mozilla-html:FALSE org:SES Consultants Inc. adr:;;233 Simcoe Cr.;Mount-Royal;QC;H3P 1X1;Canada version:2.1 email;internet:[EMAIL PROTECTED] title:President fn:Pierre Saint-Jacques end:vcard
