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 AT VM.MARIST DOT EDU] On Behalf Of
Rhodes, Richard L.
Sent: Friday, June 10, 2016 3:10 PM
To: ADSM-L AT VM.MARIST DOT 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 AT VM.MARIST DOT EDU] On Behalf Of
Nick Marouf
Sent: Friday, June 10, 2016 2:37 PM
To: ADSM-L AT VM.MARIST DOT 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 <zforray AT vcu DOT 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. <
> rrhodes AT firstenergycorp DOT 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 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>
> > Cc: Ake, Elizabeth K. <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.
> >
>
>
>
> --
> *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
> zforray AT vcu DOT 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
>
-----------------------------------------
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.
This message and any attachments (the "message") is intended solely for the
addressees and is confidential. If you receive this message in error, please
delete it and immediately notify the sender. Any use not in accord with its
purpose, any dissemination or disclosure, either whole or partial, is
prohibited except formal approval. The internet can not guarantee the integrity
of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore
be liable for the message if modified. Please note that certain functions and
services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Unless otherwise provided above, this message was sent by BNP Paribas, or one
of its affiliates in Canada, having an office at 1981 McGill College Avenue,
Montreal, QC, H3A 2W8, Canada. To the extent this message is being sent from or
to Canada, you may unsubscribe from receiving commercial electronic messages by
using this link: www.bnpparibas.ca/en/unsubscribe/
<http://www.bnpparibas.ca/en/unsubscribe/>. See www.bnpparibas.ca
<http://www.bnpparibas.ca> for more information on BNP Paribas, in Canada.
|
