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
- $ ./db2 connect to DATABASENAME user USERNAME using PASSWORD;
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
- $ ./db2 catalog db DATABASENAME at node xxxx
- $ ./db2 catalog tcpip4 node xxxx remote 192.168.0.233 server 8471
Expand|Select|Wrap|Line Numbers
- $ ./db2 list db directory
- System Database Directory
- Number of entries in the directory = 1
- Database 1 entry:
- Database alias = DATABASENAME
- Database name = DATABASENAME
- Node name = XXXX
- Database release level = b.00
- Comment =
- Directory entry type = Remote
- Catalog database partition number = -1
- Alternate server hostname =
- Alternate server port number =
- $ ./db2 list node directory
- Node Directory
- Number of entries in the directory = 1
- Node 1 entry:
- Node name = XXXX
- Comment =
- Directory entry type = LOCAL
- Protocol = TCPIP4
- Hostname = 192.168.0.233
- Service name = 8471