3703225 - DBSQL_CONNECTION_ERROR / R3trans -d RC12 with SQLCODE 2 “database ‘<TENANT>’ not connected” due to ambiguous hdbuserstore DEFAULT (HANA MDC)

In an SAP NetWeaver / SAP S/4HANA ABAP system running on SAP HANA MDC, the system intermittently fails to connect to the database.

Typical indicators are:

• Multiple ST22 ABAP dumps DBSQL_CONNECTION_ERROR (often on connection name like R/3* or R/3*ANNOTATION)
• Dump / dev traces show:
  • SQLCODE: 2
  • SQLERRTEXT: general error: database ‘<TENANT>’ not connected
• R3trans -d fails with RC12 and shows “no connect possible … DBMS = HDB … SERVER = '' PORT = ''”
• The failure already happens during the connection attempt via secure store, for example:
  “Try to connect via secure store (DEFAULT) …”
  and the error is raised before any SQL statement is executed
• At the same time, the SAP HANA database and tenant are running and reachable:
  • HANA services show as up
  • Network reachability / port reachability tests (telnet/curl) succeed
• Behavior can be intermittent: connections work at certain times and fail at others.

SAP HANA DB Version 2.0

DBSQL_CONNECTION_ERROR, SQLCODE 2, SQLERRTEXT general error, database 'SBX' not connected, R3trans -d failure, tenant resolution issue, SYSTEMDB, tenant database, SAP HANA User Store, DEFAULT key configuration, intermittent connection failure , KBA , HAN-DB-CLI , SAP HANA Clients (JDBC, ODBC) , Problem