Re: 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 ANRD imutil.c(6884): ThreadId112 Bitfile id 0.6104501 not found.(SESSION: 340550, PROCESS: 10014) 04/02/2007 13:39:49 ANRD ThreadId112 issued message from: -0x00010001c240 outDiagf -0x00010017cb3c ImDeleteBitfile -0x000100185670 imDeleteObject -0x0001003a6fc0 DeleteBackups -0x0001003a7fb4 imFSDeletionThread -0x0001e9dc StartThread -0x09403448 _pthread_body (SESSION: 340550, PROCESS: 10014) 04/02/2007 13:39:49 ANRD imfsdel.c(1827): ThreadId112 IM not able to delete object 0.6104501, rc: 19(SESSION: 340550, PROCESS:10014) 04/02/2007 13:39:49 ANRD ThreadId112 issued message from: -0x00010001c240 outDiagf -0x0001003a7144 DeleteBackups -0x0001003a7fb4 imFSDeletionThread -0x0001e9dc StartThread -0x09403448_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.
Re: Error deleting filespace
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 ANRD imutil.c(6884): ThreadId112 Bitfile id 0.6104501 not found.(SESSION: 340550, PROCESS: 10014) 04/02/2007 13:39:49 ANRD ThreadId112 issued message from: -0x00010001c240 outDiagf -0x00010017cb3c ImDeleteBitfile -0x000100185670 imDeleteObject -0x0001003a6fc0 DeleteBackups -0x0001003a7fb4 imFSDeletionThread -0x0001e9dc StartThread -0x09403448 _pthread_body (SESSION: 340550, PROCESS: 10014) 04/02/2007 13:39:49 ANRD imfsdel.c(1827): ThreadId112 IM not able to delete object 0.6104501, rc: 19(SESSION: 340550, PROCESS:10014) 04/02/2007 13:39:49 ANRD ThreadId112 issued message from: -0x00010001c240 outDiagf -0x0001003a7144 DeleteBackups -0x0001003a7fb4 imFSDeletionThread -0x0001e9dc StartThread -0x09403448_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.
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 ANRD imutil.c(6884): ThreadId112 Bitfile id 0.6104501 not found.(SESSION: 340550, PROCESS: 10014) 04/02/2007 13:39:49 ANRD ThreadId112 issued message from: -0x00010001c240 outDiagf -0x00010017cb3c ImDeleteBitfile -0x000100185670 imDeleteObject -0x0001003a6fc0 DeleteBackups -0x0001003a7fb4 imFSDeletionThread -0x0001e9dc StartThread -0x09403448 _pthread_body (SESSION: 340550, PROCESS: 10014) 04/02/2007 13:39:49 ANRD imfsdel.c(1827): ThreadId112 IM not able to delete object 0.6104501, rc: 19(SESSION: 340550, PROCESS:10014) 04/02/2007 13:39:49 ANRD ThreadId112 issued message from: -0x00010001c240 outDiagf -0x0001003a7144 DeleteBackups -0x0001003a7fb4 imFSDeletionThread -0x0001e9dc StartThread -0x09403448_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
Re: Problem deleting filespace on TSM 5.2.x
Hi Etienne! That's right, but in your case, I would be interested in why the delete fails and thus upgrade my TSM server first. Maybe you can solve the failure yourself afterwards, but in any case, you need this maintenance level to be able to provide IBM enough info in case of a PMR... Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Etienne Brodeur [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 12, 2005 19:36 To: ADSM-L@VM.MARIST.EDU Subject: Re: Problem deleting filespace on TSM 5.2.x Hi Eric, Indeed it does... but it says the fix is that instead of ending in sucess, the delete filespace will end in error with the appropriate error message: ... The intent of this APAR is to change the completion message to a failure and produce a diagnostic message indicating why the filespace could not be removed. The fix doesn't remove the filespace, it just tells you why it couldn't. You still need to manually remove the invalid entry in the DB ! Etienne Loon, E.J. van - SPLXM [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/12/2005 05:38 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Problem deleting filespace on TSM 5.2.x Hi Etienne! The apar states: * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be * * fixed in levels 5.1.10 and 5.2.4. Note * * that this is subject to change at the* * discretion of IBM. * Both levels are available for download for quite some time and both contain the fix for this bug... Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Etienne Brodeur [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 11, 2005 20:12 To: mailto:ADSM-L@VM.MARIST.EDU ADSM-L@VM.MARIST.EDU Subject: Problem deleting filespace on TSM 5.2.x Hello All, I have a probleme with deleting a Windows filespace for a particular node I want to remove. When I run DELETE FILESPACE on it it finishes without errors, but the filespace itself is not deleted. 20-09-2005 08:45:04 ANR0984I Process 106 for DELETE FILESPACE started in the FOREGROUND at 08:45:04. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0800I DELETE FILESPACE flush (fsId=2) for node MAIL started as process 106. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0802I DELETE FILESPACE flush (fsId=2) (backup/archive data) for node MAIL started. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0806I DELETE FILESPACE flush (fsId=2) complete for node MAIL: 0 objects deleted. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0985I Process 106 for DELETE FILESPACE running in the FOREGROUND completed with completion state SUCCESS at 08:45:04. (SESSION: 2938, PROCESS: 106) I have found this APAR on the TSM site which mentions that the local fix is to manually delete the invalid entry in the TSM DB... How does one go about doing that ? IC39957: DELETE FILESPACE RETURNS SUCCESS BUT FILESPACE STILL EXISTS. APAR status Closed as program error. Error description A customer may be unable to remove a filespace from the ITSM Server with the delete filespace command. The delete filespace will complete successfully but the filespace will still exist. The following messages are an example of the successful return. . ANR0806I DELETE FILESPACE * (fsId=XX) complete for node TESTFS: X objects deleted. ANR0985I Process X for DELETE FILESPACE running in the BACKGROUND completed with completion state SUCCESS at XX:XX:XX. . A subsequent 'Q fi filespace name' will reveal that the filespace was not removed. . The delete filespace should not end with a completion state of success if the filespace cannot be removed because of a referential integrity issue. The intent of this APAR is to change the completion message to a failure and produce a diagnostic message indicating why the filespace could not be removed. . Platforms affected: All ITSM Servers running 4.2, 5.1 or 5.2 . Customer/L2 Diagnostics The problem can be verified by enabling the IMFS trace class. The following trace point will show which table entry is still tied to the filespace: . imfsdel.c [2727]: nodeId=XXX, fsId=X is referenced in table name . Initial Impact: Low . Additional Keywords: IMFS FSID REM NODE ANRD REMOVE REF INVALID DELETE FILESPACE DIAG Local fix Invalid ITSM DB entry will have to be manually removed to delete the filespace. Problem summary * USERS AFFECTED: All users of IBM Tivoli Storage Manager
Re: Problem deleting filespace on TSM 5.2.x
Hi Etienne! The apar states: * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be * * fixed in levels 5.1.10 and 5.2.4. Note * * that this is subject to change at the* * discretion of IBM. * Both levels are available for download for quite some time and both contain the fix for this bug... Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Etienne Brodeur [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 11, 2005 20:12 To: mailto:ADSM-L@VM.MARIST.EDU ADSM-L@VM.MARIST.EDU Subject: Problem deleting filespace on TSM 5.2.x Hello All, I have a probleme with deleting a Windows filespace for a particular node I want to remove. When I run DELETE FILESPACE on it it finishes without errors, but the filespace itself is not deleted. 20-09-2005 08:45:04 ANR0984I Process 106 for DELETE FILESPACE started in the FOREGROUND at 08:45:04. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0800I DELETE FILESPACE flush (fsId=2) for node MAIL started as process 106. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0802I DELETE FILESPACE flush (fsId=2) (backup/archive data) for node MAIL started. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0806I DELETE FILESPACE flush (fsId=2) complete for node MAIL: 0 objects deleted. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0985I Process 106 for DELETE FILESPACE running in the FOREGROUND completed with completion state SUCCESS at 08:45:04. (SESSION: 2938, PROCESS: 106) I have found this APAR on the TSM site which mentions that the local fix is to manually delete the invalid entry in the TSM DB... How does one go about doing that ? IC39957: DELETE FILESPACE RETURNS SUCCESS BUT FILESPACE STILL EXISTS. APAR status Closed as program error. Error description A customer may be unable to remove a filespace from the ITSM Server with the delete filespace command. The delete filespace will complete successfully but the filespace will still exist. The following messages are an example of the successful return. . ANR0806I DELETE FILESPACE * (fsId=XX) complete for node TESTFS: X objects deleted. ANR0985I Process X for DELETE FILESPACE running in the BACKGROUND completed with completion state SUCCESS at XX:XX:XX. . A subsequent 'Q fi filespace name' will reveal that the filespace was not removed. . The delete filespace should not end with a completion state of success if the filespace cannot be removed because of a referential integrity issue. The intent of this APAR is to change the completion message to a failure and produce a diagnostic message indicating why the filespace could not be removed. . Platforms affected: All ITSM Servers running 4.2, 5.1 or 5.2 . Customer/L2 Diagnostics The problem can be verified by enabling the IMFS trace class. The following trace point will show which table entry is still tied to the filespace: . imfsdel.c [2727]: nodeId=XXX, fsId=X is referenced in table name . Initial Impact: Low . Additional Keywords: IMFS FSID REM NODE ANRD REMOVE REF INVALID DELETE FILESPACE DIAG Local fix Invalid ITSM DB entry will have to be manually removed to delete the filespace. Problem summary * USERS AFFECTED: All users of IBM Tivoli Storage Manager * * Server on ANY platform. * * PROBLEM DESCRIPTION: See Error Description. * * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be * * fixed in levels 5.1.10 and 5.2.4. Note * * that this is subject to change at the* * discretion of IBM. * Incorrect result message was issued for DELETE FILESPACE operation. Also, no message was issued indicating that the filespace being deleted is still referenced by an inventory database entry. Problem conclusion IBM Tivoli Storage Manager Server is modified to issue a failure result message if the filespace being deleted is referenced by any inventory database entry. In addition, a diagnostic message will be issued to indicate the reason for the failure. Temporary fix Comments APAR information APAR number
Re: Problem deleting filespace on TSM 5.2.x
Hi Eric, Indeed it does... but it says the fix is that instead of ending in sucess, the delete filespace will end in error with the appropriate error message: ... The intent of this APAR is to change the completion message to a failure and produce a diagnostic message indicating why the filespace could not be removed. The fix doesn't remove the filespace, it just tells you why it couldn't. You still need to manually remove the invalid entry in the DB ! Etienne Loon, E.J. van - SPLXM [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/12/2005 05:38 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Problem deleting filespace on TSM 5.2.x Hi Etienne! The apar states: * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be * * fixed in levels 5.1.10 and 5.2.4. Note * * that this is subject to change at the* * discretion of IBM. * Both levels are available for download for quite some time and both contain the fix for this bug... Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Etienne Brodeur [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 11, 2005 20:12 To: mailto:ADSM-L@VM.MARIST.EDU ADSM-L@VM.MARIST.EDU Subject: Problem deleting filespace on TSM 5.2.x Hello All, I have a probleme with deleting a Windows filespace for a particular node I want to remove. When I run DELETE FILESPACE on it it finishes without errors, but the filespace itself is not deleted. 20-09-2005 08:45:04 ANR0984I Process 106 for DELETE FILESPACE started in the FOREGROUND at 08:45:04. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0800I DELETE FILESPACE flush (fsId=2) for node MAIL started as process 106. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0802I DELETE FILESPACE flush (fsId=2) (backup/archive data) for node MAIL started. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0806I DELETE FILESPACE flush (fsId=2) complete for node MAIL: 0 objects deleted. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0985I Process 106 for DELETE FILESPACE running in the FOREGROUND completed with completion state SUCCESS at 08:45:04. (SESSION: 2938, PROCESS: 106) I have found this APAR on the TSM site which mentions that the local fix is to manually delete the invalid entry in the TSM DB... How does one go about doing that ? IC39957: DELETE FILESPACE RETURNS SUCCESS BUT FILESPACE STILL EXISTS. APAR status Closed as program error. Error description A customer may be unable to remove a filespace from the ITSM Server with the delete filespace command. The delete filespace will complete successfully but the filespace will still exist. The following messages are an example of the successful return. . ANR0806I DELETE FILESPACE * (fsId=XX) complete for node TESTFS: X objects deleted. ANR0985I Process X for DELETE FILESPACE running in the BACKGROUND completed with completion state SUCCESS at XX:XX:XX. . A subsequent 'Q fi filespace name' will reveal that the filespace was not removed. . The delete filespace should not end with a completion state of success if the filespace cannot be removed because of a referential integrity issue. The intent of this APAR is to change the completion message to a failure and produce a diagnostic message indicating why the filespace could not be removed. . Platforms affected: All ITSM Servers running 4.2, 5.1 or 5.2 . Customer/L2 Diagnostics The problem can be verified by enabling the IMFS trace class. The following trace point will show which table entry is still tied to the filespace: . imfsdel.c [2727]: nodeId=XXX, fsId=X is referenced in table name . Initial Impact: Low . Additional Keywords: IMFS FSID REM NODE ANRD REMOVE REF INVALID DELETE FILESPACE DIAG Local fix Invalid ITSM DB entry will have to be manually removed to delete the filespace. Problem summary * USERS AFFECTED: All users of IBM Tivoli Storage Manager * * Server on ANY platform. * * PROBLEM DESCRIPTION: See Error Description. * * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be * * fixed in levels 5.1.10 and 5.2.4. Note * * that this is subject to change
Problem deleting filespace on TSM 5.2.x
Hello All, I have a probleme with deleting a Windows filespace for a particular node I want to remove. When I run DELETE FILESPACE on it it finishes without errors, but the filespace itself is not deleted. 20-09-2005 08:45:04 ANR0984I Process 106 for DELETE FILESPACE started in the FOREGROUND at 08:45:04. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0800I DELETE FILESPACE flush (fsId=2) for node MAIL started as process 106. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0802I DELETE FILESPACE flush (fsId=2) (backup/archive data) for node MAIL started. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0806I DELETE FILESPACE flush (fsId=2) complete for node MAIL: 0 objects deleted. (SESSION: 2938, PROCESS: 106) 20-09-2005 08:45:04 ANR0985I Process 106 for DELETE FILESPACE running in the FOREGROUND completed with completion state SUCCESS at 08:45:04. (SESSION: 2938, PROCESS: 106) I have found this APAR on the TSM site which mentions that the local fix is to manually delete the invalid entry in the TSM DB... How does one go about doing that ? IC39957: DELETE FILESPACE RETURNS SUCCESS BUT FILESPACE STILL EXISTS. APAR status Closed as program error. Error description A customer may be unable to remove a filespace from the ITSM Server with the delete filespace command. The delete filespace will complete successfully but the filespace will still exist. The following messages are an example of the successful return. . ANR0806I DELETE FILESPACE * (fsId=XX) complete for node TESTFS: X objects deleted. ANR0985I Process X for DELETE FILESPACE running in the BACKGROUND completed with completion state SUCCESS at XX:XX:XX. . A subsequent 'Q fi filespace name' will reveal that the filespace was not removed. . The delete filespace should not end with a completion state of success if the filespace cannot be removed because of a referential integrity issue. The intent of this APAR is to change the completion message to a failure and produce a diagnostic message indicating why the filespace could not be removed. . Platforms affected: All ITSM Servers running 4.2, 5.1 or 5.2 . Customer/L2 Diagnostics The problem can be verified by enabling the IMFS trace class. The following trace point will show which table entry is still tied to the filespace: . imfsdel.c [2727]: nodeId=XXX, fsId=X is referenced in table name . Initial Impact: Low . Additional Keywords: IMFS FSID REM NODE ANRD REMOVE REF INVALID DELETE FILESPACE DIAG Local fix Invalid ITSM DB entry will have to be manually removed to delete the filespace. Problem summary * USERS AFFECTED: All users of IBM Tivoli Storage Manager * * Server on ANY platform. * * PROBLEM DESCRIPTION: See Error Description. * * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be * * fixed in levels 5.1.10 and 5.2.4. Note * * that this is subject to change at the* * discretion of IBM. * Incorrect result message was issued for DELETE FILESPACE operation. Also, no message was issued indicating that the filespace being deleted is still referenced by an inventory database entry. Problem conclusion IBM Tivoli Storage Manager Server is modified to issue a failure result message if the filespace being deleted is referenced by any inventory database entry. In addition, a diagnostic message will be issued to indicate the reason for the failure. Temporary fix Comments APAR information APAR number IC39957 Reported component name TSM SERVER 510 Reported component ID 5698ISMSV Reported release 52A Status CLOSED PER PE NoPE HIPER NoHIPER Submitted date 2004-03-19 Closed date 2004-04-30 Last modified date 2004-04-30 APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PQ87176 Thanks for your help, Etienne Brodeur Coordonnateur Technique - Technical Coordinator Serti Informatique Inc. Tel.: (514) 493-1909 Fax: (514) 493-3575 http://www.serti.com
Re: Problem deleting filespace on TSM 5.2.x
On Oct 11, 2005, at 2:12 PM, Etienne Brodeur wrote: I have found this APAR on the TSM site which mentions that the local fix is to manually delete the invalid entry in the TSM DB... How does one go about doing that ? Contact TSM Support. Manually correcting database problems requires a board-certified surgeon. Richard Sims
Deleting filespace
Hi Everybody, I would like to clean up my filespaces for a AIX certain node on my TSM server. Is there any way I can pass the filesystem to the dsmc delete filespace command ? I have quite a few filespaces on this server ( over 50 ) which I would like to delete. I can only get the numbered listing when I do dsmc delete filespace on the node itself. This will take a while to go through and I would like to script this. Rich
Re: Deleting filespace
You cannot script the client version of the delete filespace operation; try using the Administrative client version of this command, or ask your TSM server administrator for help (if you are not the administrator). Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2005-07-19 08:14:00: Hi Everybody, I would like to clean up my filespaces for a AIX certain node on my TSM server. Is there any way I can pass the filesystem to the dsmc delete filespace command ? I have quite a few filespaces on this server ( over 50 ) which I would like to delete. I can only get the numbered listing when I do dsmc delete filespace on the node itself. This will take a while to go through and I would like to script this. Rich
Re: Deleting filespace
Hi, Thanks Andrew. I knew you could do it from the Admin server, but I thought maybe there was a way of doing it from the client just in case I had overlooked something. I have admin access to the server, and I can script it there. Rich -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Andrew Raibeck Sent: Tuesday, July 19, 2005 11:37 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Deleting filespace You cannot script the client version of the delete filespace operation; try using the Administrative client version of this command, or ask your TSM server administrator for help (if you are not the administrator). Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2005-07-19 08:14:00: Hi Everybody, I would like to clean up my filespaces for a AIX certain node on my TSM server. Is there any way I can pass the filesystem to the dsmc delete filespace command ? I have quite a few filespaces on this server ( over 50 ) which I would like to delete. I can only get the numbered listing when I do dsmc delete filespace on the node itself. This will take a while to go through and I would like to script this. Rich
When Deleting Filespace
Howdy TSM folks, Something got me wondering when deleting filespace for a node. After you enter the command for deleting filespace(s) and when you do q pro it will display the number of objects deleted. My question is how do you calculate how many objects will be deleted? This # does't match up with the # of files in q occup. Are you aware of any sql statement that will allow you to calculate this value. I want be home before dinner, but don't know when it will end. Thanks, Sung Y. Lee
Re: Error in deleting filespace
Hi Zosi! Please supply the complete server level (like 5.1.7.0). Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Zosimo Noriega [mailto:[EMAIL PROTECTED] Sent: Saturday, July 26, 2003 08:49 To: [EMAIL PROTECTED] Subject: Re: Error in deleting filespace Hi, The TSM server 5.1 on AIX 5 and TSM client 5.1.5 on Windows 2000. Thanks, Zosi Noriega -Original Message- From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 12:12 PM To: [EMAIL PROTECTED] Subject: Re: Error in deleting filespace Hi Zosi! When posting a question to this list, please supply your TSM software level, maybe then we are able to assist you. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Zosimo Noriega [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 06:42 To: [EMAIL PROTECTED] Subject: Error in deleting filespace Hi all, I got the error in deleting filespace, please see the log from activity log. I hope everybody can help me. thanks. Zosi Noriega 07/23/03 08:33:59 ANR2017I Administrator ZBN3669 issued command: DELETE FILESPACE SAPPLIBP1 3 NAMETYPE=FSID TYPE=ANY DATA=ANY WAIT=NO 07/23/03 08:33:59 ANR0984I Process 2546 for DELETE FILESPACE started in the BACKGROUND at 08:33:59. 07/23/03 08:33:59 ANR0802I DELETE FILESPACE Registries (fsId=3) (backup/arc- hive data) for node SAPPLIBP1 started. 07/23/03 08:33:59 ANR0800I DELETE FILESPACE Registries (fsId=3) for node SAPPLIBP1 started as process 2546. 07/23/03 08:33:59 ANR0609I DELETE FILESPACE started as process 2546. 07/23/03 08:33:59 ANR0104E imutil.c(7529): Error 2 deleting row from table Expiring.Objects. 07/23/03 08:33:59 ANRD imfsdel.c(1863): ThreadId79 Error 19 deleting group leader 0 48984968. 07/23/03 08:33:59 ANR0985I Process 2546 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 08:33:59. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. ** ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Error in deleting filespace
Hi Zosi! This looks like APAR PQ71660 which is fixed in 5.1.7.0. So my advice is: upgrade. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 12:28 To: [EMAIL PROTECTED] Subject: RE: Error in deleting filespace Hi Eric, Here is TSM server 5.1.5.0. Thanks, Zosi -Original Message- From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 1:45 PM To: [EMAIL PROTECTED] Subject: Re: Error in deleting filespace Hi Zosi! Please supply the complete server level (like 5.1.7.0). Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Zosimo Noriega [mailto:[EMAIL PROTECTED] Sent: Saturday, July 26, 2003 08:49 To: [EMAIL PROTECTED] Subject: Re: Error in deleting filespace Hi, The TSM server 5.1 on AIX 5 and TSM client 5.1.5 on Windows 2000. Thanks, Zosi Noriega -Original Message- From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 12:12 PM To: [EMAIL PROTECTED] Subject: Re: Error in deleting filespace Hi Zosi! When posting a question to this list, please supply your TSM software level, maybe then we are able to assist you. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Zosimo Noriega [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 06:42 To: [EMAIL PROTECTED] Subject: Error in deleting filespace Hi all, I got the error in deleting filespace, please see the log from activity log. I hope everybody can help me. thanks. Zosi Noriega 07/23/03 08:33:59 ANR2017I Administrator ZBN3669 issued command: DELETE FILESPACE SAPPLIBP1 3 NAMETYPE=FSID TYPE=ANY DATA=ANY WAIT=NO 07/23/03 08:33:59 ANR0984I Process 2546 for DELETE FILESPACE started in the BACKGROUND at 08:33:59. 07/23/03 08:33:59 ANR0802I DELETE FILESPACE Registries (fsId=3) (backup/arc- hive data) for node SAPPLIBP1 started. 07/23/03 08:33:59 ANR0800I DELETE FILESPACE Registries (fsId=3) for node SAPPLIBP1 started as process 2546. 07/23/03 08:33:59 ANR0609I DELETE FILESPACE started as process 2546. 07/23/03 08:33:59 ANR0104E imutil.c(7529): Error 2 deleting row from table Expiring.Objects. 07/23/03 08:33:59 ANRD imfsdel.c(1863): ThreadId79 Error 19 deleting group leader 0 48984968. 07/23/03 08:33:59 ANR0985I Process 2546 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 08:33:59. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. ** ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. ** ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed
Re: Error in deleting filespace
Hi, The TSM server 5.1 on AIX 5 and TSM client 5.1.5 on Windows 2000. Thanks, Zosi Noriega -Original Message- From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 12:12 PM To: [EMAIL PROTECTED] Subject: Re: Error in deleting filespace Hi Zosi! When posting a question to this list, please supply your TSM software level, maybe then we are able to assist you. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Zosimo Noriega [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 06:42 To: [EMAIL PROTECTED] Subject: Error in deleting filespace Hi all, I got the error in deleting filespace, please see the log from activity log. I hope everybody can help me. thanks. Zosi Noriega 07/23/03 08:33:59 ANR2017I Administrator ZBN3669 issued command: DELETE FILESPACE SAPPLIBP1 3 NAMETYPE=FSID TYPE=ANY DATA=ANY WAIT=NO 07/23/03 08:33:59 ANR0984I Process 2546 for DELETE FILESPACE started in the BACKGROUND at 08:33:59. 07/23/03 08:33:59 ANR0802I DELETE FILESPACE Registries (fsId=3) (backup/arc- hive data) for node SAPPLIBP1 started. 07/23/03 08:33:59 ANR0800I DELETE FILESPACE Registries (fsId=3) for node SAPPLIBP1 started as process 2546. 07/23/03 08:33:59 ANR0609I DELETE FILESPACE started as process 2546. 07/23/03 08:33:59 ANR0104E imutil.c(7529): Error 2 deleting row from table Expiring.Objects. 07/23/03 08:33:59 ANRD imfsdel.c(1863): ThreadId79 Error 19 deleting group leader 0 48984968. 07/23/03 08:33:59 ANR0985I Process 2546 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 08:33:59. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. ** This e-mail may contain confidential and/or priviledged information. If you are not the intended recepient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail.
Re: Error in deleting filespace
Hi Zosi! When posting a question to this list, please supply your TSM software level, maybe then we are able to assist you. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Zosimo Noriega [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 06:42 To: [EMAIL PROTECTED] Subject: Error in deleting filespace Hi all, I got the error in deleting filespace, please see the log from activity log. I hope everybody can help me. thanks. Zosi Noriega 07/23/03 08:33:59 ANR2017I Administrator ZBN3669 issued command: DELETE FILESPACE SAPPLIBP1 3 NAMETYPE=FSID TYPE=ANY DATA=ANY WAIT=NO 07/23/03 08:33:59 ANR0984I Process 2546 for DELETE FILESPACE started in the BACKGROUND at 08:33:59. 07/23/03 08:33:59 ANR0802I DELETE FILESPACE Registries (fsId=3) (backup/arc- hive data) for node SAPPLIBP1 started. 07/23/03 08:33:59 ANR0800I DELETE FILESPACE Registries (fsId=3) for node SAPPLIBP1 started as process 2546. 07/23/03 08:33:59 ANR0609I DELETE FILESPACE started as process 2546. 07/23/03 08:33:59 ANR0104E imutil.c(7529): Error 2 deleting row from table Expiring.Objects. 07/23/03 08:33:59 ANRD imfsdel.c(1863): ThreadId79 Error 19 deleting group leader 0 48984968. 07/23/03 08:33:59 ANR0985I Process 2546 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 08:33:59. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Error in deleting filespace
Hi Zosi, Two quick questions which might help here: O - what level is your TSM server at the moment? O - have you upgraded your TSM server from an earlier version recently? Rgds, David McClelland Global Management Systems Reuters Ltd -Original Message- From: Zosimo Noriega [mailto:[EMAIL PROTECTED] Sent: 23 July 2003 05:42 To: [EMAIL PROTECTED] Subject: Error in deleting filespace Hi all, I got the error in deleting filespace, please see the log from activity log. I hope everybody can help me. thanks. Zosi Noriega 07/23/03 08:33:59 ANR2017I Administrator ZBN3669 issued command: DELETE FILESPACE SAPPLIBP1 3 NAMETYPE=FSID TYPE=ANY DATA=ANY WAIT=NO 07/23/03 08:33:59 ANR0984I Process 2546 for DELETE FILESPACE started in the BACKGROUND at 08:33:59. 07/23/03 08:33:59 ANR0802I DELETE FILESPACE Registries (fsId=3) (backup/arc- hive data) for node SAPPLIBP1 started. 07/23/03 08:33:59 ANR0800I DELETE FILESPACE Registries (fsId=3) for node SAPPLIBP1 started as process 2546. 07/23/03 08:33:59 ANR0609I DELETE FILESPACE started as process 2546. 07/23/03 08:33:59 ANR0104E imutil.c(7529): Error 2 deleting row from table Expiring.Objects. 07/23/03 08:33:59 ANRD imfsdel.c(1863): ThreadId79 Error 19 deleting group leader 0 48984968. 07/23/03 08:33:59 ANR0985I Process 2546 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 08:33:59. --- - Visit our Internet site at http://www.reuters.com Get closer to the financial markets with Reuters Messaging - for more information and to register, visit http://www.reuters.com/messaging Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.
Error in deleting filespace
Hi all, I got the error in deleting filespace, please see the log from activity log. I hope everybody can help me. thanks. Zosi Noriega 07/23/03 08:33:59 ANR2017I Administrator ZBN3669 issued command: DELETE FILESPACE SAPPLIBP1 3 NAMETYPE=FSID TYPE=ANY DATA=ANY WAIT=NO 07/23/03 08:33:59 ANR0984I Process 2546 for DELETE FILESPACE started in the BACKGROUND at 08:33:59. 07/23/03 08:33:59 ANR0802I DELETE FILESPACE Registries (fsId=3) (backup/arc- hive data) for node SAPPLIBP1 started. 07/23/03 08:33:59 ANR0800I DELETE FILESPACE Registries (fsId=3) for node SAPPLIBP1 started as process 2546. 07/23/03 08:33:59 ANR0609I DELETE FILESPACE started as process 2546. 07/23/03 08:33:59 ANR0104E imutil.c(7529): Error 2 deleting row from table Expiring.Objects. 07/23/03 08:33:59 ANRD imfsdel.c(1863): ThreadId79 Error 19 deleting group leader 0 48984968. 07/23/03 08:33:59 ANR0985I Process 2546 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 08:33:59. This e-mail may contain confidential and/or priviledged information. If you are not the intended recepient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail.
deleting filespace
Hi Everyone, Any help from you is really appreciated. I'm deleting filespace but I got this error and the filespace still exist. == 06/09/03 08:42:10 ANR2017I Administrator ZBN3669 issued command: DELETE FILESPACE SAPPLIBP1 3 NAMETYPE=FSID TYPE=ANY DATA=ANY WAIT=NO 06/09/03 08:42:10 ANR0984I Process 70 for DELETE FILESPACE started in the BACKGROUND at 08:42:10. 06/09/03 08:42:10 ANR0800I DELETE FILESPACE Registries (fsId=3) for node SAPPLIBP1 started as process 70. 06/09/03 08:42:10 ANR0609I DELETE FILESPACE started as process 70. 06/09/03 08:42:10 ANR0802I DELETE FILESPACE Registries (fsId=3) (backup/arc- hive data) for node SAPPLIBP1 started. 06/09/03 08:42:10 ANR0104E imutil.c(7529): Error 2 deleting row from table Expiring.Objects. 06/09/03 08:42:10 ANRD imfsdel.c(1863): ThreadId80 Error 19 deleting group leader 0 48984968. 06/09/03 08:42:10 ANR0985I Process 70 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 08:42:10. Thanks in advance. Zosi Noriega This e-mail may contain confidential and/or priviledged information. If you are not the intended recepient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail.
Re: Problem deleting filespace SYSTEM OBJECT
My responses are within the text ... On Tue, 24 Sep 2002, Gerhard Rentschler wrote: Hello, in the meantime I upgraded to 5.1.1.6. With this level I could delete the filespace without problem. However, I couldn't resist to try cleanup backupgroup again. Under 5.1.1.4 it worked. It only seemed strange that it obviously didn't finish its work, as Joel described: On 5.1.1.4, I did the CLEANUP BACKUPGROUP and I still could not delete the system objects. I reran the cleanup command numerous times and each time it reported inspecting and deleting fewer objects than the previous run. On 5.1.1.6 cleanup backupgroup stopped immediately with return code 4. In the activity log I found the following messages: 09/24/02 10:31:51 ANR2017I Administrator GERHARD issued command: CLEANUP BACKUPGROUPS 09/24/02 10:31:51 ANRD imutil.c(6663): ThreadId67 Failure deleting member 0 585368742 for group 1637 3 - encountered repeatedly in loop. 09/24/02 10:31:51 ANRD imutil.c(3931): ThreadId67 Error 19 deleting dependents for node 0 fs 0 and leader 1637 3. Now I'm little bit concerned. Is cleanup backupgroup broken or is it my database? The CLEANUP did the same thing for me on 5.1.1.6 until I did an AUDITDB FIX=YES. After doing the auditdb, it ran properly. My suggestion to all TSM admins is to do a QUERY OCCUPANCY * SYSTEM OBJECT to verify that you do not have excessive copies. How can you tell from the output of the q occ command how many excessive copies you have? For most of my servers, the system object consists of about 1800 objects and require 230 MB. Do the math and you will know if you have excessive backups. BTW, I cannot confirm that system objects are not expired. I used the following SQL statement in the middle and at the end of an expiration process: select sum(num_files) from occupancy where filespace_name='SYSTEM OBJECT' The first number I got was 1043479, the last 1012998. So I got rid of at least 30481 files. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany
Re: Problem deleting filespace SYSTEM OBJECT
Hello, in the meantime I upgraded to 5.1.1.6. With this level I could delete the filespace without problem. However, I couldn't resist to try cleanup backupgroup again. Under 5.1.1.4 it worked. It only seemed strange that it obviously didn't finish its work, as Joel described: On 5.1.1.4, I did the CLEANUP BACKUPGROUP and I still could not delete the system objects. I reran the cleanup command numerous times and each time it reported inspecting and deleting fewer objects than the previous run. On 5.1.1.6 cleanup backupgroup stopped immediately with return code 4. In the activity log I found the following messages: 09/24/02 10:31:51 ANR2017I Administrator GERHARD issued command: CLEANUP BACKUPGROUPS 09/24/02 10:31:51 ANRD imutil.c(6663): ThreadId67 Failure deleting member 0 585368742 for group 1637 3 - encountered repeatedly in loop. 09/24/02 10:31:51 ANRD imutil.c(3931): ThreadId67 Error 19 deleting dependents for node 0 fs 0 and leader 1637 3. Now I'm little bit concerned. Is cleanup backupgroup broken or is it my database? My suggestion to all TSM admins is to do a QUERY OCCUPANCY * SYSTEM OBJECT to verify that you do not have excessive copies. How can you tell from the output of the q occ command how many excessive copies you have? BTW, I cannot confirm that system objects are not expired. I used the following SQL statement in the middle and at the end of an expiration process: select sum(num_files) from occupancy where filespace_name='SYSTEM OBJECT' The first number I got was 1043479, the last 1012998. So I got rid of at least 30481 files. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany
Re: Problem deleting filespace SYSTEM OBJECT
and did it solve the problem and were you on 5.1.1.6? On Thu, 19 Sep 2002, Burton, Robert wrote: we are having the same problemand the auditdb for a 37 GB database took over 26 HRs... thanks Robert Burton Enterprise Storage Network Analyst Royal Bank of Canada 315 Front St West Toronto, On, M5V 3A4 * 416-348-3849 * [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 11:42 AM To: [EMAIL PROTECTED] Subject: Problem deleting filespace SYSTEM OBJECT Hello, I ran into the following problem with TSM 5.1.1.4 on AIX 4.3.3. Using the command del filespace rus_zsdsinz 'SYSTEM OBJECT' I get the following messages in the activity log: 09/18/02 16:20:33 ANR0984I Process 452 for DELETE FILESPACE started in the BACKGROUND at 16:20:33. 09/18/02 16:20:33 ANR0800I DELETE FILESPACE * (fsId=4) for node RUS_ZSDSINZ started as process 452. 09/18/02 16:20:33 ANR0802I DELETE FILESPACE * (fsId=4) (backup/archive data) for node RUS_ZSDSINZ started. 09/18/02 16:20:34 ANRD imfsdel.c(1860): ThreadId84 Error 1123 deleting group leader 0 585684848. 09/18/02 16:20:34 ANR0985I Process 452 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 16:20:34. I opened a PMR. Level 1 suggested to run the command cleanup backupgroup and retry the delete filespace command. It didn't help. The next advice was to upgrade to TSM 5.1.1.6 and retry the cleanup backupgroup and del filespace. The next thing to do would be a dsmserv auditdb. However, this would take a lot of time with my 55 GB database. Has anyone else seen this? Level 1 told me that he found only one similar problem. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany -- This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen. ==
Re: Problem deleting filespace SYSTEM OBJECT
Yes I have this problem. The reason I needed to delete the system objects was because they were not being deleted by EXPIRE INVENTORY and they were consuming 30% of my database space. My suggestion to all TSM admins is to do a QUERY OCCUPANCY * SYSTEM OBJECT to verify that you do not have excessive copies. On 5.1.1.4, I did the CLEANUP BACKUPGROUP and I still could not delete the system objects. I reran the cleanup command numerous times and each time it reported inspecting and deleting fewer objects than the previous run. The number was still in the 2000 range when I gave up and installed 5.1.1.6. On this level, expiration still failed to delete the system objects but I could manually delete most of them. As of now I have 6 servers where I can not delete the system objects. I have an open PMR. On Thu, 19 Sep 2002, Gerhard Rentschler wrote: Hello, I ran into the following problem with TSM 5.1.1.4 on AIX 4.3.3. Using the command del filespace rus_zsdsinz 'SYSTEM OBJECT' I get the following messages in the activity log: 09/18/02 16:20:33 ANR0984I Process 452 for DELETE FILESPACE started in the BACKGROUND at 16:20:33. 09/18/02 16:20:33 ANR0800I DELETE FILESPACE * (fsId=4) for node RUS_ZSDSINZ started as process 452. 09/18/02 16:20:33 ANR0802I DELETE FILESPACE * (fsId=4) (backup/archive data) for node RUS_ZSDSINZ started. 09/18/02 16:20:34 ANRD imfsdel.c(1860): ThreadId84 Error 1123 deleting group leader 0 585684848. 09/18/02 16:20:34 ANR0985I Process 452 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 16:20:34. I opened a PMR. Level 1 suggested to run the command cleanup backupgroup and retry the delete filespace command. It didn't help. The next advice was to upgrade to TSM 5.1.1.6 and retry the cleanup backupgroup and del filespace. The next thing to do would be a dsmserv auditdb. However, this would take a lot of time with my 55 GB database. Has anyone else seen this? Level 1 told me that he found only one similar problem. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany
Problem deleting filespace SYSTEM OBJECT
Hello, I ran into the following problem with TSM 5.1.1.4 on AIX 4.3.3. Using the command del filespace rus_zsdsinz 'SYSTEM OBJECT' I get the following messages in the activity log: 09/18/02 16:20:33 ANR0984I Process 452 for DELETE FILESPACE started in the BACKGROUND at 16:20:33. 09/18/02 16:20:33 ANR0800I DELETE FILESPACE * (fsId=4) for node RUS_ZSDSINZ started as process 452. 09/18/02 16:20:33 ANR0802I DELETE FILESPACE * (fsId=4) (backup/archive data) for node RUS_ZSDSINZ started. 09/18/02 16:20:34 ANRD imfsdel.c(1860): ThreadId84 Error 1123 deleting group leader 0 585684848. 09/18/02 16:20:34 ANR0985I Process 452 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 16:20:34. I opened a PMR. Level 1 suggested to run the command cleanup backupgroup and retry the delete filespace command. It didn't help. The next advice was to upgrade to TSM 5.1.1.6 and retry the cleanup backupgroup and del filespace. The next thing to do would be a dsmserv auditdb. However, this would take a lot of time with my 55 GB database. Has anyone else seen this? Level 1 told me that he found only one similar problem. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany
Re: Problem deleting filespace SYSTEM OBJECT
we are having the same problemand the auditdb for a 37 GB database took over 26 HRs... thanks Robert Burton Enterprise Storage Network Analyst Royal Bank of Canada 315 Front St West Toronto, On, M5V 3A4 * 416-348-3849 * [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 11:42 AM To: [EMAIL PROTECTED] Subject: Problem deleting filespace SYSTEM OBJECT Hello, I ran into the following problem with TSM 5.1.1.4 on AIX 4.3.3. Using the command del filespace rus_zsdsinz 'SYSTEM OBJECT' I get the following messages in the activity log: 09/18/02 16:20:33 ANR0984I Process 452 for DELETE FILESPACE started in the BACKGROUND at 16:20:33. 09/18/02 16:20:33 ANR0800I DELETE FILESPACE * (fsId=4) for node RUS_ZSDSINZ started as process 452. 09/18/02 16:20:33 ANR0802I DELETE FILESPACE * (fsId=4) (backup/archive data) for node RUS_ZSDSINZ started. 09/18/02 16:20:34 ANRD imfsdel.c(1860): ThreadId84 Error 1123 deleting group leader 0 585684848. 09/18/02 16:20:34 ANR0985I Process 452 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 16:20:34. I opened a PMR. Level 1 suggested to run the command cleanup backupgroup and retry the delete filespace command. It didn't help. The next advice was to upgrade to TSM 5.1.1.6 and retry the cleanup backupgroup and del filespace. The next thing to do would be a dsmserv auditdb. However, this would take a lot of time with my 55 GB database. Has anyone else seen this? Level 1 told me that he found only one similar problem. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany -- This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen. ==
Re: Problem deleting filespace SYSTEM OBJECT
but did it FIX the problem? -Original Message- From: Burton, Robert [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 2:32 PM To: [EMAIL PROTECTED] Subject: Re: Problem deleting filespace SYSTEM OBJECT we are having the same problemand the auditdb for a 37 GB database took over 26 HRs... thanks Robert Burton Enterprise Storage Network Analyst Royal Bank of Canada 315 Front St West Toronto, On, M5V 3A4 * 416-348-3849 * [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 11:42 AM To: [EMAIL PROTECTED] Subject: Problem deleting filespace SYSTEM OBJECT Hello, I ran into the following problem with TSM 5.1.1.4 on AIX 4.3.3. Using the command del filespace rus_zsdsinz 'SYSTEM OBJECT' I get the following messages in the activity log: 09/18/02 16:20:33 ANR0984I Process 452 for DELETE FILESPACE started in the BACKGROUND at 16:20:33. 09/18/02 16:20:33 ANR0800I DELETE FILESPACE * (fsId=4) for node RUS_ZSDSINZ started as process 452. 09/18/02 16:20:33 ANR0802I DELETE FILESPACE * (fsId=4) (backup/archive data) for node RUS_ZSDSINZ started. 09/18/02 16:20:34 ANRD imfsdel.c(1860): ThreadId84 Error 1123 deleting group leader 0 585684848. 09/18/02 16:20:34 ANR0985I Process 452 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 16:20:34. I opened a PMR. Level 1 suggested to run the command cleanup backupgroup and retry the delete filespace command. It didn't help. The next advice was to upgrade to TSM 5.1.1.6 and retry the cleanup backupgroup and del filespace. The next thing to do would be a dsmserv auditdb. However, this would take a lot of time with my 55 GB database. Has anyone else seen this? Level 1 told me that he found only one similar problem. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany -- This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen. ==
Problem deleting filespace
Hallo, I want to delete a filespace and get the following messages: ANR0802I Delete Filespace _old_internet_c$ (backup/archive data) for node xxx started. ANR0800I DELETE FILESPACE: _old_internet_c$ for node xxx started as process 88. ANRD SSALLOC(413): Error locating storage pool 36. ANR0859E Data storage object erasure failure, DELETE FILESPACE process aborted. ANR0985I Process 88 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 10:40:26. The expiration process shows: ANRD SSALLOC(413): Error locating storage pool 36. ANRD BFCREATE(609): Bitfile erase prohibited - transaction failed. ANRD IMUTIL(1311): Error deleting object (0 12281495) Server: VM 3.1.2.90 Can anyone tell me how to solve this problem? Regards Gerhard Ginzler
Re: Error msg deleting filespace
I tried to delete a clients filesspace in ADSM. But the process aborted with the error below; 11/21/2000 11:06:02 ANRD aferase.c(493): Invalid logSizeRatio INF (logSize=0.1859, size=0.0, aggrSize=0.17103) for aggregate 0.414569. You didn't specify your server level, but APAR IX79165 looks like it will fix this. Richard Sims, BU
Re: Error msg deleting filespace
Hi Henke! I have seen this error before, but I don't know what it means. It's some kind of database inconsistency. You can do a SHOW VOLUMEUSAGE nodename to see the volumes used by this node. Then issue a DELETE VOLUME volume DISCARDDATA=YES to delete the volumes. When this is done you will be able to delete the node from ADSM. Warning!!! This can only be done when you use collocation=YES!! Kindest regards, Eric van Loon -Original Message- From: Henrik Hansson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 21, 2000 11:20 To: [EMAIL PROTECTED] Subject: Error msg deleting filespace Hi I tried to delete a clients filesspace in ADSM. But the process aborted with the error below; 11/21/2000 11:06:02 ANRD aferase.c(493): Invalid logSizeRatio INF (logSize=0.1859, size=0.0, aggrSize=0.17103) for aggregate 0.414569. Anyone got a clue what it might be? Thanx, Henke TANSTAAFL (There Ain't No Such Thing As A Free Lunch) ** This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
