It looks similar to a problem reported on IBM Website in 2007 : http://www-01.ibm.com/support/docview.wss?uid=swg1IC52527
According to this, it's not related to the volume itself but to the database. The "dsmserv auditdb" should be performed with the server OFFLINE. Good luck, Julien Malghem System Engineer / Storage Specialist [email protected] 2 Ter rue Marcel Doret 31700 Blagnac www.rbs.fr RBS Solutions Tél. : +33 (0)5 34 47 76 77 • Portable : +33 (0)6 60 26 61 52 • Fax : +33 (0)5 34 47 14 14 Un problème ? Contactez le Centre de Support RBS au 0892 70 12 12 (0,34€/mn) ou écrivez à [email protected] Intéressé(e) par nos solutions ? Contactez notre service commercial à [email protected] Intéressé(e) par notre programme de partenariat ? Contactez notre service alliance à [email protected] Ce message et ses éventuelles pièces jointes sont établies à l'intention exclusive de son ou de ses destinataires. Toute utilisation, diffusion ou publication non autorisée est prohibée. Ready Business System SA décline toute responsabilité au titre de ce message s'il a été altéré ou falsifié. Il ne contient aucun virus, mais il est de la responsabilité de son destinataire de s'en assurer. Merci de n'imprimer ce message ou ses pièces jointes que si cela s'avère nécessaire. -----Message d'origine----- De : ADSM: Dist Stor Manager [mailto:[email protected]] De la part de Zoltan Forray/AC/VCU Envoyé : vendredi 21 mai 2010 17:02 À : [email protected] Objet : Re: [ADSM-L] Deleting ghost/empty volume on V6.1 server Don't see any difference/additional messages: 5/21/2010 10:56:51 AM ANR2017I Administrator ZFORRAY issued command: SET CONTEXTMESSAGING on 5/21/2010 10:56:51 AM ANR4445I Context parameter set to ON. 5/21/2010 11:00:48 AM ANR2017I Administrator ZFORRAY issued command: DELETE VOLUME 086176 discard=y 5/21/2010 11:00:48 AM ANR9999D_3143370830 AfGetNextContents(afqry.c:899) Thread<47268>: Missing row for bitfile 0.213369199, readWrite(Yes). 5/21/2010 11:00:48 AM ANR9999D Thread<47268> issued message 9999 from: 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x0000000000c0f622 OutDiagToCons+0x0x142 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x0000000000c12104 outDiagfExt+0x0x194 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x000000000069f41c AfGetNextContents+0x0x31c 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x00000000005f35b5 bfGetNextContents+0x0x55 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x00000000004a419a AdmDeleteVolume+0x0x5ea 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x00000000004826c1 AdmCommandLocal+0x0x3c1 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x0000000000483528 admCommand+0x0x948 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x0000000000af2bea SmAdminCommandThread+0x0x1a 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x0000000000c807f4 StartThread+0x0x84 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x000000336b206367 *UNKNOWN* 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x000000336a6d30ad *UNKNOWN* 5/21/2010 11:00:48 AM ANR9999D_0036126006 AdmDeleteVolume(admdvol.c:1413) Thread<47268>: Error 87 returned from bfGetNextContents. 5/21/2010 11:00:48 AM ANR9999D Thread<47268> issued message 9999 from: 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x0000000000c0f622 OutDiagToCons+0x0x142 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x0000000000c12104 outDiagfExt+0x0x194 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x00000000004a422e AdmDeleteVolume+0x0x67e 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x00000000004826c1 AdmCommandLocal+0x0x3c1 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x0000000000483528 admCommand+0x0x948 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x0000000000af2bea SmAdminCommandThread+0x0x1a 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x0000000000c807f4 StartThread+0x0x84 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x000000336b206367 *UNKNOWN* 5/21/2010 11:00:48 AM ANR9999D Thread<47268> 0x000000336a6d30ad *UNKNOWN* 5/21/2010 11:00:48 AM ANR0405I Session 17007 ended for administrator ZFORRAY (WinNT). From: Rick Adamson <[email protected]> To: [email protected] Date: 05/21/2010 10:39 AM Subject: Re: [ADSM-L] Deleting ghost/empty volume on V6.1 server Sent by: "ADSM: Dist Stor Manager" <[email protected]> Have you tried to enable "context messaging" to see if you can get more info on the ANR9999D messages "set contextmessaging on" Thank you, ~Rick -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Zoltan Forray/AC/VCU Sent: Friday, May 21, 2010 10:20 AM To: [email protected] Subject: Re: [ADSM-L] Deleting ghost/empty volume on V6.1 server Yep......Similar error/problem. Never starts/fails immediately 5/21/2010 10:18:57 AM ANR2017I Administrator ZFORRAY issued command: AUDIT VOLUME 086176 fix=yes 5/21/2010 10:18:57 AM ANR1199I Removable volume 086176 is required for audit process. 5/21/2010 10:18:57 AM ANR9999D_3143370830 AfGetNextContents(afqry.c:899) Thread<47192>: Missing row for bitfile 0.213369199, readWrite(Yes). 5/21/2010 10:18:57 AM ANR9999D Thread<47192> issued message 9999 from: 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x0000000000c0f622 OutDiagToCons+0x0x142 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x0000000000c12104 outDiagfExt+0x0x194 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x000000000069f41c AfGetNextContents+0x0x31c 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x00000000005f35b5 bfGetNextContents+0x0x55 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x00000000004a1eb9 DoAuditVolume+0x0x839 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x00000000004a360c AdmAuditVolume+0x0xf1c 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x00000000004826c1 AdmCommandLocal+0x0x3c1 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x0000000000483528 admCommand+0x0x948 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x0000000000af2bea SmAdminCommandThread+0x0x1a 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x0000000000c807f4 StartThread+0x0x84 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x000000336b206367 *UNKNOWN* 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x000000336a6d30ad *UNKNOWN* 5/21/2010 10:18:57 AM ANR9999D_0036126006 DoAuditVolume(admdvol.c:5449) Thread<47192>: Error 87 returned from bfGetNextContents. 5/21/2010 10:18:57 AM ANR9999D Thread<47192> issued message 9999 from: 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x0000000000c0f622 OutDiagToCons+0x0x142 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x0000000000c12104 outDiagfExt+0x0x194 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x00000000004a242d DoAuditVolume+0x0xdad 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x00000000004a360c AdmAuditVolume+0x0xf1c 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x00000000004826c1 AdmCommandLocal+0x0x3c1 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x0000000000483528 admCommand+0x0x948 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x0000000000af2bea SmAdminCommandThread+0x0x1a 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x0000000000c807f4 StartThread+0x0x84 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x000000336b206367 *UNKNOWN* 5/21/2010 10:18:57 AM ANR9999D Thread<47192> 0x000000336a6d30ad *UNKNOWN* 5/21/2010 10:18:57 AM ANR2667W Audit volume process has skipped volume 086176 due to an error. From: Rick Adamson <[email protected]> To: [email protected] Date: 05/21/2010 09:36 AM Subject: Re: [ADSM-L] Deleting ghost/empty volume on V6.1 server Sent by: "ADSM: Dist Stor Manager" <[email protected]> Did you try to perform an audit on the volume(s) using the "fix" option? ~Rick Adamson -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Zoltan Forray/AC/VCU Sent: Friday, May 21, 2010 9:33 AM To: [email protected] Subject: [ADSM-L] Deleting ghost/empty volume on V6.1 server Does anyone have a suggestion on deleting a screwed-up volume on a 6.1.3.4 server? I have tried all the usual methods, with no success. Any attempt to get any info from this volume generates this error: 5/21/2010 7:56:07 AM ANR9999D_3143370830 AfGetNextContents(afqry.c:899) Thread: Missing row for bitfile 0.213369199, readWrite(No). 5/21/2010 7:56:07 AM ANR9999D Thread issued message 9999 from: 5/21/2010 7:56:07 AM ANR9999D Thread 0x0000000000c0f622 OutDiagToCons+0x0x142 5/21/2010 7:56:07 AM ANR9999D Thread 0x0000000000c12104 outDiagfExt+0x0x194 5/21/2010 7:56:07 AM ANR9999D Thread 0x000000000069f41c AfGetNextContents+0x0x31c 5/21/2010 7:56:07 AM ANR9999D Thread 0x000000000069dc7c AfMoveData+0x0x1cc 5/21/2010 7:56:07 AM ANR9999D Thread 0x000000000061d40e bfMoveData+0x0x45e 5/21/2010 7:56:07 AM ANR9999D Thread 0x000000000055b458 AdmMoveData+0x0x538 5/21/2010 7:56:07 AM ANR9999D Thread 0x00000000004826c1 AdmCommandLocal+0x0x3c1 5/21/2010 7:56:07 AM ANR9999D Thread 0x0000000000483528 admCommand+0x0x948 5/21/2010 7:56:07 AM ANR9999D Thread 0x0000000000af2bea SmAdminCommandThread+0x0x1a 5/21/2010 7:56:07 AM ANR9999D Thread 0x0000000000c807f4 StartThread+0x0x84 5/21/2010 7:56:07 AM ANR9999D Thread 0x000000336b206367 *UNKNOWN* 5/21/2010 7:56:07 AM ANR9999D Thread 0x000000336a6d30ad *UNKNOWN* 5/21/2010 7:56:07 AM ANR2209W Volume 086176 contains no data. When I try to DELETE VOLUME ... DISCARDDATA=YES, I get: 5/21/2010 9:30:51 AM ANR9999D_0036126006 AdmDeleteVolume(admdvol.c:1413) Thread<47110>: Error 87 returned from bfGetNextContents. 5/21/2010 9:30:51 AM ANR9999D Thread<47110> issued message 9999 from: 5/21/2010 9:30:51 AM ANR9999D Thread<47110> 0x0000000000c0f622 OutDiagToCons+0x0x142 5/21/2010 9:30:51 AM ANR9999D Thread<47110> 0x0000000000c12104 outDiagfExt+0x0x194 5/21/2010 9:30:51 AM ANR9999D Thread<47110> 0x00000000004a422e AdmDeleteVolume+0x0x67e 5/21/2010 9:30:51 AM ANR9999D Thread<47110> 0x00000000004826c1 AdmCommandLocal+0x0x3c1 5/21/2010 9:30:51 AM ANR9999D Thread<47110> 0x0000000000483528 admCommand+0x0x948 5/21/2010 9:30:51 AM ANR9999D Thread<47110> 0x0000000000af2bea SmAdminCommandThread+0x0x1a 5/21/2010 9:30:51 AM ANR9999D Thread<47110> 0x0000000000c807f4 StartThread+0x0x84 5/21/2010 9:30:51 AM ANR9999D Thread<47110> 0x000000336b206367 *UNKNOWN* 5/21/2010 9:30:51 AM ANR9999D Thread<47110> 0x000000336a6d30ad *UNKNOWN* Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services [email protected] - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
