Protocol Specific Error Codes 10053
Contents |
sql30081n; RC=9; QUERYTIMEOUTINTERVAL Technote (troubleshooting) Problem(Abstract) Client applications fail with error: [IBM][CLI Driver] SQL30081N A communication error has
Sql30081n A Communication Error Has Been Detected. Sqlstate=08001
been detected. Communication protocol being used: "TCP/IP". Communication API being used: protocol specific error code(s): "*", "*", "0". sqlstate=08001 "SOCKETS". Location where the error was detected: "10.111.11.2". Communication function detecting the error: "send". Protocol specific error
Protocol Specific Error Code(s) 10061 * * . Sqlstate=08001
code(s): "9", "*", "*". SQLSTATE=08001 Cause The error 9 from looking at the errno.h file is: #define EBADF 9 /* Bad file descriptor */ "rc 9 (bad file descriptor) communication function detecting the error: "selectforconnecttimeout" - Sockets are handled as file objects which are opened and closed (using fopen() and fclose()) - if DB2 requests a "recv" sockets__API call on a socket that no longer exists, we get back a rc=9 when the socket's API attempts to open the "file". Environment All Diagnosing the problem Check the DCS Entry for the INTERRUPT_ENABLED communication function detecting the error recv set. This is the third positional parameter (,,INTERRUPT_ENABLED ). Resolving the problem Anytime a client application terminates a connection by means of closing the application abnormally or any kind of interrupt, it will terminate the connection to the mainframe and the gateway will receive an SQL30081N error. "SQL30081 rc=9" for Bad File Descriptor is caused by the host not responding to the client connect request. This indicates that the client timed out the connection with the server because the client did not receive a reply in a reasonable amount of time. The solution is to set QUERYTIMEOUTINTERVAL=0 in the db2cli.ini and stop and restart the application. Related information SQL30081N Document information More support for: DB2 for Linux, UNIX and Windows OTHER - Uncategorised Software version: 9.1, 9.5, 9.7 Operating system(s): AIX, HP-UX, Linux, Solaris, Windows Reference #: 1395987 Modified date: 18 November 2015 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & platforms Xamarin ASP.NET C++ TypeScript .NET - VB, https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started protocol specific UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started protocol specific error Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Networking and Internet Windows Sockets 2 Winsock Reference Winsock Reference Windows Sockets Error Codes Windows Sockets Error Codes Windows Sockets Error Codes Socket Options Winsock IOCTLs Winsock Annexes Winsock Enumerations Winsock Functions Winsock Structures and Typedefs Winsock Tracing Events Winsock SPI Windows Sockets Error Codes TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Windows Sockets Error Codes Most Windows Sockets 2 functions do not return the specific cause of an error when the function returns. For information, see the Handling Winsock Errors topic. The WSAGetLastError function returns the last error that occurred for the calling thread. When a particular Windows Sockets function indicates an error has occurred, this function should be called immediately to retrieve the extended error code for the failing function call. These error codes and a short text description associated with an error code are defined in the Winerror.h header file. The FormatMessage function can be used to obtain the message string for the returned error. For information on how to handle error codes when porting socket applica