ADSM-L

expiration runs, deletion not done

2003-02-24 12:42:52
Subject: expiration runs, deletion not done
From: Henk ten Have <hthta AT SARA DOT NL>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 24 Feb 2003 18:39:33 +0100
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      ANR9999D imutil.c(5570): ThreadId<100> 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)

<Prev in Thread] Current Thread [Next in Thread>