Home   |   Register   |   Rules   |   Calendar   |   Get Daily   |     |  
 


If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > [IBM][CLI Driver] SQL30081N A communication error has been detected.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 03-03-06, 01:02
sundaram sundaram is offline
Registered User
  
Join Date: Mar 2006
Posts: 104
[IBM][CLI Driver] SQL30081N A communication error has been detected.
We are using DB2 version 7.2.5 and websphere application server 5.1.5.

Occasionaly we get a communication error connecting to database through Websphere Datasource.

Any idea why this error is comming? Can it be due to network problems?


The Error in websphere log is

STATE: 08001; MESSAGE: [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error: "connect". Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001
DSRA0010E: SQL State = 08001, Error Code = -30,081; ERROR_CODE: -30081
java.sql.SQLException: [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error: "connect". Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001


Thanks
DSRA0010E: SQL State = 08001, Error Code = -30,081
Reply With Quote
  #2 (permalink)  
Old 03-07-06, 06:04
JAYANTA_DATTA JAYANTA_DATTA is offline
Registered User
  
Join Date: Oct 2004
Location: DELHI INDIA
Posts: 336
Hi Dear,
If your WEBSPHERE is on a different machine and on that DB2 client is installed, then take the entry in the db2diag.log at the client machine as well as in the DB2 Server machine.

I hope looking at the db2diag.log people can give you better suggestion.
Reply With Quote
  #3 (permalink)  
Old 03-07-06, 06:11
JAYANTA_DATTA JAYANTA_DATTA is offline
Registered User
  
Join Date: Oct 2004
Location: DELHI INDIA
Posts: 336
Hi Dear,
If your WEBSPHERE is on a different machine and on that DB2 client is installed, then take the entry in the db2diag.log at the client machine as well as in the DB2 Server machine.

I hope looking at the db2diag.log people can give you better suggestion.
Reply With Quote
  #4 (permalink)  
Old 03-07-06, 17:33
sundaram sundaram is offline
Registered User
  
Join Date: Mar 2006
Posts: 104
Thanks for the reply Jayant.
The websphere and db2 are running in different machines.

The db2 server has no error entries.

The entries in db2diag.log in client machine are:

2006-03-04-16.57.51.734000 InstanceB2 Node:000
PID:3424(java.exe) TID:5976 Appid:015DC746.B104.060303052002
common_communication sqlcctcpconnr Probe:101
DIA3202C The TCP/IP call "connect" returned an errno="10060".

2006-03-05-00.00.22.093000 InstanceB2 Node:000
PID:4424(java.exe) TID:2224 Appid:
common_communication sqlcctcpconnr Probe:101
DIA3202C The TCP/IP call "connect" returned an errno="10060".

2006-03-05-04.46.22.781000 InstanceB2 Node:000
PID:3424(java.exe) TID:4544 Appid:015DC746.B104.060303052002
common_communication sqlcctcpconnr Probe:101
DIA3202C The TCP/IP call "connect" returned an errno="10060".
Reply With Quote
  #5 (permalink)  
Old 03-07-06, 19:53
sathyaram_s sathyaram_s is offline
Super Moderator
  
Join Date: Aug 2001
Location: UK
Posts: 4,534
For a start, a couple of things to check ...

a) Can the websphere machine connect to the db2 machine ... can you ping from one another ..

b) What is the port number on the server DB2 is configure ..

db2 get dbm cfg , SVCENAME config parm ...

netstat -an | find "<portnum>"

Is the DB2 server really listening ?

c) On the client is the node directory referring to the correct host (ping using this hostname) and the portnumber as identified above ...

d) on the server, have you set the registry variable, DB2COMM set to TCPIP

db2set -all

Cheers
Sathyaram
__________________
Visit the new-look IDUG Website , register to gain access to the excellent content.
Reply With Quote
  #6 (permalink)  
Old 03-08-06, 18:30
sundaram sundaram is offline
Registered User
  
Join Date: Mar 2006
Posts: 104
Hi Sathyam,

a) Can the websphere machine connect to the db2 machine ... can you ping from one another ..

yes

b) What is the port number on the server DB2 is configure ..

db2 get dbm cfg , SVCENAME config parm ...

netstat -an | find "<portnum>"

Is the DB2 server really listening ?

YES

c) On the client is the node directory referring to the correct host (ping using this hostname) and the portnumber as identified above ...

YES
d) on the server, have you set the registry variable, DB2COMM set to TCPIP

YES
Reply With Quote
  #7 (permalink)  
Old 03-08-06, 20:11
sathyaram_s sathyaram_s is offline
Super Moderator
  
Join Date: Aug 2001
Location: UK
Posts: 4,534
Ha ... I missed the term occassionally in your original post. If this is the case, yes, I would say it is very likely to be network issues

Sathyaram

Quote:
Originally Posted by sundaram
Occasionaly we get a communication error connecting to database through Websphere Datasource.

Any idea why this error is comming? Can it be due to network problems?
__________________
Visit the new-look IDUG Website , register to gain access to the excellent content.
Reply With Quote
  #8 (permalink)  
Old 03-09-06, 07:26
atinjain05 atinjain05 is offline
Registered User
  
Join Date: Mar 2006
Location: UK
Posts: 8
communication error
hi sundaram

I also got this problem in my setup,I have logged a PMR for this 2 days back and they asked me to visit this site and i hope it will be helpful for you also

http://www-1.ibm.com/support/docview...UTF-8&lang=all


Let me know for any further info
Reply With Quote
  #9 (permalink)  
Old 03-09-06, 07:51
sathyaram_s sathyaram_s is offline
Super Moderator
  
Join Date: Aug 2001
Location: UK
Posts: 4,534
Did this solve your problem ??

When I had a similar issue, I tried all such settings and they didn't help .. As the client was communicating over a WAN to a remote database server, certain firewall settings caused timeout and DB2 received this error .. So the network guys had to make some configuration changes ... Well, this was back in 2000 ...

Of course, every environment is unique

Sathyaram
__________________
Visit the new-look IDUG Website , register to gain access to the excellent content.
Reply With Quote
  #10 (permalink)  
Old 03-09-06, 07:58
atinjain05 atinjain05 is offline
Registered User
  
Join Date: Mar 2006
Location: UK
Posts: 8
Hi
As I mentioned that it happens 2 days back only,I am yet to test this.

Just pass the info if it can help

Regards
Ati
Reply With Quote
  #11 (permalink)  
Old 03-09-06, 23:11
sundaram sundaram is offline
Registered User
  
Join Date: Mar 2006
Posts: 104
Hi

That link is quite useful. We will try it out and let the forum know of the outcome.


Thanks
Reply With Quote
Reply

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 
 
 
Home  |   Register  |   Get New  |   FAQ's  |   Sitemap

Powered by vBulletin
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.