Hi TSM-ers! Good news, my database inconsistencies are removed. Just for future reference (although I doubt there are many more TSM 5.3 users out there) I will post here what I have been instructed by IBM Support to solve this: 1) Create an admin account IBM_SERVICE with class=system. The following commands do NOT work with any other admin account! 2) Issue the following command: repair orphans scan 3) Use the q actlog search=orphans to check for it's status. The console does NOT show you, apparently the output is only written to the actlog. Here is the sample output:
Repair Orphans began at 08/24/09 16:15:31.(SESSION: 8579286) Repair Orphans checking AF.Bitfiles and BF tables at 08/24/09 16:15:31.(SESSION: 8579286) Repair Orphans: Pool -2 for bitfile 0.883051744 does not exist.(SESSION: 8579286) Repair Orphans: Pool -2 for bitfile 0.883055277 does not exist.(SESSION: 8579286) Repair Orphans: Pool -2 for bitfile 0.883055287 does not exist.(SESSION: 8579286) <snip> Repair Orphans exit at 08/24/09 17:25:08, 2441 rows deleted.(SESSION: 8579286) 4) Issue the following command:repair orphans scan. Output: Repair Orphans: Resetting restart from 0.1408476986 to 0.0.(SESSION: 8699969) 5) Issue the following command:repair orphans repair. Output: Repair Orphans began at 08/25/09 11:14:06.(SESSION: 8699969) Repair Orphans checking AF.Bitfiles and BF tables at 08/25/09 11:14:06.(SESSION: 8699969) Repair Orphans: Deleted bitfile 0.883051744 in invalid storage pool -2.(SESSION: 8699969) Repair Orphans: Deleted bitfile 0.883055277 in invalid storage pool -2.(SESSION: 8699969) Repair Orphans: Deleted bitfile 0.883055287 in invalid storage pool -2.(SESSION: 8699969) <snip> Repair Orphans exit at 08/25/09 12:46:22, 2441 rows deleted.(SESSION: 8699969) I can now delete the filespaces successfully. Thank you all very much for your help! Kind regards, Eric van Loon KLM Royal Dutch Airlines -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of km Sent: vrijdag 21 augustus 2009 19:18 To: ADSM-L@VM.MARIST.EDU Subject: Re: Dealloc prohibited - transaction failed On 21/08, Loon, EJ van - SPLXM wrote: > Hi KM! > > sho aggr 0 1086967169: > > AggrId: 0.1086967169, AggrSize: 0.717, LogSize: 0.717, NumFiles: 1. > Aliases: None. > > I guess I have to parc the undeletable nodes somewhere until the TSM > server is upgraded to a supported level... > Kind regards, > Eric van Loon > KLM Royal Dutch Airlines > Well, you still have two (traditional) options: 1) dsmserv AUDITDB fix=yes 2) Try to expire the filespace from the client. Set up an empty directory as a filespace with the same name as the filespace to be deleted, either with virtualmountpoint (UNIX), SUBST (Win) or union mount (Linux/BSD) and then run dsmc i. -km ********************************************************************** 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. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 **********************************************************************