Client-Server ==> FUNNY SITUATION

Anurag Kumar

Client-Server ==> FUNNY SITUATION
___________________________________________
ENVIRONMENT
___________________________________________

(1) Server = DB2 UDB DPF, 8.2.3 on AIX, 64-bit instance.
(2) Client = DB2 RTC 8.1 FP10 on AIX, 64-bit instance.

___________________________________________
PROBLEM
___________________________________________
(1) 1st, 3rd, 5th....attempts to connect to server database
are successful.
(2) 2nd, 4th, 6th...attempts to connect to server database
return tcp/ip error. Error Message is as below:

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

_______________________________________________

I have done the basic checking - DB2COMM / SVCENAME etc
Also note that I do not have to do absolutely anything between
1st and 2nd attempt to get the failure message AND similarly
I do not have to do absolutely anything between
2nd and 3rd attempt to get connected !!


This problem has had me completely floored.
Any advice is urgently sought (YES, THIS IS PRODUCTION)

TiA.............Anurag
D

************************************************************
HSBC Software Development (India) Pvt Ltd
HSBC Center Riverside,West Avenue ,
25 B Kalyani Nagar Pune 411 006 INDIA

Telephone: +91 20 26683000
Fax: +91 20 26681030
************************************************************


-----------------------------------------
***********************************************************************
This e-mail is confidential. It may also be legally privileged.
If you are not the addressee you may not copy, forward, disclose
or use any part of it. If you have received this message in error,
please delete it and all copies from your system and notify the
sender immediately by return e-mail.

Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
***********************************************************************

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

paul martin

Re: Client-Server ==> FUNNY SITUATION
(in response to Anurag Kumar)
Could it be the ports\channels on the mainframe servicing this have two
assigned and it is doing something like load balancing and one works and
the other doesn't?
Paul

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Anurag Kumar
Sent: Wednesday, January 04, 2006 8:41 AM
To: [login to unmask email]
Subject: [DB2-L] Client-Server ==> FUNNY SITUATION

___________________________________________
ENVIRONMENT
___________________________________________

(1) Server = DB2 UDB DPF, 8.2.3 on AIX, 64-bit instance.
(2) Client = DB2 RTC 8.1 FP10 on AIX, 64-bit instance.

___________________________________________
PROBLEM
___________________________________________
(1) 1st, 3rd, 5th....attempts to connect to server database
are successful.
(2) 2nd, 4th, 6th...attempts to connect to server database
return tcp/ip error. Error Message is as below:

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

_______________________________________________

I have done the basic checking - DB2COMM / SVCENAME etc Also note that I
do not have to do absolutely anything between 1st and 2nd attempt to get
the failure message AND similarly I do not have to do absolutely
anything between 2nd and 3rd attempt to get connected !!


This problem has had me completely floored.
Any advice is urgently sought (YES, THIS IS PRODUCTION)

TiA.............Anurag
D

************************************************************
HSBC Software Development (India) Pvt Ltd HSBC Center Riverside,West
Avenue ,
25 B Kalyani Nagar Pune 411 006 INDIA

Telephone: +91 20 26683000
Fax: +91 20 26681030
************************************************************


-----------------------------------------
***********************************************************************
This e-mail is confidential. It may also be legally privileged.
If you are not the addressee you may not copy, forward, disclose or use
any part of it. If you have received this message in error, please
delete it and all copies from your system and notify the sender
immediately by return e-mail.

Internet communications cannot be guaranteed to be timely, secure, error
or virus-free. The sender does not accept liability for any errors or
omissions.
***********************************************************************

------------------------------------------------------------------------
---------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Robert A. (Cameron of Pittsburgh at Alcoa) Knight

Re: Client-Server ==> FUNNY SITUATION
(in response to paul martin)
I have had similar problems in the past:
Could be incorrect I/P address or port or both;
One resolution was to recycle the server. The
Sqlstate was 08001/08003

I would be interested in the final solution

Bob Knight

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Anurag Kumar
Sent: Wednesday, January 04, 2006 9:41 AM
To: [login to unmask email]
Subject: [DB2-L] Client-Server ==> FUNNY SITUATION

