Josh
there is a reference on Richard's web page of an audit db with a flag that
does the disk stuff. I had two tapes that I couldn't delete and after
running this audit (without taking things down and I only have a 10 gig db)
it solved my problem. I am running 3.1.2.40 and the audit only took about
five minutes. Hope that helps.
-----Original Message-----
From: Joshua S. Bassi [mailto:[EMAIL PROTECTED]]
Sent: Saturday, December 16, 2000 8:40 AM
To: [EMAIL PROTECTED]
Subject: Re: Can't Del Disk Vol
There is not a copy of this disk storage pool volume so that is out.
The discardd=y option doesn't work either.
>If these do not work then you should call the support center and see
>if they have a method of cleaning the entries out of the data base.
My customer has done this as well. The PMR is still open and has been
for 3 months. The only suggesting support has is to audit the DB.
This is a 40GB DB and my customer cannot schedule the downtime.
--
Joshua S. Bassi
IBM Certified- AIX Support, HACMP, SAN
Enterprise Disk(Shark)& Tape Solutions
Tivoli Certified Consultant - ADSM/TSM
[EMAIL PROTECTED]
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Len Boyle
Sent: Friday, December 15, 2000 2:59 PM
To: [EMAIL PROTECTED]
Subject: Re: Can't Del Disk Vol
In article <[EMAIL PROTECTED]>, "Joshua S. Bassi"
<[EMAIL PROTECTED]> says:
>
>All,
>
>I have a customer with a disk storage pool volume that
>won't delete. It is a raw logical volume and somehow
>it was removed from the system, so it needs to be
>purged out of the ADSM database.
>
>del vol /dev/radsmpool19
>and
>del vol /dev/radsmpool19
>
>Produce a message that indicates "ANR9999d dfqry.c(595):
>Missing row for bitfile 0.27709337" and "ANR2406E volume
>still contains data"
Hello Joshua
I believe that you have two methods that will work, depending about
the past history of the data recorded as existing on the volumes.
If you want to keep the missing file data and you have a copy of the
data on a copypool volume then you can use the "restore volume"
command to restore the data from the copypool to a volume that is
not destroyed. This process will delete the tsm data base refrences
to the data on the destroyed volumes.
Or if you do not want to save the data, issue the "delete volume"
command with the "discarddata=yes" option.
If these do not work then you should call the support center and see
if they have a method of cleaning the entries out of the data base.
/len
-------------------------------------------------------------------------
Leonard Boyle [EMAIL PROTECTED]
SAS Institute Inc. ussas4hs@ibmmail
Room RB448 [EMAIL PROTECTED]
1 SAS Campus Drive (919) 531-6241
Cary NC 27513
