Hi Steve, Did you check the content of the .profile file of the instance user on the DR host? It should be identical to the one on the prime site. If that's OK you could try and drop the instance and recatalog the database on the DR node:
# /opt/tivoli/tsm/db2/instance/db2idrop <instancename> # /opt/tivoli/tsm/db2/instance/db2icrt -a server -s ese -u <instance_user> <instance_user_password> $ db2 catalog db tsmdb1 on /tsm/wtsmt01 Maybe that helps? Kind regards, Eric van Loon Air France/KLM Storage Engineering -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Harris, Steven Sent: woensdag 23 mei 2018 1:36 To: ADSM-L@VM.MARIST.EDU Subject: TSM Instance can't find its instance directory. Hi guys I have a curly one here. TSM 7.1.1.300 on AIX 7.1 I'm preparing for a DR test. The DR process is that the TSM instance directory, database, logs and disk/file storage pools reside on an IBM V840 flash device. These are mirrored to the DR site using remote copy. The old way was to use the remote copy directly, the new way is to run a flashcopy backup of the remote-copied volumes and mount those. Old process or new I get the same error. It last worked November last year. On my test instance, when I start at prime site as the instance user, it finds the instance directory /tsm/wtsmt01. It then opens the dsmserv.opt and initialization completes as usual. When I start at the DR site, also as the instance user, with the same filesystems mounted, and in the instance directory, it does not find the instance directory, but tries to use the root directory. Obviously the dsmserv.opt file is not found and the process goes down hill from there. Primary: ANR0900I Processing options file /tsm/wtsmt01/dsmserv.opt. DR: ANR0905W Options file /dsmserv.opt not found. ANR0010W Unable to open message catalog for language en_AU.8859-15. The default language message catalog will be used. ANR7811I Using instance directory . I have compared the two sets of environment variables and they are identical, apart from obvious things like PID and RANDOM. According to the doc, the instance directory is supposed to be set from the DB2 instance directory. This is checked with db2 get dbm cfg | grep DFTDBPATH and is the same on both boxes. I even explicitly set it again on the DR side to no effect. TSM Support has been no help. Can anyone point me in the right direction? Even some idea of how to trace what's happening would be useful. Thanks Steve Steven Harris TSM Admin/Consultant Canberra Australia This message and any attachment is confidential and may be privileged or otherwise protected from disclosure. You should immediately delete the message if you are not the intended recipient. If you have received this email by mistake please delete it from your system; you should not copy the message or disclose its content to anyone. This electronic communication may contain general financial product advice but should not be relied upon or construed as a recommendation of any financial product. The information has been prepared without taking into account your objectives, financial situation or needs. You should consider the Product Disclosure Statement relating to the financial product and consult your financial adviser before making a decision about whether to acquire, hold or dispose of a financial product. For further details on the financial product please go to http://www.bt.com.au Past performance is not a reliable indicator of future performance. ******************************************************** 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 ********************************************************
