db2setup on RHEL AS V4 doesn't work

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Laurence - 22 Jun 2006 00:16 GMT

Hi there,

I have searched a couple of keywords for db2setup issue, but find out
nothing.

I'm tring to install DB2_ESE_8.2_LNX on RHEL AS 4 by using db2setup.
The message shown -

db2setup is preparing the DB2 Setup Wizard which will
guide you through the program setup process. Please
wait.

after invoked the ./db2setup, then nothing happened.

Is there any suggestion? I'll be very appreciate.

Thanks in advance

Reply to this Message

Mark A - 22 Jun 2006 00:22 GMT

> Hi there,
>
[quoted text clipped - 13 lines]
>
> Thanks in advance

db2setup launches a GUI application. You may to export the display in your
telnet session to get the GUI to work.

Reply to this Message

Laurence - 22 Jun 2006 01:52 GMT

Thanks for your reply.

On RHEL AS 4 (192.168.10.101), I did:

xhost -
xhost +192.168.10.111

then, on Windows XP (192.168.10.111), I did:

putty 192.168.10.101
export DISPLAY=192.168.10.111:0.0

and tried

gnome-terminal &

the gnome-terminal appeared through Xmanager on Windows XP

But as I executed db2setup the message showed

db2setup is preparing the DB2 Setup Wizard which will
guide you through the program setup process. Please
wait.

then nothing happened.

Any more suggestions?

Reply to this Message

Laurence - 22 Jun 2006 07:28 GMT

I've solved the db2setup issue.

I have a tar file of DB2 UDB ESE V8.2, and extracted that by Linux tar
command rather than Windows tools such as 7-zip.

Then, the db2setup program is able to work in the event.

Reply to this Message

Darin McBride - 22 Jun 2006 00:22 GMT

> Hi there,
>
[quoted text clipped - 11 lines]
>
> Is there any suggestion? I'll be very appreciate.

I assume you started by waiting. ;-) I also assume you waited for long
enough to decide that something bad was happening - or, at least, nothing
good.

Can you check /tmp/db2setup.err to see if it has any contents that may help?
If that's not helpful, the next thing to do is retry, but add "-d" to the
command line, e.g., "./db2setup -d". Once you've waited a sufficient
amount of time, kill it, and then send me /tmp/db2setup.trc* (there should
be two files).

Also if the err file is not helpful, if you have a support contract, you'll
be best off opening a PMR with IBM - that will get you the priority service
that you may need (and have paid for ;->). As it is, IBM can't guarantee
my service in a newsgroup ;-)

Thanks,

Reply to this Message