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. <
rrhodes AT firstenergycorp DOT 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 AT VM.MARIST DOT 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 19988546 1 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 AT VM.MARIST DOT EDU<mailto:
> ADSM-L AT VM.MARIST DOT EDU>>
> Cc: Ake, Elizabeth K. <akee AT firstenergycorp DOT com<mailto:
> akee AT firstenergycorp DOT com>>
> Subject: v7 upgrade woes
>
> 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.
>
|
