## 3.18.3  Application and Database Connectivity Analysis
There are a number of ways to identify possible root causes for network communication issues between your application and the SAP HANA instance it is connecting to.
## Prerequisites
You have access to both the application and SAP HANA instance.
## Procedure
1. On an ABAP application server, check the following:
- a. Run transaction OS01 - Database - Ping x10 If a connection to the database cannot be established over a longer period of time by an SAP ABAP
application work process, the work process is terminated. First, the work process enters the reconnect
state in which it constantly tries to connect to the database, after a predefined amount of retries fail, the work process terminates. In this case the connectivity from the SAP application server to the SAP HANA server must be verified.
- b. Run transaction SE38 - Report ADBC_TEST_CONNECTION
If a specific database connection is failing, the report ADBC_TEST_CONNECTION offers a connectivity check for each defined database connection.
- c. Check for common errors in SAP KBA 2213725 - How-To: Troubleshooting of -10709 errors
If an application is facing communication issues with the SAP HANA server, on client side the connectivity issue may be indicated by several 10709-errors, mostly short dumps. The error 10709 is generic but the error text of the short dumps contains the error information that was returned by the server. Some root causes may be found in unfavorable parameter settings, either on client or on server side, some may be caused by a faulty network.
In most cases, a short dump with characteristics is raised:
The "Database error text" gives you a first hint as to what might have caused the issue. For an overview of the most common errors in this context and detailed explanations of how to resolve them, see SAP KBA 2213725 - How-To: Troubleshooting of -10709 errors .
2. On non-ABAP applications, check the following SAP Notes and documentation references:
- a. SAP Note 1577128 - Supported clients for SAP HANA
On non-ABAP client connections check that the client you are using is supported.
- b. Section Troubleshooting: ODBC Tracing in the SAP HANA Client Interface Programming Reference
A typical SAP HANA ODBC connection failure is indicated by an error with the following prefix:
The most common errors are documented in SAP Notes and KBAs. You can use the search features of the Support portal to find a solution for a specific error. If no specific SAP Note is available, you can record an ODBC trace to gain more detailed insight.
- c. SAP KBA 2081065 - Troubleshooting SAP HANA Network
If the error occurs sporadically, it is useful to perform a long-term stress test between the client and SAP HANA server to confirm the network's stability. For more information, see SAP Note 500235 . T o examine the exact traffic from the TCP/IP layer, a tcpdump can be recorded which shows what packets are sent and received and which packets were rejected or required a retransmission.
3. Generic Smart Data Access troubleshooting steps are:
- a. To verify that the issue might not be a flaw in the SAP HANA cockpit, always try to connect via the 'isql' tool on the SAP HANA host directly as the SAP HANA &lt;sid>= adm.
- b. Make sure all libraries can be accessed on OS level by the SAP HANA &lt;sid>= adm user (PATH environment variable).
- c. In the SAP HANA &lt;sid>= adm home directory (cd $home) check that the correct host and port, and username and password combinations are used in the .odbc.ini file.
- d. Check that the LD_LIBRARY_PATH environment variable of the SAP HANA &lt;sid>= adm user contains the unixODBC and remote DB driver libraries.
For example, with a Teradata setup, the LD_LIBRARY_PATH should contain the following paths: .../usr/local/unixODBC/lib/:/opt/teradata/client/15.00/odbc_64/lib...
Connections from the SAP HANA server to remote sources are established using the ODBC interface (unixODBC). For more information, see the SAP HANA Administration Guide .
4. Microsoft SQL Server 2012 - Specific Smart Data Access Troubleshooting
- a. Make sure unixODBC 2.3.0 is used. A higher version leads to a failed installation of the Microsoft ODBC Driver 11 for SQL Server 2012.
- b. The version can be verified with the following command executed as the SAP HANA &lt;sid>= adm user on the SAP HANA host: isql --version .
- c. You can also refer to the Guided Answers tree Troubleshooting Smart Data Access (SDA) Configuration .
5. Teradata - Specific Smart Data Access Troubleshooting
- a. Check SAP KBA 2078138 - "Data source name not found, and no default driver specified" when accessing a Teradata Remote Source through HANA Smart Data Access .
7. Under certain circumstances it is necessary to adjust the order of the paths maintained in LD_LIBRARY_PATH.
## Related Information
SAP Note 2213725
SAP Note 1577128
SAP Note 2081065
SAP Note 500235
SAP Note 2078138
SAP HANA Administration Guide
Client Interface Programming Reference: ODBC Tracing and Trace Options
Troubleshooting Smart Data Access (SDA) Configuration (Guided Answer)