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

after ip address changed, get communication error

P: n/a
i have catalog a remote database on my local db2 server, but now the
remote database server with same machine name but the ip address
changed, so i remove the old one, and try to catalog again under
control center --- all cataloged systems, then i use discover search
button, find the sysetm name, but gives me error

SQL30081N A communication error has been detected. Communication
protocol being used: "TCP/IP". Communication API being used:
"SOCKETS". Location where the error was detected: "". Communication
function detecting the error: "connect". Protocol specific error
code(s): "10061", "*", "*". SQLSTATE=08001

looks like it still think it uses the old ip address, but the host
name is now being used by another machine's url, the old ip address
has been applied to this machine, but no db2 on this machine, so how
can i let db2 catalog the right ip address with right server? thanks
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
There's a cache of the database directory kept by both the client and
server...you normally need to terminate your application to pick up the
new settings.

xixi wrote:
i have catalog a remote database on my local db2 server, but now the
remote database server with same machine name but the ip address
changed, so i remove the old one, and try to catalog again under
control center --- all cataloged systems, then i use discover search
button, find the sysetm name, but gives me error

SQL30081N A communication error has been detected. Communication
protocol being used: "TCP/IP". Communication API being used:
"SOCKETS". Location where the error was detected: "". Communication
function detecting the error: "connect". Protocol specific error
code(s): "10061", "*", "*". SQLSTATE=08001

looks like it still think it uses the old ip address, but the host
name is now being used by another machine's url, the old ip address
has been applied to this machine, but no db2 on this machine, so how
can i let db2 catalog the right ip address with right server? thanks

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.