SAP Knowledge Base Article - Preview

2213725 - How-To: Troubleshooting of -10709 errors

Symptom

Connections from an application to a HANA instance are usually established by the HANA DBSL, plain ODBC/JDBC or ODBO interface.

In case network or connectivity issues occur, usually the error-code 10709 is raised on application side containing an error-text from server (error message).

Typical occurances are:

SL Tools

E.g.: Following the DMO-Option the SUM phase EU_CLONE_MIG_DT_RUN might fail with the following error:

DbSl Trace: Connect to database failed, rc=1, rcSQL=-10709

(DB) ERROR: db_connect rc = 256

<path_to_SUM>\R3load.EXE: job finished with 1 error(s)

The corresponding R3load tracefile reveals the following information related to this error:

R3load.exe.log
----------------

Try to connect via secure store (DEFAULT) on connection 0 ...
DbSl Trace: sdb_malloc(size=1024) : 0000000003F38640 (779906 bytes allocated)
DbSl Trace: Connect to database failed, rc=1, rcSQL=-10709
DbSl Trace: SQLCODE : -10709
DbSl Trace: SQLERRTEXT : Connection failed (RTE:[89006] System call 'connect' failed, rc=10060:A connection attempt failed be\
DbSl Trace: cause the connected party did not properly respond after a period of time, or established connection\
DbSl Trace: failed because connected host has failed to respond)

Also when using R3trans a typical error would be:

R3trans -d

trans.log
----------------
4 ETW000 [ dev trc,00000] Try to connect via secure store (DEFAULT) on connection 0 ... 32 0.006890
4 ETW000 [ dev trc,00000] no connection data found for key (DEFAULT) in HANA secure store 160 0.007050
4 ETW000 [ dev trc,00000] connect via secure store, rc = -10104 (Invalid value for KEY (DEFAULT))
4 ETW000 [ dev trc,00000] Try to connect via environment (<hostname>:<port>) on connection 0 ... 13 0.007080
4 ETW000 [dbhdbsql.cpp,00000] *** ERROR => Connect to database failed, rc=1, rcSQL=-10709 450 0.007530
4 ETW000 [ dev trc,00000] SQLCODE : -10709 18 0.007548
4 ETW000 [ dev trc,00000] SQLERRTEXT : Connection failed (RTE:[89006] System call 'connect' failed, rc=111:Connection refused)
4 ETW000 11 0.007559
4 ETW000 [ dev trc,00000] -> SetSdbDbslCA(errcode=-10709) 12 0.007571
4 ETW000 [ dev trc,00000] -> freeConnection(con_hdl=0) 12 0.007583
4 ETW000 [ dev trc,00000] close all opened locators of connection 0 10 0.007593
4 ETW000 [ dev trc,00000] } DbSlHDBConnect(rc=99) 26 0.007619
4 ETW000 [ dblink ,00000] ***LOG BY2=>sql error -10709 performing CON 37 0.007656
4 ETW000 [ dblink ,00000] ***LOG BY0=>Connection failed (RTE:[89006] System call 'connect' failed, rc=111:Connection refused)

It is clear that for further investigations the "SQLERRTEXT" is of importance here. Proceed to the Cause / Resolution sections.

SAP Application Server ABAP

SAP workprocesses are failing due to connection errors to the HANA Database. This is usually indicated by a short-dump with following categorization:

Category                  Installation Errors
Runtime Errors         DBSQL_SQL_ERROR
Except.                    CX_SY_OPEN_SQL_DB
Date and Time          <datetime>

The shortdumps with the error-code -10709 are raised by the HANA client and can have different root causes. The "Database error text" already reveals a first hint on what might have caused the issue. Here you may see the following error texts:

"SQL message: Connect failed (connect timeout expired)"
"SQL message: Connect failed (no reachable host left)"
"SQL message: Connection failed (RTE:[89006] System call 'send' failed, rc=32:Broken pipe)"
"SQL message: Connection failed (RTE:[89006] System call 'connect' failed, rc=111:Connection refused)"
"SQL message: Connection failed (RTE:[89006] System call 'connect' failed, rc=10061:No connection could be made because the target machine actively refused it)"

A general troubleshooting roadmap for ALL -10709 shortdumps is:

  1. In ST22 open the shortdump
     -> check the "SQL message"
     -> in the section "system environment" identify on which application server and in which dialog workprocess the issue has occured
  2. With this information gathered go to ST11 (make sure you are on the application server for which the shortdump was generated)
     -> open the relevant dialog workprocess trace (dev_wXXX) where XXX should be replaced by the workprocess id
     -> for the corresponding timestamp, the error should be logged in more detail

HANA ODBC

Testing an ODBC connection to a HANA instance fails with the follwing error:

Connection failed: [08S01][SAP AG][LIBODBCHDB SO][HDBODBC] Communication link failure;-10709 Connect failed (no reachable host left)

Independently from where the 10709 error has been raised the following summary of possible error-messages will be discussed in a cause/resolution manner:

Error 1: "Connect failed (connect timeout expired)"
Error 2: "Connect failed (no reachable host left)"
Error 3: "Connection failed (RTE:[89006] System call 'send' failed, rc=32:Broken pipe)"
Error 4: "Connection failed (RTE:[89006] System call 'connect' failed, rc=111:Connection refused)"
Error 5: "Connection failed (RTE:[89006] System call 'connect' failed, rc=10061:No connection could be made because the target machine actively refused it)"


Read more...

Product

SAP HANA 1.0, platform edition

Keywords

communication, link, statement routing, client_distribution_mode , KBA , HAN-DB-CLI , SAP HANA Clients (JDBC, ODBC) , HAN-DB , SAP HANA Database , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.