Been Being Communication Communication Detected Error Has Protocol Sql30081n Used
Contents |
errors; 30081; SQL30081; SQL30081N; 30081; -30081 Technote (FAQ) Question This document lists SQL30081N TCP/IP communication protocol errors and
Protocol Specific Error Code(s) 10060 * * . Sqlstate=08001
recommended action plans associated with them. Cause The communication protocol errors [ibm][cli driver] sql30081n a communication error has been detected depend on the platform you are working on. Each protocol error has its own definition and corresponding
Sql30081n "10060"
action plan. Answer For further discussion on this topic, visit this developerWorks forum thread: https://www.ibm.com/developerworks/community/forums/html/topic?id=cceab3ae-4dd4-425a-af81-0b4e3f965ee2 Problem Details The SQL30081N error message has the following format: SQL30081N A protocol specific error code(s): "*", "0". sqlstate=08001 communication error has been detected. Communication protocol being used: protocol . Communication API being used: interface . Location where the error was detected: location . Communication function detecting the error: function . Protocol specific error code(s): rc1 , rc2 , rc3 For example: SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". communication function detecting the error: "selectforconnecttimeout" Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error: "connect". Protocol specific error code(s): "111", "*", "*". The following table lists protocol specific errors that can occur on different platforms and the corresponding action plans to resolve these errors. If the error code is not listed in the table, search the operating system documentation /usr/include/errno.h (Linux/UNIX) or System Error Codes (Windows). Windows AIX SUN HP Linux Short Name Action Plan 10061 79 146 239 111 ECONNREFUSED Connection Refused Client attempts to establish a connection to server using an invalid IP or port. Check on server side: DB2 environment variable DB2COMM is set such as: DB2COMM=TCPIP DBM CFG's SVCENAME is set to the instance's port number or service name. The command to update this parameter is: "db2 update dbm cfg using svcename
communicating with a DB2 server on AIX, and IBM AIX TCP Traffic Regulation has been enabled sql30081 rc=32 RC=73 tcptr_enable concurrent Traffic Regulation denial of service Technote (troubleshooting) Problem(Abstract) When IBM http://www.ibm.com/support/docview.wss?uid=swg21673820 AIX TCP Traffic Regulation has been enabled, DB2 client applications may receive errors on https://scn.sap.com/thread/3604730 connections and other server requests, such as SQL30081 rc=32 or rc=73. Symptom DB2 client applications fail with communication errors such as:
[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: "192.168.1.110".
Communication function detecting the protocol specific error: "send". Protocol specific
error code(s): "32", "*", "0". SQLSTATE=08001
or
[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: "192.168.1.110".
Communication function detecting the error: "recv". Protocol specific
error code(s): "73", "*", "0". SQLSTATE=08001
Cause The AIX systems administrator may have enabled IBM AIX TCP protocol specific error Traffic Regulation, which provides kernel-level TCP Denial-of-Service (DoS) attack mitigation. This feature may have also been enabled by running the AIXpert tool and selecting a high security mode. The parameter is tcptr_enable =1. Environment AIX 6.1 and higher. Diagnosing the problem The parameter enabling IBM AIX TCP Traffic Regulation is tcptr_enable, which by default is set to off (0). The setting can be checked with the no -a command: # no -o tcptr_enable
tcptr_enable = 1
The policies in effect can be viewed by issuing the tcptr -show command:
# tcptr -show
TCP Traffic Regulation Policies:
StartPort=39044 EndPort=39044 MaxPool=16 Div=1 Used=7
Note that the TCP/IP port that DB2 is listening on is defined by the SVCENAME database manager configuration parameter. Any policy covering that port may be imposing limits on remote DB2 connections. Resolving the problem If TCP traffic regulation is enabled, consult with the systems administrator to determine more appropriate settings. Related information IBM AIX TCP Traffic Regulation A simplified Chinese translation is available Document information More support for: DB2 for Linux, UNIX and Windows Connectivity - DRDA Software version: 9.5, 9.7, 9.8, 10.1, 10.5 Operating system(s): AIX Software edition: Advanced Enterprise Server, Advanced Workgroup Server, Enterprise Server, Express, Express-C, Personal, Workgrou
Enterprise Resource Planning (SAP ERP)Where is this place located?All Places Enterprise Resource Planning (SAP ERP) 10 Replies Latest reply: Nov 17, 2014 2:27 PM by Vineet Patil Tweet protocol being used: "TCP/IP". Communication API being used: "SOCKETS Vineet Patil Aug 17, 2014 12:44 PM Currently Being Moderated Hi,We are performing Oracle to DB2 database migration .In Adjust nametab phase below error is being faced:Execution of the command "/usr/sap/SBX/SYS/exe/run/dipgntab -rwr40 -srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT" finished with return code 255. Output:ERROR in initialization (can't get R/3-version)ERROR in initialization (can't get R/3-version)Log file dipgntab.log contains :ERROR in initialization (can't get R/3-version)We tried to catalog the DB,edited /etc/services for sapdb2