Villa, more on this and I need to be corrected. I gave you a wrong solution. The dropped table recovery on and not logged initially approach WILL NOT work. Here's why, at roll forward time, the table will be marked as "inaccessible" when the alter table activate NLI is executed. When the roll forward recover dropped table would subsequently be met in the logs, the export would attempt to run the select against a table that is NOT accessible and it fails. So... If you do NOT drop the table and you have NOT activated 'not logged initially' since the last backup up to the time of the last application, you should be able to restore the table space just prior to the unit of work that activated NLI and recover the table to that point. This would presume that the table lives alone in its tblsps., which would be recommended Another desperate measure would be to try to use db2dart to put the rows out to a file before the table is dropped. Sorry and hope you didn't do too much work on my recommendation.
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
