473,583 Members | 2,751 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

SQL30081N

Hi,
I have a remote DB2 database on AIX and I am accessing ti using a
windows client .i was using control center on windows to add the remote
system under it and I gave all the node names and pressed discover and
it gives me the following 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: "172.21.2.1 55".
Communication function detecting the error: "recv". Protocol specific
error code(s): "*", "*", "0". 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:
<protocolThe actual communication protocol being used. Valid
token values are:

o TCP/IP

o APPC

o NETBIOS

o IPX/SPX

<interfaceThe 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

<locationThis 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.LUna me).

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.

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

<rc1>, <rc2>, <rc3The 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 <rc1is present and contains the global errno value from
the TCP/IP sockets function call. When using Windows Sockets,

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

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

- If <rc3is 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 <functionis
WSAStartup, and <rc1is 0, then <rc2contains 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

<rc1contains the return code from the CPI-C function. If
present, <rc2contains the global errno value from the
CPI-C function call. <rc3is not applicable.

o NETBIOS

<rc1contains the return code from the call to NetBIOS.
<rc2and <rc3are not applicable.

o IPX/SPX

<rc1contains 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 <rc1t_errno is
TLOOK, <rc2contains the TLI event that has occurred. If
the <rc2event is T_DISCONNECT, <rc3contains the
disconnect reason code. On AIX, if the <rc1t_errno is
TSYSERR, <rc3contains the system errno (defined in
sys/errno.h). If <rc1contains 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. <rc2contains the MQ-specific error
code. <rc3is not used for MQ.

o SOAP

<rc1contains the return code from the SOAP communication
function. The <rc2depends upon the value of <rc3>.
<rc2is 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 <rc3value "0" indicates that this is a high-level
SOAP error (not a socket or GSKit error). the <rc3value
"1" indicates that this was a socket error. the
<rc3value "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

*************** *************** *************** *************** *************** *************** *************** *

The FEDERATED parameter at server is set to YES and DB2COMM is set to
tcp/ip
Appreciate your help, thanks

Jul 6 '06 #1
4 7477
Try this

>From your machine start/run/cmd
db2cmd---it will open another window
In that window do this

db2 "catalog tcpip node xxxx remote <hostname of the db serverremote
<port number>"
db2 "catalog database at node xxxx"

After this is done...try this

db2 connect to <dbuser <useridpasswo rd <passwd>

Now use CONTROL CENTER....

cheers...
Shashi Mannepalli

Asphalt Blazer wrote:
Hi,
I have a remote DB2 database on AIX and I am accessing ti using a
windows client .i was using control center on windows to add the remote
system under it and I gave all the node names and pressed discover and
it gives me the following 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: "172.21.2.1 55".
Communication function detecting the error: "recv". Protocol specific
error code(s): "*", "*", "0". 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:
<protocolThe actual communication protocol being used. Valid
token values are:

o TCP/IP

o APPC

o NETBIOS

o IPX/SPX

<interfaceThe 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

<locationThis 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.LUna me).

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.

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

<rc1>, <rc2>, <rc3The 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 <rc1is present and contains the global errno value from
the TCP/IP sockets function call. When using Windows Sockets,

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

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

- If <rc3is 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 <functionis
WSAStartup, and <rc1is 0, then <rc2contains 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

<rc1contains the return code from the CPI-C function. If
present, <rc2contains the global errno value from the
CPI-C function call. <rc3is not applicable.

o NETBIOS

<rc1contains the return code from the call to NetBIOS.
<rc2and <rc3are not applicable.

o IPX/SPX

<rc1contains 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 <rc1t_errno is
TLOOK, <rc2contains the TLI event that has occurred. If
the <rc2event is T_DISCONNECT, <rc3contains the
disconnect reason code. On AIX, if the <rc1t_errno is
TSYSERR, <rc3contains the system errno (defined in
sys/errno.h). If <rc1contains 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. <rc2contains the MQ-specific error
code. <rc3is not used for MQ.

o SOAP

<rc1contains the return code from the SOAP communication
function. The <rc2depends upon the value of <rc3>.
<rc2is 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 <rc3value "0" indicates that this is a high-level
SOAP error (not a socket or GSKit error). the <rc3value
"1" indicates that this was a socket error. the
<rc3value "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

