Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / June 2006

Tip: Looking for answers? Try searching our database.

Install Fixpak 8.1 11 from 8.1 7 connection woes

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
mandible - 29 May 2006 19:46 GMT
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 - 29 May 2006 21:23 GMT
> 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
[quoted text clipped - 3 lines]
>
> I think it was just a couple commands
Could it be you are looking for the CATALOG command?

Signature

Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

mandible - 30 May 2006 13:11 GMT
maybe I'll give that a check
mandible - 30 May 2006 13:21 GMT
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 - 30 May 2006 13:55 GMT
> This is the error I get when I try and setup a Alias connection from my
> box to the server using the configuration assistant.
[quoted text clipped - 11 lines]
> 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 - 30 May 2006 23:30 GMT
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 - 31 May 2006 00:25 GMT
> 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 - 31 May 2006 13:11 GMT
> > 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.
[quoted text clipped - 4 lines]
>
> 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 - 31 May 2006 18:53 GMT
>>>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.
[quoted text clipped - 10 lines]
> 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 - 13 Jun 2006 16:21 GMT
I used Configuration Assistant from the get go if you read higher
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.