mairhtin o'feannag wrote:
Hello,
I'm having problems connecting to my new v9 db box. The pertinent
information is below:
DB2_db2inst1 60000/tcp
DB2_db2inst1_1 60001/tcp
DB2_db2inst1_2 60002/tcp
DB2_db2inst1_EN D 60003/tcp
TCP/IP Service name (SVCENAME) = DB2_db2inst1
[db2inst1@mairht in db2dump]$ db2set
AUTOSTART=yes
DB2COMM=tcpip
Stupid question, maybe, but you did restart the DB2 server after setting the
DB2COMM registry variable?
SQL30081N A communication error has been detected. Communication
protocol
being used: "TCP/IP". Communication API being used: "SOCKETS".
Location
where the error was detected: "67.170.223.55" . Communication
function
detecting the error: "connect". Protocol specific error code(s):
"10061", "*",
"*". SQLSTATE=08001
db2 catalog tcpip node homesvr remote 67.170.223.55 server DB2
_db2inst1
db2 catalog db sample as sample2 at node homesvr
The V9 manual shows the following explanation for SQL30081.
---------------------------------------------------------------------------
If <protocol= TCP/IP, <function= connect, <rc1=
ECONNREFUSED/WSAECONNREFUSED , AIX (79), Windows (10061), linux (111), SUN
(146), HP (239), the attempt to connect was rejected. Possible causes:
* The remote database server has not been cataloged correctly at the
client. In a client-gateway-server scenario, ensure the host entries are
cataloged correctly on the gateway. See the Quick Beginnings guide for
assistance.
* The database manager configuration file at the server has not been
configured properly with the proper communication parameters. Check that
svcename has been configured properly with the TCP/IP service name or port
number and that the port number is unique. If database manager
configuration parameters have been updated at the server, the database
manager must be stopped and re-started for the changes to take effect.
There might be a mismatch between the TCP/IP service name or port number
specified on the server and on the client. Ensure the service name maps to
the correct port number by checking the services file. You can check this
by reading the services file or checking the output of "netstat -a".
* The DB2COMM environment variable at the server does not specify the
communication protocol used by the client. Check that TCPIP has been
specified. Issue db2set to see what has already been set. Issue db2set
DB2COMM = TCPIP to set the value.
* The database manager at the server has not been started, or has not
been started successfully, or has gone down. The server should have
returned SQL1063, and not SQL5043. If you set the database manager
configuration parameter, diaglevel, to 4 using, db2 update dbm cfg using
diaglevel 4, prior to issuing db2start, the administration notification log
will provide detailed information on which protocols were started
successfully. Check the administration notification log.
* The server might be too busy to handle the volume of incoming
connections at this time.
* Network failure, contact your network administrator. You can try a
test using the protocol tester, pctt, to verify this is not a DB2 problem.
---------------------------------------------------------------------------
--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany
