Solution : https://service.sap.com/sap/support/notes/1364372 (SAP Service marketplace login required)
Summary :
When establishing secondary database connections in SAP environments, users encounter significant delays which block SAP work processes through long-running connection attempts. In certain conditions, such as during crash recovery phases of the target database, connection setups are prone to timeouts, specifically resulting in an SQL error code -30081. SAP's remedy involves patches for DB2 V9.1 enhancing default timeout periods from 5 seconds to 60 seconds to avoid abrupt connection failures. Additionally, SAP has introduced configurable parameters like 'dbs/db6/dbsl_login_timeout_secondary' to tailor timeout settings, aiding in managing connection stability and system performance.
Key words :
sqlstate=08001abap location info 'cl_sql_connection=============cp', sap applications periodically open secondary database connections, [ibm][cli driver] sql30081n, sap work process takes, sap database interface library, dbs/db6/dbsl_login_timeout_secondary=<seconds>, protocol specific error code, sap work process, sap database interface, sap work processes
Related Notes :
| 1267189 | DBA Cockpit: DB2 for LUW as Remote Database |