Timeout connection on DWC (SAP Datawherehouse Cloud) with open sql schema user

[diego_oliveira4]

In our DWC environment we configure a user for direct access to database (Open SQL Schema). We have created some procedures with this user, but we are having difficulty executing because the internal DWC database is configured to reset the connection after a few minutes (before finalizing the execution of the procedure).

Is there any way to set the connection timeout for a longer or indefinite timeout?

[simon25 · Accepted solution]

Hi Diego,

There may be a corresponding entry in the indexserver trace of the DWC tenant DB for this error.

The "Socket closed by peer" error is slightly different , but more or less the same as we would expect in the indexserver trace or an ABAP dump : "rc=104:Connection reset by peer local=xx.xx.xx.xx:3xx15 , remote= xx.xx.xx.xx_tcp". This error indicates that the target host can't be reached.

Is it an expensive procedure or long running before providing the expected result , or does it immediately terminate with the dump on hdbsql ?

Session and connection timeouts are usually controlled on HANA globally or per tenant db, by these inifile parameter families :

'indexserver.ini -> [session]'

'indexserver.ini -> [communication]'

'global.ini -> [communication]'

Detailed further in these SAP KBA sections :

'7. What are important network related SAP HANA parameters?' - 2222200 - FAQ: SAP HANA Network

'17. Which timeouts exist on SAP HANA side?' - 2000003 - FAQ: SAP HANA

indexserver.ini -> [session] -> initial_receive_timeout

indexserver.ini -> [session] -> socket_keepalive

indexserver.ini -> [communication] -> default_read_timeout

indexserver.ini -> [session] -> idle_connection_timeout

.........

Any kind of timeout issues or dropped connections on the network layer during a transaction on HANA, we would always recommend customers ensure they have optimal configuration setup as per 2382421 - Optimizing the Network Configuration on HANA- and OS-Level

Kind Regards

Simon