By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,610 Members | 2,310 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,610 IT Pros & Developers. It's quick & easy.

Problem Upgrading to FP9a Using Alternate Fixpack

P: n/a
Trying to upgrade alternate FP9 to alternate FP9a on Red Hat Linux. After
running the following command:

../installAltFixPak -y

it says it was successful, but no new directory is created in /opt/IBM/db2

Assuming that maybe fixpack 9a updates the existing /opt/IBM/db2/V8.FP9
directory, I ran db2iupdt on the instance (using root), but db2level still
shows the signature for fixpack 9 (not 9a). "DB2 v8.1.0.88", "s050422"

But looking at the file dates on /opt/IBM/db2/V8.FP9/bin it does not appear
any on them got updated even though the install script said it ran
successfully.

I had the same problem with alternate fixpack 6 and 6a. Has anyone
successfully updated to "a" alternate fixpacks from the same level (without
"a") on Linux?

Also, suing the brand new IBM webpage for downloading DB2 fixpacks, it
appears to me to be impossible to download alternate fixpacks unless one
already knows where the FTP site is.
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Mark A wrote:
Trying to upgrade alternate FP9 to alternate FP9a on Red Hat Linux. After
running the following command:

./installAltFixPak -y

it says it was successful, but no new directory is created in /opt/IBM/db2

Assuming that maybe fixpack 9a updates the existing /opt/IBM/db2/V8.FP9
directory, I ran db2iupdt on the instance (using root), but db2level still
shows the signature for fixpack 9 (not 9a). "DB2 v8.1.0.88", "s050422"

But looking at the file dates on /opt/IBM/db2/V8.FP9/bin it does not appear
any on them got updated even though the install script said it ran
successfully.

I had the same problem with alternate fixpack 6 and 6a. Has anyone
successfully updated to "a" alternate fixpacks from the same level (without
"a") on Linux?

Also, suing the brand new IBM webpage for downloading DB2 fixpacks, it
appears to me to be impossible to download alternate fixpacks unless one
already knows where the FTP site is.

Did you uninstall the alternate fixpack. I'm told you can't just install
on top for the AFP.

Cheers
Serge

--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab
Nov 12 '05 #2

P: n/a
Mark A wrote:
Trying to upgrade alternate FP9 to alternate FP9a on Red Hat Linux. After
running the following command:


Because they're both FP9, they won't coexist. You need to uninstall
the existing FP9 alternate fixpack, and then install the new copy.
Nov 12 '05 #3

P: n/a
"Darin McBride" <dm******@naboo.to.org.no.spam.for.me> wrote in message
news:UoUve.1814178$6l.565789@pd7tw2no...
Mark A wrote:
Trying to upgrade alternate FP9 to alternate FP9a on Red Hat Linux. After
running the following command:


Because they're both FP9, they won't coexist. You need to uninstall
the existing FP9 alternate fixpack, and then install the new copy.


No mention of that in the readme file installation instructions.

Anyone from IBM know why it is impossible to download alternate fixpacks
from the new download website?

Nov 12 '05 #4

P: n/a
"Serge Rielau" <sr*****@ca.ibm.com> wrote in message
news:3i************@individual.net...
Did you uninstall the alternate fixpack. I'm told you can't just install
on top for the AFP.

Cheers
Serge

--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab


For normal alternate fixpacks (not "a" or "b", etc) you install the
alternate fixpack and it installs the code for each fixpack in a separate
directory on /opt/IBM/db2 (for Linux). Then you update each instance to
point to the alternate fixpack you want, which updates the db2 profile and
home directories to point to the correct binaries.

I have done this many time before, but it does not work when installing 9a
if 9 already installed.
Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.