*************** *************** *************** *************** *************** *************** *************** *

The FEDERATED parameter at server is set to YES and DB2COMM is set to
tcp/ip
Appreciate your help, thanks
Jul 6 '06 #2
I am able to do this on the unix machine, it works there. for example,
i cataloged the above said server in a test machine and it worked. But
when I am using the IBM DB2 CC client on windows the dicover is not
dicovering the remote machine and it gives me the previously mentioned
error.

Shashi Mannepalli wrote:
Try this

From your machine start/run/cmd
db2cmd---it will open another window
In that window do this

db2 "catalog tcpip node xxxx remote <hostname of the db serverremote
<port number>"
db2 "catalog database at node xxxx"

After this is done...try this

db2 connect to <dbuser <useridpasswo rd <passwd>

Now use CONTROL CENTER....

cheers...
Shashi Mannepalli

Asphalt Blazer wrote:
Hi,
I have a remote DB2 database on AIX and I am accessing ti using a
windows client .i was using control center on windows to add the remote
system under it and I gave all the node names and pressed discover and
it gives me the following 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: "172.21.2.1 55".
Communication function detecting the error: "recv". Protocol specific
error code(s): "*", "*", "0". 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:
<protocolThe actual communication protocol being used. Valid
token values are:

o TCP/IP

o APPC

o NETBIOS

o IPX/SPX

<interfaceThe 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

<locationThis 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.LUna me).

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.

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

<rc1>, <rc2>, <rc3The 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 <rc1is present and contains the global errno value from
the TCP/IP sockets function call. When using Windows Sockets,

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

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

- If <rc3is 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 <functionis
WSAStartup, and <rc1is 0, then <rc2contains 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

<rc1contains the return code from the CPI-C function. If
present, <rc2contains the global errno value from the
CPI-C function call. <rc3is not applicable.

o NETBIOS

<rc1contains the return code from the call to NetBIOS.
<rc2and <rc3are not applicable.

o IPX/SPX

<rc1contains 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 <rc1t_errno is
TLOOK, <rc2contains the TLI event that has occurred. If
the <rc2event is T_DISCONNECT, <rc3contains the
disconnect reason code. On AIX, if the <rc1t_errno is
TSYSERR, <rc3contains the system errno (defined in
sys/errno.h). If <rc1contains 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. <rc2contains the MQ-specific error
code. <rc3is not used for MQ.

o SOAP

<rc1contains the return code from the SOAP communication
function. The <rc2depends upon the value of <rc3>.
<rc2is 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 <rc3value "0" indicates that this is a high-level
SOAP error (not a socket or GSKit error). the <rc3value
"1" indicates that this was a socket error. the
<rc3value "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

*************** *************** *************** *************** *************** *************** *************** *

The FEDERATED parameter at server is set to YES and DB2COMM is set to
tcp/ip
Appreciate your help, thanks
Jul 6 '06 #3
Shashi
Damn me..I got what you said. My apologies. Thanks for your
help, I appreciate it, thanks
Asphalt Blazer wrote:
I am able to do this on the unix machine, it works there. for example,
i cataloged the above said server in a test machine and it worked. But
when I am using the IBM DB2 CC client on windows the dicover is not
dicovering the remote machine and it gives me the previously mentioned
error.

Shashi Mannepalli wrote:
Try this

>From your machine start/run/cmd
db2cmd---it will open another window
In that window do this

db2 "catalog tcpip node xxxx remote <hostname of the db serverremote
<port number>"
db2 "catalog database at node xxxx"

After this is done...try this

db2 connect to <dbuser <useridpasswo rd <passwd>

Now use CONTROL CENTER....

cheers...
Shashi Mannepalli

