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

Connecting to Server Problem

P: n/a
Hi Guys

I have Db2 server installed on remote server. i am connecting to that
remote server by using VPN.

I want to connect that remote DB2 server instance using my local
machine DB2 development client. Bur Its gives me following error
message. I searched lots of things on net and tried on remote server
but i didnt got suceess. Can any one tell me how to set TCP\IP
connection protocol on server for particular instance. Becuase I think
While creating db2 instance they didnt specified TCP\IP connection
protocol and TCP\IP service name. So please explain me how I can set
set TCP\Ip connection protocol along with setting service on particular
TCP port.

Error Message:

SQL30081N A communication error has been detected. Communication
protocol being used: "TCP/IP". Communication API being used:
"SOCKETS". Location where the error was detected: "10.5.4.3".
Communication function detecting the error: "connect". Protocol
specific error code(s): "10061", "*", "*". SQLSTATE=08001

Explanation:

An error has been detected by the communication subsystem.

If the connection has already been established, possible causes
include the following:

o A communication subsystem error at the client node or server
node has caused the connection to go down.

o If a SOCKS server is being used, a communications subsystem
error on the SOCKS server has caused the connection to go
down.

o A network error has caused the connection to go down.

o The database agent at the server was forced off by the system
administrator.

o The database agent at the server was terminated due to an
abnormal termination of a key database manager process.

If you are trying to establish a new connection, possible causes
include the following:

o The remote database server has not been cataloged correctly
at the client.

o The database manager configuration file at the server has not
been configured with the proper communication parameters.

o The communication subsystem at the client node or server node
has not been configured correctly, or has not been started
successfully.

o The communication subsystem at the SOCKS server, if one is
being used, has not been configured correctly, or has not
been started successfully.

o The DB2COMM environment variable at the server doesn't
specify the communication protocol used by the client.

o The database manager at the server has not been started, or
has not been started successfully. One or more of the
communication protocols specified by DB2COMM may not have
been successfully started.

Refer to the token values for details. Depending on the
protocol being used and the communication function invoked, some
tokens may not be applicable. The following is the explanation
of the token values:
<protocol> The actual communication protocol being used. Valid
token values are:

o TCP/IP

o APPC

o NETBIOS

o IPX/SPX

<interface> The application programming interface used to invoke
the above communication protocol services. Valid token values
are:

o SOCKETS

o SOCKS

o CPI-C

o DLR or DD

o TLI or Connection/Bindery

o SOAP

o MQI-CLIENT

<location> This is a protocol specific ID which uniquely
identifies the node that detected the error. If the protocol
being used is:

o TCP/IP

The format of the ID is the Internet address in dot
notation.

o APPC

The format of the ID is the fully qualified LU name
(networkID.LUname).

o NETBIOS

The format of the ID is the Workstation name (nname).

o IPX/SPX

The format of the ID is the network address and node address
in hexadecimal notation (network.node).

o MQ

The format of the ID is the MQ queue name.

o SOAP

The format of the ID is the Internet address in dot
notation.

If the location information is not available at the time that
the error occurred, this token is not filled in.

<function> The name of the communication subsystem function that
returned the error code(s).

<rc1>, <rc2>, <rc3> The list of the available error codes and
subcodes that are specific to each protocol being used. Tokens
that are not applicable contain "*".

If the protocol being used is:

o TCP/IP

- If <rc1> is present and contains the global errno value from
the TCP/IP sockets function call. When using Windows Sockets,

if present, <rc1> contains the error from the TCP/IP
sockets function call returned by WSAGetLastError().

- If <rc2> is present and contains the global h_errno value
from the TCP/IP name resolution function call. When using
Windows Sockets, if present, <rc2> contains the error
from the TCP/IP database function call returned by
WSAGetLastError().

- If <rc3> is present and contains "0", it means that the
TCP/IP connection has been closed. This could be caused by one

of the following:

- The database agent at the server was forced off by the
system
administrator.

- A database agent could not be started at the server because

the maxagents database manager configuration
parameter has been exceeded. Check the administration
notification log to see if an error message has been
logged.

- The connection may have been closed by the remote server at

the TCP/IP level.

- The database agent at the server was terminated due to an

abnormal termination of a key database manager
process.

Note: When using Windows Sockets, if the <function> is
WSAStartup, and <rc1> is 0, then <rc2> contains the
Windows Sockets Specification version level requested by
DB2, and <rc3> contains the Windows Sockets
Specification version level supported by the Windows
Sockets DLL.

o APPC

<rc1> contains the return code from the CPI-C function. If
present, <rc2> contains the global errno value from the
CPI-C function call. <rc3> is not applicable.

o NETBIOS

<rc1> contains the return code from the call to NetBIOS.
<rc2> and <rc3> are not applicable.

o IPX/SPX

<rc1> contains the global t_errno value from the call to
TLI Services, or the return code from the call to NetWare

Connection or Bindery Services. If the <rc1> t_errno is
TLOOK, <rc2> contains the TLI event that has occurred. If
the <rc2> event is T_DISCONNECT, <rc3> contains the
disconnect reason code. On AIX, if the <rc1> t_errno is
TSYSERR, <rc3> contains the system errno (defined in
sys/errno.h). If <rc1> contains the error return code from a
call to AIX NetWare Connection or Bindery Services, <rc2>
contains the error generator.

o MQ

<rc1>contains the function completion code, 1 for a warning
and 2 for an error. <rc2> contains the MQ-specific error
code. <rc3> is not used for MQ.

o SOAP

<rc1> contains the return code from the SOAP communication
function. The <rc2> depends upon the value of <rc3>.
<rc2> is either:

- The TCP/IP sockect error errorno value in UNIX,
WSAGetLastError for Windows operating systems.

- A Secure Socke Layer (SSL) return code from the Global
Security Kit (GSK).

The <rc3> value "0" indicates that this is a high-level
SOAP error (not a socket or GSKit error). the <rc3> value
"1" indicates that this was a socket error. the
<rc3> value "2" indicates that this was a GSKit
error.

See the Communications Errors appendix of the Message Reference
for more information on specific communication error codes.

User Response:

If the connection has already been established, check if:

1. The database agent at the server has been forced off.

2. The database manager at the server has abnormally
terminated.

3. A communication subsystem or network error has occurred. See
the Message Reference for more information on specific
communication error codes.

If you are trying to establish a new connection, check if:

1. The remote database server is cataloged properly on the
client node.

2. The database manager configuration file at the server is
configured with the proper communication related parameters.
If the database manager configuration parameters have been
updated at the server, ensure that you stop and then re-start
the database manager, for the changes to take effect.

3. The communication subsystems on both client and server nodes
are configured and started up properly.

4. The DB2COMM environment variable at the server specifies the
communication protocol used by the client.

5. The database manager at the server is successfully started.
Start database manager processing at the server should have
returned SQL1063, and not SQL5043. If SQL5043 is returned,
check the administration notification log for more
information.

6. A communication subsystem or network error has occurred.

If the problem persists, consult with your network administrator
and/or communication expert to determine the cause of the problem
using the set of tokens provided.

sqlcode : -30081

sqlstate : 08001

Thanks
Suresh

Jun 7 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.