Install Fixpak 8.1 11 from 8.1 7 connection woes

[mandible]

Hello I recently upgraded my db2 to 8.1 fixpak 11 and have been having
trouble setting up alias connections to the newly upgraded database. I
believe I had this problem before and can't seem to find the commands
to bring the new database forward for connection purposes was wondering
if anyone can help me.

I think it was just a couple commands
Thanks.

[Serge Rielau]

mandible wrote:

Hello I recently upgraded my db2 to 8.1 fixpak 11 and have been having
trouble setting up alias connections to the newly upgraded database. I
believe I had this problem before and can't seem to find the commands
to bring the new database forward for connection purposes was wondering
if anyone can help me.

I think it was just a couple commands

Could it be you are looking for the CATALOG command?

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

[mandible]

maybe I'll give that a check

[mandible]

This is the error I get when I try and setup a Alias connection from my
box to the server using the configuration assistant.

CLI connection failed.

SQL30081N A communication error has been detected. Communication
protocol being used: "TCP/IP". Communication API being used:
"SOCKETS". Location where the error was detected: "192.168.93.3".
Communication function detecting the error: "connect". Protocol
specific error code(s): "10061", "*", "*". SQLSTATE=08001
I have successfully patched all my other db2 systems to fixpak 11 but
didn't do them all at the same time and I remember there being
something I had to do before I could access them through outside
applications, but they are usable from local server applications.

[Larry]

mandible wrote:

This is the error I get when I try and setup a Alias connection from my
box to the server using the configuration assistant.

CLI connection failed.

SQL30081N A communication error has been detected. Communication
protocol being used: "TCP/IP". Communication API being used:
"SOCKETS". Location where the error was detected: "192.168.93.3".
Communication function detecting the error: "connect". Protocol
specific error code(s): "10061", "*", "*". SQLSTATE=08001
I have successfully patched all my other db2 systems to fixpak 11 but
didn't do them all at the same time and I remember there being
something I had to do before I could access them through outside
applications, but they are usable from local server applications.

What happens if you try to connect to an existing database from the same
box to the same box? 10061 is a TCP/IP comm error that indicates
connection refused by the server.

Larry Edelstein

[mandible]

we have a websphere application on the same box as the database and it
works fine connecting to the db. if that's what you meant.

[Larry]

mandible wrote:

we have a websphere application on the same box as the database and it
works fine connecting to the db. if that's what you meant.

No ... not from an application on the same box as the database ... can
you connect to the database from an application or command prompt on the
same client machine that you are getting the failure from?

Larry E.

[mandible]

Larry wrote:

mandible wrote:

we have a websphere application on the same box as the database and it
works fine connecting to the db. if that's what you meant.

No ... not from an application on the same box as the database ... can
you connect to the database from an application or command prompt on the
same client machine that you are getting the failure from?

Larry E.

Okay I believe you're asking if I can connect from my client machine to
this database directly and the answer is no.
To do work on it I usually ssh into the box and do a lot of my work via
command prompt. I was trying to set up the alias in the first place so
that I could get a connection with the db2 tools.

[Larry]

mandible wrote:

Larry wrote:

mandible wrote:

we have a websphere application on the same box as the database and it
works fine connecting to the db. if that's what you meant.

No ... not from an application on the same box as the database ... can
you connect to the database from an application or command prompt on the
same client machine that you are getting the failure from?

Larry E.

Okay I believe you're asking if I can connect from my client machine to
this database directly and the answer is no.
To do work on it I usually ssh into the box and do a lot of my work via
command prompt. I was trying to set up the alias in the first place so
that I could get a connection with the db2 tools.

Recommend that you use the Client Configuration Assistant (now called
the "Configuration Assistant") to set up the communications from your
client machine. This would be the first step. Then, can set up an alias
if you still wish to (alias in DB2 is merely an "alternate name" and is
not required for communications).

Larry E.

[mandible]

I used Configuration Assistant from the get go if you read higher