expiration runs, deletion not done
AIX 4.3.3, TSM 4.2.3.3. Since a couple of days expirations runs, but deletion stops after an error: 02/21/03 14:44:10 ANRD imutil.c(5570): ThreadId100 Bitfile id 0.496165168 not found. 02/21/03 14:44:11 (100) Generating Database Transaction Table Context: 02/21/03 14:44:11 (100) *** no transactions found *** 02/21/03 14:44:11 (100) Generating SM Context Report: 02/21/03 14:44:11 (100) *** no sessions found *** 02/21/03 14:44:11 (100) Generating AS Vol Context Report: 02/21/03 14:44:11 (100) No mounted (or mount in progress) volumes. 02/21/03 14:44:11 (100) Generating ssSession Context Report: 02/21/03 14:44:11 (100) No storage service sessions active. 02/21/03 14:44:11 (100) Generating ssOpenSeg Context Report: 02/21/03 14:44:11 (100) No storage service segments found. 02/21/03 14:44:11 (100) Generating BF Copy Control Context Report: 02/21/03 14:44:11 (100) No global copy control blocks. and a couple of 100 other (silly) messages. 'Normally', if expirations ends before it is finished, the next expiration startes where the last expirations did stop. So, smart as we are (ahum), we stop expiration after the error and restart. But in this case this trick doesn't work. Every expiration starts all over again, hardly deleting anything, hit this error again, continues with examination and stops at the end of his list. Number of examined object is now nearly 4 million, my guess is that at least 3 million should be deleted. Not to mention that we will ran out of tapes pretty soon Cheers, Henk ten Have (completely clueless and not amused)
Re: expiration runs, deletion not done
Since a couple of days expirations runs, but deletion stops after an error: 02/21/03 14:44:10 ANRD imutil.c(5570): ThreadId100 Bitfile id 0.496165168 not found. Henk - Possibly: You could do a Select search on your Backups or Archives tables for that OBJECT_ID, to identify the filespace object involved, and perhaps via Contents determine what tape volume it is on, then do an Audit Volume Fix=Yes ? 'Normally', if expirations ends before it is finished, the next expiration startes where the last expirations did stop. So, smart as we are (ahum), we stop expiration after the error and restart. But in this case this trick doesn't work. I'm curious: Did you do a CANcel EXPIration or CANcel PRocess ? Richard Sims, BU
Re: expiration runs, deletion not done
Henk - Possibly: You could do a Select search on your Backups or Archives tables for that OBJECT_ID, to identify the filespace object involved, and perhaps via Contents determine what tape volume it is on, then do an Audit Volume Fix=Yes ? Richard, I know which filespace is involved (i.e. the last ANR4391 before the error starts). I try (tomorrow) to find the tape volume. At least it's a good try to give an audit volume a chance. I'm curious: Did you do a CANcel EXPIration or CANcel PRocess ? Actually I did a CANcel PRocess. I tried now a CANcel EXPIration. Guess what? Expiration don't start ALL over, but keeps starting a couple of dozen filespaces BEFORE the one which gives the error. I'll be damned Anyway, you give me some things to try, thanks. I'll let you know about my experience the next days. Cheers, Henk (next days? Don't think so, tomorrow...before we ran out of tape volumes)
