Thank you for the response and links.  The symptoms sound exactly like what
I am seeing but the dates don't correlate . The 7.1.7.300 package I
upgraded the server to (from 7.1.7.000) is dated 06/20/2017 while the
SP_8.1.1_LIN86_SER-STG_ML.bin file I am using to install 8.1.1 is dated
06/30/2017 - unless the dates have to be much later than 06/30/2017 (*For
example, the following upgrade procedures can fail:  -  3: Upgrade from
patch release 7.1.7.200 to V8.1.1*).

I am re-downloading the 8.1.1 install package to see if it makes a
difference, since the docs say "*If 7.1.7.100 is installed, you can obtain
a V8.1.1 installation package from Passport Advantage and directly upgrade
the server to V8.1.1 without uninstalling 7.1.7.100"*

If not, I will go the uninstall route.  Again, thanks.

On Wed, Jul 26, 2017 at 6:00 AM, Giacomo Testa <giacomo.testa AT gmail DOT com>
wrote:

> Hi,
>
> There seems to be a problem upgrading a Spectrum Protect server from
> 7.1.7.x to 8.1.x, if 8.1.x was released earlier than 7.1.7.x.
>
> http://www-01.ibm.com/support/docview.wss?uid=swg1IT20210
> http://www-01.ibm.com/support/docview.wss?uid=swg22002297
>
> Delivery (Release) Dates:
> https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/
> Tivoli+Storage+Manager/page/TSM+Schedule+for+Fix-Packs
>
>
> Giacomo Testa
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Zoltan Forray
> Sent: Tuesday, July 25, 2017 20:11
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Upgrading Linux server from 7.1.7.300 to 8.1.1 - fail
>
> Is there any reason I can't upgrade from 7.1.7.x to 8.1.1 using the
> Passport download package?  Do I have to go to 8.1.0 first?
>
> I am working on a test server - RHEL7.  It was 7.1.7.000 - installed
> 7.1.7.300 - no problem.
>
> Extracted the 8.1.1 package from Passport so it includes the license file
> but installing it as an "Update" fails trying to uninstall DB2, I think.
> Been Googling anything on install/upgrade and there isn't anything special
> for me to do as far as I know/can find, other than *./install.sh -c*.
> Don't have any issues with disk space or ulimits. The ever popular "if you
> have a failure - check these logs and fix the problem" is pretty useless.
> This is all I can find:
>
> ERROR: The deinstallation process cannot continue while there are DB2
> instances related to the current DB2 copy. If you need to move up or down a
> level from this DB2 level, use the installFixPack command from the DB2
> image for the level you desire to move to, which will update this copy. If
> you are only trying to uninstall this DB2 copy, you must either drop the
> related instance(s) "tsminst1" first, or you can update the instances to
> another DB2 copy which is at the same version as this DB2 copy, then
> restart the db2_deinstall command.
>
> Preparing the system :.......Failure
>
>
> --
> *Zoltan Forray*
> Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon
> Monitor Administrator VMware Administrator 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
>



--
*Zoltan Forray*
Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator
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