ADSM-L

Re: ANR9999D IMUTIL(4923) - delete filespace

2003-03-27 09:44:12
Subject: Re: ANR9999D IMUTIL(4923) - delete filespace
From: "Stumpf, Joachim" <joachim.stumpf AT DATEV DOT DE>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 27 Mar 2003 14:43:35 -0000
Hello,

with the help from support I was able to delete the filespace.
But first:

"auditdb inventory fix=yes" on TSM-Server 5.1.6.2 finished
with RC=1 after 65000 lines of output --> and the the error
was still there.

After upgrading the TSM-Server to 5.1.6.3 I was able to run the
auditdb with RC=0.
Audit deleted some invalid entries (254 entries) and after this
I was able to delete the filespace.

Information from PQ71960 which is still open:
Support gave me the information that during the upgradedb from
4.x to 5.1.x FSID and NODEID were be converted with zero.

-- 
regards / Mit freundlichen Gruessen
Joachim Stumpf
Datev eG
Nuremberg - Germany

------------- Original-Nachricht folgt ------------- 

Henk ten Have,

the result of "show bfo 0 243145" is
"Bitfile Object: 0.243145 Bitfile Object NOT found."

I called support (created pmr at IBM-Webpage) and wait now for their call ;-)
And I think I'm lucky - my TEST-DB is only 500MB...

thanks for your help - I will post here again when I have a solution (or 
other important informations)

--
regards
Joachim Stumpf

------------- Original-Nachricht folgt -------------

Joachim,

> I tried to delete a filespace on my TSM-Test-server (V5.1.6.2 on z/OS 1.4)
> and got the following messages.
> Has anyone seen this before? What can I do? Is my DB corrupted?

At least you'r lucky it's your test-server...

> ANR9999D IMFSDEL(1864): ThreadId<517> Error deleting group leader 0 243145.
> ANR0985I Process 11 for DELETE FILESPACE running in the BACKGROUND completed
> with completion state FAILURE at 13:12:52.

Try a "show bfo 0 243145". If you'r lucky, this command shows something like:

Storage Pool ID: xx Volume ID: yy Volume Name: 'volume_name'.
If yes, you can try a "audit vol 'volume_name' fix=3Dyes".

If not, try a "auditdb". (How big is your database?).

And if yes or no, always call your local Support immediatly, these errors
are damn serious.

Cheers,
Henk ten Have (running a "auditdb fix=3Dyes" on a testserver for +3 days now,
database=3D70Gbyte, Processed 318836522 database entries sofar)


-- 
regards / Mit freundlichen Gruessen
Joachim Stumpf
Datev eG
Nuremberg - Germany
      

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