We're running server version 5.3.3.0. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Wahlstedt Sent: Tuesday, April 03, 2007 6:05 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Error deleting filespace
Hi, Which version of TSM are you running? There are some fixes for filespace deletion. However, if you cant find any usefull information on TSM web when you are search for 'IM not able to delete object', imutil.c, Bitfile id not found and imfsdel.c etc I recommend you to open a case with support. //Henrik -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of LeBlanc, Patricia Sent: den 2 april 2007 20:40 To: ADSM-L@VM.MARIST.EDU Subject: Error deleting filespace Has anyone ever encountered errors deleting filespaces? I have one that will not delete.... Here is the error: 04/02/2007 13:39:48 ANR0802I DELETE FILESPACE /database (fsId=8) (backup/archive data) for node DEL20070205-SLEEPER started.(SESSION: 340550, PROCESS: 10014) 04/02/2007 13:39:49 ANR9999D imutil.c(6884): ThreadId<112> Bitfile id 0.6104501 not found.(SESSION: 340550, PROCESS: 10014) 04/02/2007 13:39:49 ANR9999D ThreadId<112> issued message 9999 from: <-0x000000010001c240 outDiagf <-0x000000010017cb3c ImDeleteBitfile <-0x0000000100185670 imDeleteObject <-0x00000001003a6fc0 DeleteBackups <-0x00000001003a7fb4 imFSDeletionThread <-0x000000010000e9dc StartThread <-0x0900000000403448 _pthread_body (SESSION: 340550, PROCESS: 10014) 04/02/2007 13:39:49 ANR9999D imfsdel.c(1827): ThreadId<112> IM not able to delete object 0.6104501, rc: 19(SESSION: 340550, PROCESS:10014) 04/02/2007 13:39:49 ANR9999D ThreadId<112> issued message 9999 from: <-0x000000010001c240 outDiagf <-0x00000001003a7144 DeleteBackups <-0x00000001003a7fb4 imFSDeletionThread <-0x000000010000e9dc StartThread <-0x0900000000403448_pthread_body (SESSION: 340550, PROCESS: 10014) 04/02/2007 13:39:49 ANR0987I Process 10014 for DELETE FILESPACE running in the BACKGROUND processed 2 items with a completion state of FAILURE at 13:39:49.(SESSION: 340550, PROCESS: 10014) If it's related to database integrity.....how do I fix that? I can't audit my db. Thanks, pattie ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.