___________________________________________
ENVIRONMENT
___________________________________________

(1) Server = DB2 UDB DPF, 8.2.3 on AIX, 64-bit instance.
(2) Client = DB2 RTC 8.1 FP10 on AIX, 64-bit instance.

___________________________________________
PROBLEM
___________________________________________
(1) 1st, 3rd, 5th....attempts to connect to server database
are successful.
(2) 2nd, 4th, 6th...attempts to connect to server database
return tcp/ip error. Error Message is as below:

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

_______________________________________________

I have done the basic checking - DB2COMM / SVCENAME etc
Also note that I do not have to do absolutely anything between
1st and 2nd attempt to get the failure message AND similarly
I do not have to do absolutely anything between
2nd and 3rd attempt to get connected !!


This problem has had me completely floored.
Any advice is urgently sought (YES, THIS IS PRODUCTION)

TiA.............Anurag
D

************************************************************
HSBC Software Development (India) Pvt Ltd
HSBC Center Riverside,West Avenue ,
25 B Kalyani Nagar Pune 411 006 INDIA

Telephone: +91 20 26683000
Fax: +91 20 26681030
************************************************************


-----------------------------------------
***********************************************************************
This e-mail is confidential. It may also be legally privileged.
If you are not the addressee you may not copy, forward, disclose
or use any part of it. If you have received this message in error,
please delete it and all copies from your system and notify the
sender immediately by return e-mail.

Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
***********************************************************************

------------------------------------------------------------------------
---------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Jay Reavill

Re: Client-Server ==> FUNNY SITUATION
(in response to Robert A. (Cameron of Pittsburgh at Alcoa) Knight)
The only time I've seen a similar situation is when a connection is forced
off. After the force it typically would take 2 connect attempts to be
successful. Could it be that the connections are somehow being forced off
or not terminating cleanly?

----------------------------------------
Jay Reavill DBA
Certegy Card Services
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
----------------------------------------




"Anurag Kumar"
<[login to unmask email] To: [login to unmask email]
C.CO.IN> cc:
Sent by: "DB2 Subject: [DB2-L] Client-Server ==> FUNNY SITUATION
Data Base
Discussion List"
<[login to unmask email]
.ORG>


01/04/2006 09:41
AM
Please respond
to "DB2 Database
Discussion list
at IDUG"





___________________________________________
ENVIRONMENT
___________________________________________

(1) Server = DB2 UDB DPF, 8.2.3 on AIX, 64-bit instance.
(2) Client = DB2 RTC 8.1 FP10 on AIX, 64-bit instance.

___________________________________________
PROBLEM
___________________________________________
(1) 1st, 3rd, 5th....attempts to connect to server database
are successful.
(2) 2nd, 4th, 6th...attempts to connect to server database
return tcp/ip error. Error Message is as below:

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

_______________________________________________

I have done the basic checking - DB2COMM / SVCENAME etc
Also note that I do not have to do absolutely anything between
1st and 2nd attempt to get the failure message AND similarly
I do not have to do absolutely anything between
2nd and 3rd attempt to get connected !!


This problem has had me completely floored.
Any advice is urgently sought (YES, THIS IS PRODUCTION)

TiA.............Anurag
D

************************************************************
HSBC Software Development (India) Pvt Ltd
HSBC Center Riverside,West Avenue ,
25 B Kalyani Nagar Pune 411 006 INDIA

Telephone: +91 20 26683000
Fax: +91 20 26681030
************************************************************


-----------------------------------------
***********************************************************************
This e-mail is confidential. It may also be legally privileged.
If you are not the addressee you may not copy, forward, disclose
or use any part of it. If you have received this message in error,
please delete it and all copies from your system and notify the
sender immediately by return e-mail.

Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
***********************************************************************

---------------------------------------------------------------------------------

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org
. The IDUG List Admins can be reached at [login to unmask email]
Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm








------------------------------------------------------------------------------
This message contains information from Certegy, Inc which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e:mail [login to unmask email]
=====

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm