Re: FW: v7 upgrade woes
We got some good folks from IBM support to help out after getting our local IBM folks involved. And now we appear to have an answer to our TSM v7 upgrades hanging. We use DataDomain via NFS for file devices, tsm db backups, recplans, stuff (reports, etc) and (. . drum roll . .) archfailoverlogdir. Starting in DB2 v10, db2 acquires a flock lock on it's files, and it appears that the DataDomain does not support this. If DB2 can't acquire the lock, it just blocks forever. This behavior appears to be preventable in AIX by specifying the NFS "llocl" mount option. Or, we could just ditch the archfailoverlogdir. This behavior can be tested by a small perl script found here: http://www-01.ibm.com/support/docview.wss?uid=swg21641535 +3 months to find out we needed an extra NFS mount option. (All this is subject to more testing.) Rick > > > > > > > > From: Rhodes, Richard L. > > Sent: Tuesday, June 07, 2016 3:32 PM > > To: 'ADSM: Dist Stor Manager' <ADSM-L@VM.MARIST.EDU> > > Cc: Ake, Elizabeth K. <a...@firstenergycorp.com> > > Subject: v7 upgrade woes > > > > This is half plea for help and half rant (grr). > > > > 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.
Re: FW: v7 upgrade woes
When they first incorporated DB2 into TSM IBM used to have a dedicated DB2 support group to help with these issues. I'm wondering if they were let go during the last IBM purge? Thank you, Systems Administrator Systems & Network Services NYU IT/Technology Operations Services 212-998-1110 646-539-8239 On Tue, Jun 21, 2016 at 9:43 AM, Rhodes, Richard L. < rrho...@firstenergycorp.com> wrote: > Ahhh, the joy of IBM support! > > We are stuck in between the narrow IBM support silos. > > TSM support sees that the db2 database isn't working after an upgrade test > and sent the case to DB2 support. > DB2 support says the database got a "already in use" error of some kind > and wants to know what else is running. DB2 support has no idea what TSM is > or that a TSM upgrade does. > > We need someone who knows TSM, the upgrade process, DB2 and all this on > AIX. But IBM support is incapable of having someone who crosses their > narrow boundaries. It seems our only way out is to either up this case to > a Sev 1 or declare a CRITSIT and force IBM to get multiple areas involved. > > We are SO frustrated. Sometimes I wonder if the people inside IBM who use > TSM have to use the same TSM support we do. > > Rick > > > > > From: Rhodes, Richard L. > Sent: Friday, June 10, 2016 10:59 AM > To: 'ADSM: Dist Stor Manager' <ADSM-L@VM.MARIST.EDU> > Subject: FW: v7 upgrade woes > > We've been testing . . . we tried walking all the upgrades: > > - brought up a 6.3.5 tsm db > - tried upgrade to 7.1.4, it failed/hung (yup, responds like all our tests) > - restored snapshots back to the 6.3.5 setup > - tried upgrade v7.1- WORKED, TSM comes up fine > - tried upgrade to v7.1.1.1 - upg utility said there was nothing to > upgrade! > - tried upgrade to v7.3 - Upgrade worked, but TSM hangs on startup > > The v7.3 upgrade installed just fine and the upgrade utility ended. But > when we try to start TSM it just sits there hung. While TSM is sitting > there "hung" trying to come up, we do a "ps -ef | grep db2" and found that > DB2 was NOT UP. (should have checked that sooner!) > > ps -ef | egrep -i "db2|dsm" > tsmuser 12910806 14221316 0 10:26:23 pts/4 0:00 > /opt/tivoli/tsm/server/bin/dsmserv -i /tsmdata/tsmsap1/config > tsmuser 17432632 12910806 0 10:26:24 pts/4 0:00 db2set -i tsmuser > DB2_PMODEL_SETTINGS >root 199885461 0 09:55:59 - 0:00 > /opt/tivoli/tsm/db2/bin/db2fmcd > > > You can leave the TSM startup "hung" like this for hours and it never goes > any further. > > We keep digging. Support sent us to the DB2 team, hopefully they can help. > > Rick > > > > > > From: Rhodes, Richard L. > Sent: Tuesday, June 07, 2016 3:32 PM > To: 'ADSM: Dist Stor Manager' <ADSM-L@VM.MARIST.EDU ADSM-L@VM.MARIST.EDU>> > Cc: Ake, Elizabeth K. <a...@firstenergycorp.com a...@firstenergycorp.com>> > Subject: v7 upgrade woes > > This is half plea for help and half rant (grr). > > 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. >
FW: v7 upgrade woes
Ahhh, the joy of IBM support! We are stuck in between the narrow IBM support silos. TSM support sees that the db2 database isn't working after an upgrade test and sent the case to DB2 support. DB2 support says the database got a "already in use" error of some kind and wants to know what else is running. DB2 support has no idea what TSM is or that a TSM upgrade does. We need someone who knows TSM, the upgrade process, DB2 and all this on AIX. But IBM support is incapable of having someone who crosses their narrow boundaries. It seems our only way out is to either up this case to a Sev 1 or declare a CRITSIT and force IBM to get multiple areas involved. We are SO frustrated. Sometimes I wonder if the people inside IBM who use TSM have to use the same TSM support we do. Rick From: Rhodes, Richard L. Sent: Friday, June 10, 2016 10:59 AM To: 'ADSM: Dist Stor Manager' <ADSM-L@VM.MARIST.EDU> Subject: FW: v7 upgrade woes We've been testing . . . we tried walking all the upgrades: - brought up a 6.3.5 tsm db - tried upgrade to 7.1.4, it failed/hung (yup, responds like all our tests) - restored snapshots back to the 6.3.5 setup - tried upgrade v7.1- WORKED, TSM comes up fine - tried upgrade to v7.1.1.1 - upg utility said there was nothing to upgrade! - tried upgrade to v7.3 - Upgrade worked, but TSM hangs on startup The v7.3 upgrade installed just fine and the upgrade utility ended. But when we try to start TSM it just sits there hung. While TSM is sitting there "hung" trying to come up, we do a "ps -ef | grep db2" and found that DB2 was NOT UP. (should have checked that sooner!) ps -ef | egrep -i "db2|dsm" tsmuser 12910806 14221316 0 10:26:23 pts/4 0:00 /opt/tivoli/tsm/server/bin/dsmserv -i /tsmdata/tsmsap1/config tsmuser 17432632 12910806 0 10:26:24 pts/4 0:00 db2set -i tsmuser DB2_PMODEL_SETTINGS root 199885461 0 09:55:59 - 0:00 /opt/tivoli/tsm/db2/bin/db2fmcd You can leave the TSM startup "hung" like this for hours and it never goes any further. We keep digging. Support sent us to the DB2 team, hopefully they can help. Rick From: Rhodes, Richard L. Sent: Tuesday, June 07, 2016 3:32 PM To: 'ADSM: Dist Stor Manager' <ADSM-L@VM.MARIST.EDU<mailto:ADSM-L@VM.MARIST.EDU>> Cc: Ake, Elizabeth K. <a...@firstenergycorp.com<mailto:a...@firstenergycorp.com>> Subject: v7 upgrade woes This is half plea for help and half rant (grr). 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.
Re: FW: v7 upgrade woes
We just went through a complete upgrade. 6.3.5 -> 7.1.5 23 instances on 11 servers. 1 AIX, 2 windows, rest Linux. What worked for us is only installing the license package from the passport 7.1.3 package, then upgrading directly to 7.1.5 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rhodes, Richard L. Sent: Friday, June 10, 2016 3:10 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] FW: v7 upgrade woes We just brought up new pSeries chassis to rollover our existing pSeries chassis. The new lpars will be AIX v7. The plan is to get up to TSM v7, then swing the storage to new lpars on the new chassis. Of course, testing all this swing is yet to occur. We’ve got stuck just on the TSM v6-v7 upgrade. Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Nick Marouf Sent: Friday, June 10, 2016 2:37 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: FW: v7 upgrade woes Fyi, When I upgraded on AIX I had went from 6.3.4.0 to 7.1.3.0 and then to 7.1.5.100 with no issues. Date (GMT) Version Pre-release Driver 2016/06/01 18:29:52 7.1.3.0 2016/06/07 17:11:31 7.1.5.0 AIX 6100-09 next two upgrade are on AIX 7100-04 On Fri, Jun 10, 2016 at 12:28 PM, Zoltan Forray <zfor...@vcu.edu> wrote: > Since I need to upgrade 6-TSM servers (2-of them at the same time since > they are Library Managers) to 7.1.5.200, I am closely following this > thread/discussion about upgrade issues. > > Have all these woes only been on AIX system? > > I tested an old decommissioned server (all user data had been exported to > another TSM server) and upgraded from 6.3.5.100 to 7.1.3.00 base (Passport > downloaded with license keys) and then to 7.1.5.100 with no issues. Of > course, mine are all RedHat 6 Linux. > > On Fri, Jun 10, 2016 at 10:59 AM, Rhodes, Richard L. < > rrho...@firstenergycorp.com> wrote: > > > We've been testing . . . we tried walking all the upgrades: > > > > - brought up a 6.3.5 tsm db > > - tried upgrade to 7.1.4, it failed/hung (yup, responds like all our > tests) > > - restored snapshots back to the 6.3.5 setup > > - tried upgrade v7.1- WORKED, TSM comes up fine > > - tried upgrade to v7.1.1.1 - upg utility said there was nothing to > > upgrade! > > - tried upgrade to v7.3 - Upgrade worked, but TSM hangs on startup > > > > The v7.3 upgrade installed just fine and the upgrade utility ended. But > > when we try to start TSM it just sits there hung. While TSM is sitting > > there "hung" trying to come up, we do a "ps -ef | grep db2" and found > that > > DB2 was NOT UP. (should have checked that sooner!) > > > > ps -ef | egrep -i "db2|dsm" > > tsmuser 12910806 14221316 0 10:26:23 pts/4 0:00 > > /opt/tivoli/tsm/server/bin/dsmserv -i /tsmdata/tsmsap1/config > > tsmuser 17432632 12910806 0 10:26:24 pts/4 0:00 db2set -i tsmuser > > DB2_PMODEL_SETTINGS > >root 199885461 0 09:55:59 - 0:00 > > /opt/tivoli/tsm/db2/bin/db2fmcd > > > > > > You can leave the TSM startup "hung" like this for hours and it never > goes > > any further. > > > > We keep digging. Support sent us to the DB2 team, hopefully they can > help. > > > > Rick > > > > > > > > > > > > From: Rhodes, Richard L. > > Sent: Tuesday, June 07, 2016 3:32 PM > > To: 'ADSM: Dist Stor Manager' <ADSM-L@VM.MARIST.EDU> > > Cc: Ake, Elizabeth K. <a...@firstenergycorp.com> > > Subject: v7 upgrade woes > > > > This is half plea for help and half rant (grr). > > > > 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
Re: FW: v7 upgrade woes
We just brought up new pSeries chassis to rollover our existing pSeries chassis. The new lpars will be AIX v7. The plan is to get up to TSM v7, then swing the storage to new lpars on the new chassis. Of course, testing all this swing is yet to occur. We’ve got stuck just on the TSM v6-v7 upgrade. Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Nick Marouf Sent: Friday, June 10, 2016 2:37 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: FW: v7 upgrade woes Fyi, When I upgraded on AIX I had went from 6.3.4.0 to 7.1.3.0 and then to 7.1.5.100 with no issues. Date (GMT) Version Pre-release Driver 2016/06/01 18:29:52 7.1.3.0 2016/06/07 17:11:31 7.1.5.0 AIX 6100-09 next two upgrade are on AIX 7100-04 On Fri, Jun 10, 2016 at 12:28 PM, Zoltan Forray <zfor...@vcu.edu> wrote: > Since I need to upgrade 6-TSM servers (2-of them at the same time since > they are Library Managers) to 7.1.5.200, I am closely following this > thread/discussion about upgrade issues. > > Have all these woes only been on AIX system? > > I tested an old decommissioned server (all user data had been exported to > another TSM server) and upgraded from 6.3.5.100 to 7.1.3.00 base (Passport > downloaded with license keys) and then to 7.1.5.100 with no issues. Of > course, mine are all RedHat 6 Linux. > > On Fri, Jun 10, 2016 at 10:59 AM, Rhodes, Richard L. < > rrho...@firstenergycorp.com> wrote: > > > We've been testing . . . we tried walking all the upgrades: > > > > - brought up a 6.3.5 tsm db > > - tried upgrade to 7.1.4, it failed/hung (yup, responds like all our > tests) > > - restored snapshots back to the 6.3.5 setup > > - tried upgrade v7.1- WORKED, TSM comes up fine > > - tried upgrade to v7.1.1.1 - upg utility said there was nothing to > > upgrade! > > - tried upgrade to v7.3 - Upgrade worked, but TSM hangs on startup > > > > The v7.3 upgrade installed just fine and the upgrade utility ended. But > > when we try to start TSM it just sits there hung. While TSM is sitting > > there "hung" trying to come up, we do a "ps -ef | grep db2" and found > that > > DB2 was NOT UP. (should have checked that sooner!) > > > > ps -ef | egrep -i "db2|dsm" > > tsmuser 12910806 14221316 0 10:26:23 pts/4 0:00 > > /opt/tivoli/tsm/server/bin/dsmserv -i /tsmdata/tsmsap1/config > > tsmuser 17432632 12910806 0 10:26:24 pts/4 0:00 db2set -i tsmuser > > DB2_PMODEL_SETTINGS > >root 199885461 0 09:55:59 - 0:00 > > /opt/tivoli/tsm/db2/bin/db2fmcd > > > > > > You can leave the TSM startup "hung" like this for hours and it never > goes > > any further. > > > > We keep digging. Support sent us to the DB2 team, hopefully they can > help. > > > > Rick > > > > > > > > > > > > From: Rhodes, Richard L. > > Sent: Tuesday, June 07, 2016 3:32 PM > > To: 'ADSM: Dist Stor Manager' <ADSM-L@VM.MARIST.EDU> > > Cc: Ake, Elizabeth K. <a...@firstenergycorp.com> > > Subject: v7 upgrade woes > > > > This is half plea for help and half rant (grr). > > > > 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 thi
Re: FW: v7 upgrade woes
Yes, they are all AIX 6100-09. We have DR lpars for each PROD lpar. When we upgrade we test by bringing up the appropriate TSM instance on it's DR server, perform the upgrade to test, leave the DR aix at the new TSM version, then upgrade the PROD lpar/TSM. We've tested two TSM instances on their DR lpars and both have this problem. Given how others have no problem with v7 upgrade, I think it's something about our systems (AIX?), but we have no idea. It's up to support . . . Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Friday, June 10, 2016 2:29 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: FW: v7 upgrade woes Since I need to upgrade 6-TSM servers (2-of them at the same time since they are Library Managers) to 7.1.5.200, I am closely following this thread/discussion about upgrade issues. Have all these woes only been on AIX system? I tested an old decommissioned server (all user data had been exported to another TSM server) and upgraded from 6.3.5.100 to 7.1.3.00 base (Passport downloaded with license keys) and then to 7.1.5.100 with no issues. Of course, mine are all RedHat 6 Linux. On Fri, Jun 10, 2016 at 10:59 AM, Rhodes, Richard L. < rrho...@firstenergycorp.com> wrote: > We've been testing . . . we tried walking all the upgrades: > > - brought up a 6.3.5 tsm db > - tried upgrade to 7.1.4, it failed/hung (yup, responds like all our tests) > - restored snapshots back to the 6.3.5 setup > - tried upgrade v7.1- WORKED, TSM comes up fine > - tried upgrade to v7.1.1.1 - upg utility said there was nothing to > upgrade! > - tried upgrade to v7.3 - Upgrade worked, but TSM hangs on startup > > The v7.3 upgrade installed just fine and the upgrade utility ended. But > when we try to start TSM it just sits there hung. While TSM is sitting > there "hung" trying to come up, we do a "ps -ef | grep db2" and found that > DB2 was NOT UP. (should have checked that sooner!) > > ps -ef | egrep -i "db2|dsm" > tsmuser 12910806 14221316 0 10:26:23 pts/4 0:00 > /opt/tivoli/tsm/server/bin/dsmserv -i /tsmdata/tsmsap1/config > tsmuser 17432632 12910806 0 10:26:24 pts/4 0:00 db2set -i tsmuser > DB2_PMODEL_SETTINGS >root 199885461 0 09:55:59 - 0:00 > /opt/tivoli/tsm/db2/bin/db2fmcd > > > You can leave the TSM startup "hung" like this for hours and it never goes > any further. > > We keep digging. Support sent us to the DB2 team, hopefully they can help. > > Rick > > > > > > From: Rhodes, Richard L. > Sent: Tuesday, June 07, 2016 3:32 PM > To: 'ADSM: Dist Stor Manager' <ADSM-L@VM.MARIST.EDU> > Cc: Ake, Elizabeth K. <a...@firstenergycorp.com> > Subject: v7 upgrade woes > > This is half plea for help and half rant (grr). > > 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. > -- *Zoltan Forray* TSM Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator (in training) Virginia Commonwealth University UCC/Office of Tec
Re: FW: v7 upgrade woes
Fyi, When I upgraded on AIX I had went from 6.3.4.0 to 7.1.3.0 and then to 7.1.5.100 with no issues. Date (GMT) Version Pre-release Driver 2016/06/01 18:29:52 7.1.3.0 2016/06/07 17:11:31 7.1.5.0 AIX 6100-09 next two upgrade are on AIX 7100-04 On Fri, Jun 10, 2016 at 12:28 PM, Zoltan Forray <zfor...@vcu.edu> wrote: > Since I need to upgrade 6-TSM servers (2-of them at the same time since > they are Library Managers) to 7.1.5.200, I am closely following this > thread/discussion about upgrade issues. > > Have all these woes only been on AIX system? > > I tested an old decommissioned server (all user data had been exported to > another TSM server) and upgraded from 6.3.5.100 to 7.1.3.00 base (Passport > downloaded with license keys) and then to 7.1.5.100 with no issues. Of > course, mine are all RedHat 6 Linux. > > On Fri, Jun 10, 2016 at 10:59 AM, Rhodes, Richard L. < > rrho...@firstenergycorp.com> wrote: > > > We've been testing . . . we tried walking all the upgrades: > > > > - brought up a 6.3.5 tsm db > > - tried upgrade to 7.1.4, it failed/hung (yup, responds like all our > tests) > > - restored snapshots back to the 6.3.5 setup > > - tried upgrade v7.1- WORKED, TSM comes up fine > > - tried upgrade to v7.1.1.1 - upg utility said there was nothing to > > upgrade! > > - tried upgrade to v7.3 - Upgrade worked, but TSM hangs on startup > > > > The v7.3 upgrade installed just fine and the upgrade utility ended. But > > when we try to start TSM it just sits there hung. While TSM is sitting > > there "hung" trying to come up, we do a "ps -ef | grep db2" and found > that > > DB2 was NOT UP. (should have checked that sooner!) > > > > ps -ef | egrep -i "db2|dsm" > > tsmuser 12910806 14221316 0 10:26:23 pts/4 0:00 > > /opt/tivoli/tsm/server/bin/dsmserv -i /tsmdata/tsmsap1/config > > tsmuser 17432632 12910806 0 10:26:24 pts/4 0:00 db2set -i tsmuser > > DB2_PMODEL_SETTINGS > >root 199885461 0 09:55:59 - 0:00 > > /opt/tivoli/tsm/db2/bin/db2fmcd > > > > > > You can leave the TSM startup "hung" like this for hours and it never > goes > > any further. > > > > We keep digging. Support sent us to the DB2 team, hopefully they can > help. > > > > Rick > > > > > > > > > > > > From: Rhodes, Richard L. > > Sent: Tuesday, June 07, 2016 3:32 PM > > To: 'ADSM: Dist Stor Manager' <ADSM-L@VM.MARIST.EDU> > > Cc: Ake, Elizabeth K. <a...@firstenergycorp.com> > > Subject: v7 upgrade woes > > > > This is half plea for help and half rant (grr). > > > > 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. > > > > > > -- > *Zoltan Forray* > TSM Software & Hardware Administrator > Xymon Monitor Administrator > VMware Administrator (in training) > Virginia Commonwealth University > UCC/Office of Technology Services > www.ucc.vcu.edu > zfor...@vcu.edu - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://infosecurity.vcu.edu/phishing.html >
Re: FW: v7 upgrade woes
Since I need to upgrade 6-TSM servers (2-of them at the same time since they are Library Managers) to 7.1.5.200, I am closely following this thread/discussion about upgrade issues. Have all these woes only been on AIX system? I tested an old decommissioned server (all user data had been exported to another TSM server) and upgraded from 6.3.5.100 to 7.1.3.00 base (Passport downloaded with license keys) and then to 7.1.5.100 with no issues. Of course, mine are all RedHat 6 Linux. On Fri, Jun 10, 2016 at 10:59 AM, Rhodes, Richard L. < rrho...@firstenergycorp.com> wrote: > We've been testing . . . we tried walking all the upgrades: > > - brought up a 6.3.5 tsm db > - tried upgrade to 7.1.4, it failed/hung (yup, responds like all our tests) > - restored snapshots back to the 6.3.5 setup > - tried upgrade v7.1- WORKED, TSM comes up fine > - tried upgrade to v7.1.1.1 - upg utility said there was nothing to > upgrade! > - tried upgrade to v7.3 - Upgrade worked, but TSM hangs on startup > > The v7.3 upgrade installed just fine and the upgrade utility ended. But > when we try to start TSM it just sits there hung. While TSM is sitting > there "hung" trying to come up, we do a "ps -ef | grep db2" and found that > DB2 was NOT UP. (should have checked that sooner!) > > ps -ef | egrep -i "db2|dsm" > tsmuser 12910806 14221316 0 10:26:23 pts/4 0:00 > /opt/tivoli/tsm/server/bin/dsmserv -i /tsmdata/tsmsap1/config > tsmuser 17432632 12910806 0 10:26:24 pts/4 0:00 db2set -i tsmuser > DB2_PMODEL_SETTINGS >root 199885461 0 09:55:59 - 0:00 > /opt/tivoli/tsm/db2/bin/db2fmcd > > > You can leave the TSM startup "hung" like this for hours and it never goes > any further. > > We keep digging. Support sent us to the DB2 team, hopefully they can help. > > Rick > > > > > > From: Rhodes, Richard L. > Sent: Tuesday, June 07, 2016 3:32 PM > To: 'ADSM: Dist Stor Manager' <ADSM-L@VM.MARIST.EDU> > Cc: Ake, Elizabeth K. <a...@firstenergycorp.com> > Subject: v7 upgrade woes > > This is half plea for help and half rant (grr). > > 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. > -- *Zoltan Forray* TSM Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator (in training) Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
FW: v7 upgrade woes
We've been testing . . . we tried walking all the upgrades: - brought up a 6.3.5 tsm db - tried upgrade to 7.1.4, it failed/hung (yup, responds like all our tests) - restored snapshots back to the 6.3.5 setup - tried upgrade v7.1- WORKED, TSM comes up fine - tried upgrade to v7.1.1.1 - upg utility said there was nothing to upgrade! - tried upgrade to v7.3 - Upgrade worked, but TSM hangs on startup The v7.3 upgrade installed just fine and the upgrade utility ended. But when we try to start TSM it just sits there hung. While TSM is sitting there "hung" trying to come up, we do a "ps -ef | grep db2" and found that DB2 was NOT UP. (should have checked that sooner!) ps -ef | egrep -i "db2|dsm" tsmuser 12910806 14221316 0 10:26:23 pts/4 0:00 /opt/tivoli/tsm/server/bin/dsmserv -i /tsmdata/tsmsap1/config tsmuser 17432632 12910806 0 10:26:24 pts/4 0:00 db2set -i tsmuser DB2_PMODEL_SETTINGS root 199885461 0 09:55:59 - 0:00 /opt/tivoli/tsm/db2/bin/db2fmcd You can leave the TSM startup "hung" like this for hours and it never goes any further. We keep digging. Support sent us to the DB2 team, hopefully they can help. Rick From: Rhodes, Richard L. Sent: Tuesday, June 07, 2016 3:32 PM To: 'ADSM: Dist Stor Manager' <ADSM-L@VM.MARIST.EDU> Cc: Ake, Elizabeth K. <a...@firstenergycorp.com> Subject: v7 upgrade woes This is half plea for help and half rant (grr). 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.
Re: v7 upgrade woes
Hey Rick, I had some challenges with the upgrade as well (3 machines - 10 TSM Instances). We upgraded from 6.3.4.3 to 7.1.5 though. Anyhow, the script/file that your Installation is getting stuck at caught my attention: com.tivoli.dsm.server.db2.* I hope the following helps... So here's what we did: The upgrade completed but the TSM Server started complaining about not being licensed. (yup I understand, yours doesn't finish, but bear with me...) The TSM Server was halted, and server version 7.1.3 was downloaded to get the "TSM" licensing package. (7.1.5 didn't not apply the license for TSM nor DB2...) The "TSM" licensing package was installed but when we attempted to start the TSM Server it failed to start with these messages: IBM Tivoli Storage Manager for AIX Version 7, Release 1, Level 5.000 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2016. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7801I Subsystem process ID is 10223948. ANR0900I Processing options file /db2home/tsminst0/dsmserv.opt. ANR7811I Using instance directory /db2home/tsminst0. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0151W Database manager fails to start. For more information about the failure, issue the db2start command. ANR0171I dbiconn.c(1844): Error detected on 0:1, database in evaluation mode. ANR0162W Supplemental database diagnostic information: -1:08001:-1032 ([IBM][CLI Driver] SQL1032N No start database manager command was issued. SQLSTATE=57019 When attempting to run "db2start", got this message: tsminst0@entbkcol1 /db2home/tsminst0: db2start 03/24/2016 22:32:13 0 0 SQL8000N DB2START processing failed; a valid product license was not found. If you have licensed this product, ensure the license key is properly registered. You can register the license using the db2licm command. The license key can be obtained from your licensed product CD. SQL1032N No start database manager command was issued. SQLSTATE=57019 Ran db2 command to verify db2 license, and showed as EXPIRED: /db2home/tsminst0/sqllib/adm/db2licm -l Product name: "DB2 Enterprise Server Edition" Expiry date: "Expired" Product identifier: "db2ese" Version information: "10.5" Then, - change directories to /repository/native - list the DB2 zip file: ls -tlr com.tivoli.dsm.server.db2*.zip - Uncompressed the file: com.tivoli.dsm.server.db2.aix.ppc64_10.5.500.111.zip (<== SEE, I KNEW THAT SCRIPT/FILE NAMING RANG-A-BELL!) - change directories to: /repository/native/ese/db2/license - list the file: tmp/image/tsmsrv713/repository/native/ese/db2/license# ls -tlr db2ese.lic -rw-r--r--1 root system 912 Apr 29 2015 db2ese.lic - Copy the file to: /db2home/tsminst0/sqllib/adm - Then as the instance owner run the following command to apply the license: db2licm -a db2ese.lic - Check to see if the license was installed: $ /db2home/tsminst0/sqllib/adm/db2licm -l Product name: "DB2 Enterprise Server Edition" License type: "Restricted" Expiry date: "Permanent" Product identifier: "db2ese" Version information: "10.5" IT SHOULD SHOW AS "RESTRICTED" The fix for the issue we ran into is in APAR IT14939. Good Luck! On Tue, Jun 7, 2016 at 2:31 PM, Rhodes, Richard L. < rrho...@firstenergycorp.com> wrote: > This is half plea for help and half rant (grr). > > 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
Re: v7 upgrade woes
These are the steps that will let you monitor the progress... nohup /opt/tivoli/tsm/server/bin/dsmserv insertdb sesswait=60 >insert.out 2>&1 & Monitor the output of the process. Verify that the DSMSERV INSERTDB process has issued the following message before continuing to the next step: ANR1336I INSERTDB: Ready for connections from the source server Issue the following command to monitor the process output in the insert.out file: tail -f insert.out (12) Start the extraction from the original server. Specify the TCP/IP address and port for the V6.3 server. Direct the output of the process to a file for monitoring: run as root ID nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd extractdb hladdress=10.xxx.xxx.xxx lladdress=1500 >extract.out 2>&1 & nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd extractdb hladdress=127.0.0.1 lladdress=1500 >extract.out 2>&1 & Monitor the processes for errors and warning messages, and for items that you might need to take action on: tail -f extract.out (13) Ensure you get something similar to this message: ANR0900I Processing options file /home/tsminst1/dsmserv.opt. ANR0921I Tracing is now active to file server.trace. ANR7811I Using instance directory /home/tsminst1. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0200I Recovery log assigned capacity is 13052 megabytes. ANR0201I Database assigned capacity is 143352 megabytes. ANR0306I Recovery log volume mount in progress. ANR0353I Recovery log analysis pass in progress. ANR0354I Recovery log redo pass in progress. ANR0355I Recovery log undo pass in progress. ANR0352I Transaction recovery complete. ANR1635I The server machine GUID, 00.00.00.00.9f.fb.11.db.94.98.08.63.0a.65.cd.15, has initialized. ANR2283I Database backup trigger defined, but is disabled. ANR4726I The NAS-NDMP support module has been loaded. ANR8440E Initialization failed for SCSI library DD565LIB; will retry in 2 minute(s). ANR8440E Initialization failed for SCSI library LANFREELIB; will retry in 2 minute(s). ANR4029I EXTRACTDB: Database checkpoint started. ANR4030I EXTRACTDB: Database checkpoint completed. ANR0610I EXTRACTDB started by ADMINISTRATOR as process 1. ANR8214E Session open with 10.xxx.xxx.xxx failed due to connection refusal. ANR0454E Session rejected by server $UPGRADETARGET$, reason: Communication Failure. ANR1396E EXTRACTDB: Process 1, database extract, has completed with errors. ANR1383I EXTRACTDB: Found 0 database objects. ANR1384I EXTRACTDB: Processed 0 database objects. ANR1385I EXTRACTDB: Skipped 0 empty database objects. ANR1386I EXTRACTDB: Failed to process 0 database objects. ANR1387I EXTRACTDB: Processed 0 database records. ANR1388I EXTRACTDB: Read 0 database pages. ANR1389I EXTRACTDB: Wrote 0 bytes. ANR1390I EXTRACTDB: Elapsed time was 0:00:01. ANR1391I EXTRACTDB: Throughput was 0.00 megabytes per hour. ANR1394E EXTRACTDB: Failed to start or failed to complete successfully. s0017pdv root@/home/tsminst1 -> ANR0478W Session request refused. Server is running in standalone mode. ANR1336I INSERTDB: Ready for connections from the source server. Remaining time: 0:56:00 ANR1337I A DBBACKUP trigger has been removed. ANR1379I INSERTDB: Read 86,445,332 bytes and inserted 378,967 database entries in 0:00:00 (0.00 megabytes per hour). ___ Database Upgrade. ANR1305I Disk volume /dev/rtsmcxdsklv1 varied online. ANR0409I Session 1 ended for server $UPGRADETARGET$ (AIX). ANR1382I EXTRACTDB: Process 1, database extract, has completed. ANR1383I EXTRACTDB: Found 118 database objects. ANR1384I EXTRACTDB: Processed 59 database objects. ANR1385I EXTRACTDB: Skipped 59 empty database objects. ANR1386I EXTRACTDB: Failed to process 0 database objects. ANR1387I EXTRACTDB: Processed 788,564 database records. ANR1388I EXTRACTDB: Read 35,110 database pages. ANR1389I EXTRACTDB: Wrote 140,828,690 bytes. ANR1390I EXTRACTDB: Elapsed time was 0:02:30. ANR1391I EXTRACTDB: Throughput was 3216.00 megabytes per hour. _ Good luck! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Nick Marouf Sent: Tuesday, June 7, 2016 12:46 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] v7 upgrade woes Sorry to hear that. I just went through this similar upgrade without a hitch, and I'm planning two more. On Tue, Jun 7, 2016 at 1:31 PM, Rhodes, Richard L. < rrho...@firstenergycorp.com> wrote: > This is half plea for help and half rant (grr). > > 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.DB2PostI
Re: v7 upgrade woes
Sorry to hear that. I just went through this similar upgrade without a hitch, and I'm planning two more. On Tue, Jun 7, 2016 at 1:31 PM, Rhodes, Richard L. < rrho...@firstenergycorp.com> wrote: > This is half plea for help and half rant (grr). > > 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. >
Re: 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." <rrho...@firstenergycorp.com> To: ADSM-L@VM.MARIST.EDU Date: 06/07/2016 03:35 PM Subject: [ADSM-L] v7 upgrade woes Sent by:"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> This is half plea for help and half rant (grr). 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.
v7 upgrade woes
This is half plea for help and half rant (grr). 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.
