SQL1024N. A database connection does not exists. sqlstate08003

[adititiwari]

i have made a federated server wherein i have cataloged a remote iseries database using port 456. Later I created a wrapper but when was creating a server it gave me an error: SQL1024N. A database connection does not exists. sqlstate08003. I tried establishing a connection to the same database it ended with an 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: "192.168.100.60 ". Communication function detecting the error: "connect". Protocol specific error code(s): "79", "*", "*". SQLSTATE=08001

I tried telnet but the connection was not established, netstat command also shows the request in the LISTEN mode, traceroute command was also successful. I can also successfully ping the remote server.

[Amarnath Reddy N]

error code(s) "79"means :
The connection has been refused. If you are trying to connect to the database, check that the database manager and TCP/IP protocol support at the server have been started successfully.

If using SOCKS protocol support, also ensure that TCP/IP protocol support at the SOCKS server has been started successfully.

many reasons for this error :

* 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".
* A firewall at the remote database server has prevented the connection from being established. Verify that the firewall is properly configured to accept connection requests from the client.
* 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.

[adititiwari]

Thanx a lot! Actually i added the p400 server as a host in my AIX server.