Asphalt Blazer wrote:
Hi,
I have a remote DB2 database on AIX and I am accessing ti using a
windows client .i was using control center on windows to add the remote
system under it and I gave all the node names and pressed discover and
it gives me the following 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: "172.21.2.1 55".
Communication function detecting the error: "recv". Protocol specific
error code(s): "*", "*", "0". 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:
>
>
<protocolThe actual communication protocol being used. Valid
token values are:
>
o TCP/IP
>
o APPC
>
o NETBIOS
>
o IPX/SPX
>
>
>
<interfaceThe 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
>
>
>
<locationThis 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.LUna me).
>
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.
>
<functionThe name of the communication subsystem function that
returned the error code(s).
>
<rc1>, <rc2>, <rc3The 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 <rc1is present and contains the global errno value from
the TCP/IP sockets function call. When using Windows Sockets,
>
if present, <rc1contains the error from the TCP/IP
sockets function call returned by WSAGetLastError ().
>
- If <rc2is present and contains the global h_errno value
from the TCP/IP name resolution function call. When using
Windows Sockets, if present, <rc2contains the error
from the TCP/IP database function call returned by
WSAGetLastError ().
>
- If <rc3is 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 <functionis
WSAStartup, and <rc1is 0, then <rc2contains 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
>
<rc1contains the return code from the CPI-C function. If
present, <rc2contains the global errno value from the
CPI-C function call. <rc3is not applicable.
>
o NETBIOS
>
<rc1contains the return code from the call to NetBIOS.
<rc2and <rc3are not applicable.
>
o IPX/SPX
>
<rc1contains 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 <rc1t_errno is
TLOOK, <rc2contains the TLI event that has occurred. If
the <rc2event is T_DISCONNECT, <rc3contains the
disconnect reason code. On AIX, if the <rc1t_errno is
TSYSERR, <rc3contains the system errno (defined in
sys/errno.h). If <rc1contains 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. <rc2contains the MQ-specific error
code. <rc3is not used for MQ.
>
o SOAP
>
<rc1contains the return code from the SOAP communication
function. The <rc2depends upon the value of <rc3>.
<rc2is 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 <rc3value "0" indicates that this is a high-level
SOAP error (not a socket or GSKit error). the <rc3value
"1" indicates that this was a socket error. the
<rc3value "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
>
*************** *************** *************** *************** *************** *************** *************** *
>
The FEDERATED parameter at server is set to YES and DB2COMM is set to
tcp/ip
Appreciate your help, thanks
Jul 6 '06 #4
it worked. But can anybod ytell me why the DISCOVER ing direclty from
control cneter would not work?
Asphalt Blazer wrote:
Shashi
Damn me..I got what you said. My apologies. Thanks for your
help, I appreciate it, thanks
Asphalt Blazer wrote:
I am able to do this on the unix machine, it works there. for example,
i cataloged the above said server in a test machine and it worked. But
when I am using the IBM DB2 CC client on windows the dicover is not
dicovering the remote machine and it gives me the previously mentioned
error.

Shashi Mannepalli wrote:
Try this
>
>
From your machine start/run/cmd
db2cmd---it will open another window
In that window do this
>
db2 "catalog tcpip node xxxx remote <hostname of the db serverremote
<port number>"
db2 "catalog database at node xxxx"
>
After this is done...try this
>
db2 connect to <dbuser <useridpasswo rd <passwd>
>
Now use CONTROL CENTER....
>
cheers...
Shashi Mannepalli
>
Asphalt Blazer wrote:
Hi,
I have a remote DB2 database on AIX and I am accessing ti using a
windows client .i was using control center on windows to add the remote
system under it and I gave all the node names and pressed discover and
it gives me the following 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: "172.21.2.1 55".
Communication function detecting the error: "recv". Protocol specific
error code(s): "*", "*", "0". 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:


<protocolThe actual communication protocol being used. Valid
token values are:

o TCP/IP

o APPC

o NETBIOS

o IPX/SPX



<interfaceThe 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



<locationThis 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.LUna me).

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.

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

<rc1>, <rc2>, <rc3The 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 <rc1is present and contains the global errno value from
the TCP/IP sockets function call. When using Windows Sockets,

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

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

- If <rc3is 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 <functionis
WSAStartup, and <rc1is 0, then <rc2contains 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

<rc1contains the return code from the CPI-C function. If
present, <rc2contains the global errno value from the
CPI-C function call. <rc3is not applicable.

o NETBIOS

<rc1contains the return code from the call to NetBIOS.
<rc2and <rc3are not applicable.

o IPX/SPX

