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

Linux DB2 Client Hangs when Connecting to Remote Host

P: 1
Hello,

I'm having a problem connecting to DB2 on a remote iSeries host from a Linux server, both of which reside on my company's internal network. I'm using the IBM Linux Client V9.1. When I try to connect to the remote host using a simple connect statement, DB2 hangs.

The connection statement I'm using (I've obviously obscured the parameter names):

Expand|Select|Wrap|Line Numbers
  1. $ ./db2 connect to DATABASENAME user USERNAME using PASSWORD;
  2.  
The user name and password that I am using are correct. I can login to the iSeries directly using the iSeries Navigator utility. There is also a WebSphere server on the network that is able to access the same iSeries host remotely using the same login and password via JDBC.

DB2DIAG.LOG does not show any errors when the application hangs when attempting to connect to this port (8471) or other open ports (8470, 8472, etc.). When I attempt to connect to a closed port (50000), DB2 connect returns an error and the error does show up in DB2DIAG.LOG (DIA3202C The TCP/IP call "connect" returned an errno="111".).

Here are the commands I typed to create the db directory and node directory listings:

Expand|Select|Wrap|Line Numbers
  1. $ ./db2 catalog db DATABASENAME at node xxxx
  2. $ ./db2 catalog tcpip4 node xxxx remote 192.168.0.233 server 8471
  3.  
Here is what the db directory and node directory listings look like:

Expand|Select|Wrap|Line Numbers
  1. $ ./db2 list db directory
  2.  
  3.  System Database Directory
  4.  
  5.  Number of entries in the directory = 1
  6.  
  7. Database 1 entry:
  8.  
  9.  Database alias                       = DATABASENAME
  10.  Database name                          = DATABASENAME
  11.  Node name                            = XXXX
  12.  Database release level               = b.00
  13.  Comment                              =
  14.  Directory entry type                 = Remote
  15.  Catalog database partition number    = -1
  16.  Alternate server hostname            =
  17.  Alternate server port number         =
  18.  
  19.  
  20. $ ./db2 list node directory
  21.  
  22.  Node Directory
  23.  
  24.  Number of entries in the directory = 1
  25.  
  26. Node 1 entry:
  27.  
  28.  Node name                      = XXXX
  29.  Comment                        =
  30.  Directory entry type           = LOCAL
  31.  Protocol                       = TCPIP4
  32.  Hostname                       = 192.168.0.233
  33.  Service name                   = 8471
  34.  
  35.  
Any ideas of what could be wrong here? Thanks in advance!
Feb 1 '08 #1
Share this Question
Share on Google+
1 Reply


sakumar9
Expert 100+
P: 127
Actually DB2 might not have hanged but was trying for the connection. If there is anything wrong with the configuration, then DB2 will keep on retrying untill Number Of Retries exceeds certain number.

1. Ensure that you are using correct IP address. (Looks find from the details that you have sent)
2. Check the port numbers; (DBM cfg parameter)

3. set DB2COMM=tcpip


Let me know if you still have problems or if the solution was something else.

Regards
-- Sanjay
Feb 27 '08 #2

Post your reply

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