SAP Knowledge Base Article - Preview

2050354 - Troubleshooting network problems between the HANA Instance and SAP application servers

Symptom

Network problems may result in a variety of symptoms/problems, including but not limited to:

  • A significant increase in database response time on SAP side (transaction ST03n) is reported. Workprocesses are stuck in "sequential read" according to transactions SM50/SM66 even though no database activity is visible on HANA side and no excessive statement runtimes can be identified.

  • Transactions might abort with a variety of SQL errors. The following ones are most common in this situation:
    • 10807 - Connection Loss
    • 10108 - Session Reconnect
  • In some cases these errors are accompanied by secondary error codes that put an even stronger emphasis to a problem on network layer:
    • System call 'recv' failed, rc=110:Connection timed out
    • System call 'recv' failed, rc=10060:A connection attempt failed because the connected party did not properly respond

The exact error codes are depending on the operating system that is used on client (SAP) side.


Read more...

Environment

Netweaver on HANA

Keywords

KBA , performance , latency , rtt , HAN-DB , SAP HANA Database , Problem

About this page

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

Search for additional results

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