<rc1contains 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 <rc1t_errno is
TLOOK, <rc2contains the TLI event that has occurred. If
the <rc2event is T_DISCONNECT, <rc3contains the
disconnect reason code. On AIX, if the <rc1t_errno is
TSYSERR, <rc3contains the system errno (defined in
sys/errno.h). If <rc1contains 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. <rc2contains the MQ-specific error
code. <rc3is not used for MQ.

o SOAP

<rc1contains the return code from the SOAP communication
function. The <rc2depends upon the value of <rc3>.
<rc2is 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 <rc3value "0" indicates that this is a high-level
SOAP error (not a socket or GSKit error). the <rc3value
"1" indicates that this was a socket error. the
<rc3value "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

*************** *************** *************** *************** *************** *************** *************** *

The FEDERATED parameter at server is set to YES and DB2COMM is set to
tcp/ip
Appreciate your help, thanks
Jul 6 '06 #5

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

1
8575
by: alederer | last post by:
Hallo! I have the following situation: A db2 v6.1 client on AIX 4.3 (db2level reports U469703) and a OS/390 database version 6.1 . In some situations, I get the following error in my db2 CLI application: SQL30081N A communication error has been
3
43183
by: Tim Reynolds | last post by:
I support a .Net application running on a SERVER accessing MF Db2 data. Occasionally, we have some type of connection problem that we have been unable to debug up to this point. We typically receive one of these IBM.Data.DB2.DB2Exception messages: ERROR SQL30081N A communication error has been detected. Communication protocol being...
2
9966
by: WantedToBeDBA | last post by:
Hi all, We have db2 installed on AIX box (db2 version - 8.1). Its started and i am able to view 50000(default port) in netstat(netstat -a -n). But when i try to connect using telnet, i am getting this error. I don't know how to correct it. Till yesterday its working well. I don't know what is the problem now.. Help me guys. Its very...
3
7025
by: Laura | last post by:
I've just installed the DB2 Run-time client in a Solaris machine. Then I finnish the installation configuring the connection: 1. machine catalog was OK: ========================== $ db2 catalog tcpip node atlas remote dsroracle server 8100 DB20000I The CATALOG TCPIP NODE command completed successfully. DB21056W Directory changes may not...
1
9006
by: Praveen | last post by:
Hi, I have installed WebSphere Portal on AIX and connected to DB2 on a remote machine, Getting the followin errors when trying to get the values from database thru applications installed on Portal. Any Help Appreciated. Thanks in advance. Praveen Singh
4
36087
by: Ralf Gross | last post by:
Hi, I installed DB2 V8.1 with fixpak 10, created a new database and can connect to the database. $ db2 connect to mkstest Database Connection Information Database server = DB2/LINUX 8.2.3
7
6879
by: Ina Schmitz | last post by:
Hi NG, I wanted to reset the database (manager) configuration with RESET DATABASE CONFIGURATION and RESET DATABASE MANAGER CONFIGURATION After doing this, I rebooted server and client and restarted IBM Universal Database 8.2. But now, I couldn't connect to my database anymore :-( getting the following
0
2214
by: Troels Arvin | last post by:
Hello, From SAS, we're getting the following error message once in a while: ERROR: CLI error trying to establish connection: SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "xxx.xxx.xxx.xxx". Communication...
5
3899
by: bonymuscles | last post by:
Hi All, I am working for the first time on DB2. I have installed ver 7.2, and am using AIX version 5.2, and 5.3 for some DBs. I am getting this error "SQL30081N" for some of the databases. I have added the Databases as per the info I have got. Please guide me as to when this kind of an error may occur, and how I can resolve this? This...
0
7828
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it. First, let's disable language...
0
8186
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed. This is as boiled down as I can make it. ...
0
8329
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that...
0
8197
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the...
1
5704
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes...
0
5377
by: conductexam | last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one. At the time of converting from word file to html my equations which are in the word document file was convert...
0
3821
by: TSSRALBI | last post by:
Hello I'm a network technician in training and I need your help. I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs. The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols. I succeeded, with both firewalls in...
1
2335
by: 6302768590 | last post by:
Hai team i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
1
1436
muto222
by: muto222 | last post by:
How can i add a mobile payment intergratation into php mysql website.

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.