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 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.