Re: [ADSM-L] v7 upgrade woes

Richard,
Have you tried using the truss utility to monitor the upgrade process ?
Thank You,
Neil Strand

www.cassevern.com
6201 Chevy Chase Drive, Laurel, MD 20707
800.252.4715 • 301.776.3400 • Fax 301.776.3444

From: "Rhodes, Richard L." <rrhodes AT FIRSTENERGYCORP DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: 06/07/2016 03:35 PM
Subject: [ADSM-L] v7 upgrade woes
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

This is half plea for help and half rant (grrrrrr). For the past two months we've been trying to test a TSM v6.3.5 to v7.1.4/v7.1.5 upgrade . . . . and have completely failed! TSM v6.3.5 AIX 6100-09 upgrade to TSM v7.1.4 and/or v7.1.5 When we run the upgrade it runs to this status message: Installing: [(99%) com.tivoli.dsm.server.db2.DB2PostInstall ] Then it sits, doing nothing. AIX sees no db2 activity, no java activity, no nothing. It sits for hours! We've let it sit once for 13 hours (overnight) and the above message was still there. Eventually we kill it. We've tried: two separate AIX systems two separate TSM's (one 400gb db and one 100gb db) probably tried 8-10 upgrades, all failed Support had us try a DB2 standalone upgrade and it also never finished. We've worked with support and got nowhere. They have no idea what is happening, let alone any idea of how to figure out what is happening. They did find one issue - we have to install a base XLC runtime v13.1.0.0 before the v7 upgrade. Any thoughts are welcome. Rick ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.