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

DB2 Database Catalog

P: 3
Hi,

I am new to DB2, i want to catalog DB2 databases in Control Center(Windows) but databases exist in AIX server

I catalog the database by following commands in CLP (windows)

=>catalog tcpip node <node name> remote <server name> server <port no>

=>catalog database <db name> at node <node name>

i am getting the error while try to connect database in Control Center

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: "gethostbyname". Protocol specific error code(s): "*", "11004", "*". SQLSTATE=08001

How can i solve this problem
Dec 18 '07 #1
Share this Question
Share on Google+
2 Replies


sakumar9
Expert 100+
P: 127
1. Check if you are using the correct port number and IP address. This posr number should be updated in dbm cfg parameter.
2. DB2COMM registry variable should be set to tcpip. (You can use db2set command to check its value, or use db2set to set this value)
3. Make sure that the server database is started.

Regards
-- Sanjay
Feb 21 '08 #2

docdiesel
Expert 100+
P: 297
1. Check if you are using the correct port number and IP address. This posr number should be updated in dbm cfg parameter.
2. DB2COMM registry variable should be set to tcpip. (You can use db2set command to check its value, or use db2set to set this value)
3. Make sure that the server database is started.

Regards
-- Sanjay
Agreed. Usually it's point 2 which is why you get no tcp/ip connection. (The catalog statements seem right so far.) Check if your instance is up and running on your AIX server, with the db2 variable DB2COMM set (just run db2set to list them), and check if it's listening on the given tcp port:

Expand|Select|Wrap|Line Numbers
  1. #On AIX server, check if someone's listening on port x:
  2. netstat -lntp
  3.  
  4. # check what port DB2 should be using:
  5. db2 get dbm cfg | grep SVCENAME
  6.  
  7. # if it's not numeric, check the number in /etc/services:
  8. grep db2c_db2svc01 /etc/services
  9.  
  10. #Or in Windows client, check if you can get a tcp connection
  11. telnet server_ip server_port
  12.  
Regards,

Bernd
Feb 22 '08 #3

Post your reply

Sign in to post your reply or Sign up for a free account.