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" 10/12/2005 05:38 Please respond to "ADSM: Dist Stor Manager" 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 ' 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 A
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" 10/12/2005 05:38 Please respond to "ADSM: Dist Stor Manager" 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 ' 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 * *
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 ' 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 informati
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
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 ' 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