Re: FW: v7 upgrade woes

2016-07-06 Thread Rhodes, Richard L. 
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' 
> > Cc: Ake, Elizabeth K. 
> > 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

2016-06-21 Thread Robert J Molerio 
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' 
> 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' >
> Cc: Ake, Elizabeth K. >
> 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

2016-06-13 Thread Shawn DREW 
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

2016-06-10 Thread Rhodes, Richard L. 
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

2016-06-10 Thread Rhodes, Richard L. 
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

2016-06-10 Thread Nick Marouf 
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  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' 
> > Cc: Ake, Elizabeth K. 
> > 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

2016-06-10 Thread Zoltan Forray 
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' 
> Cc: Ake, Elizabeth K. 
> 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