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

Strange FP 4 installation Problem (DB2 V 8.1)

P: n/a
I am administering a DB2 UDB 8.1 server on Solaris 9. I have experienced a
strange problem when applying FixPak 4a. Here's a short timeline of what
happened:

1) Installed DB2 UDB v8.1 for Solaris 64bit
2) created instance and sample database successfully
3) applied Fixpak 4a
4) attempted to run db2start, but all the execute permissions had been
removed from db2start.
5) Issued a db2level command and the output suggested I now had a 32-bit
version of DB2.

I'm able to back out of the FixPak successfully, but DB2 is still indicated
at 32-bits and each time I apply the FixPak, the db2binaries are disabled
from execution. Has anyone ever seen this?

TW
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Tech Witch wrote:
I am administering a DB2 UDB 8.1 server on Solaris 9. I have experienced
a
strange problem when applying FixPak 4a. Here's a short timeline of what
happened:

1) Installed DB2 UDB v8.1 for Solaris 64bit
2) created instance and sample database successfully
3) applied Fixpak 4a
4) attempted to run db2start, but all the execute permissions had been
removed from db2start.
5) Issued a db2level command and the output suggested I now had a 32-bit
version of DB2.

I'm able to back out of the FixPak successfully, but DB2 is still
indicated at 32-bits and each time I apply the FixPak, the db2binaries are
disabled
from execution. Has anyone ever seen this?


Did you update the instance (db2iupdt)?

And both 32- and 64-bit are installed at the same time, and the default
instance is 32-bit. You can use db2iupdt to convert to 64-bit, too.
Nov 12 '05 #2

P: n/a

"Darin McBride" <dm******@naboo.to.org.no.spam.for.me> wrote in message
news:mYFvd.486517$Pl.354674@pd7tw1no...
And both 32- and 64-bit are installed at the same time, and the default
instance is 32-bit. You can use db2iupdt to convert to 64-bit, too.


No, I did not try this after applying the fixpak. Do you think it will
re-enable the binary files? They currently have permissions of r-r-r.

TW
Nov 12 '05 #3

P: n/a
Tech Witch wrote:

"Darin McBride" <dm******@naboo.to.org.no.spam.for.me> wrote in message
news:mYFvd.486517$Pl.354674@pd7tw1no...
And both 32- and 64-bit are installed at the same time, and the default
instance is 32-bit. You can use db2iupdt to convert to 64-bit, too.


No, I did not try this after applying the fixpak. Do you think it will
re-enable the binary files? They currently have permissions of r-r-r.


Which binary files have this? There are files in ~/sqllib/bin and
~/sqllib/adm - none of which should have this permission, although if
it's the latter, db2iupdt will fix that. If it's ~/sqllib/bin, then
there is likely another problem with your system that may only be
solved by uninstall/reinstall.

Running db2iupdt is part of the fixpak readme instructions - please
consult the readme with your fixpak for more information on what needs
to be done during a fixpak upgrade.

Thanks,
Nov 12 '05 #4

P: n/a
"Darin McBride" <dm******@naboo.to.org.no.spam.for.me> wrote in message
news:54Kvd.512970$%k.31751@pd7tw2no...
<snip>
Running db2iupdt is part of the fixpak readme instructions - please
consult the readme with your fixpak for more information on what needs
to be done during a fixpak upgrade.


Ahh, the old, it's in the README trick. It'll get you every time! I
followed your instructions, and the README's and we're rocking with FP 4
now. Thanks!

TW
Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.