2769851 - SAP schema user in HANA DB locked due to liveCache authentication failure

Your SAP schema user was locked due to too many failed authentication/logon attempts.

Please note that the SAP schema username will differ between SAP systems; some possible SAP schema usernames include:

• SAPABAP1
• SAPHANADB
• SAPSR3
• SAP<SID>
• etc.

When testing the credentials maintained in the hdbuserstore (or ABAP SFSS) across all application server(s), the credentials are valid.

---

Using HANA audit policies, you are able to detemine that the origin of the of the unsuccessful authentication requests is your SAP system's application server(s) and the <sid>adm user.

From the SAP GUI, you do the following:

1. Navigate to t-code AL11
2. Open DIR_HOME
3. Use the Search for Character Strings in the Displayed Files (Shift+F1) option to search for the following string in the work process developer traces:
   "authentication failed"

In the developer traces, you see content similar to the following:

B Connect to LCA as SAPABAP1 with <server name>:<port>
C Try to connect as SAPABAP1/<pwd>@<server name>:<port> on connection 2 ...
C *** ERROR => Connect to database failed, rc=1, rcSQL=10
 [dbhdbsql.cpp 584]
................................................................................................................
C SQLCODE : 10
C SQLERRTEXT : authentication failed

Alternatively, you may see:

• Connect to LDA
• Connect to LEA

If you do not see a "Connect to <DB connection name>" string, then this KBA does not apply to your scenario.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

SAP HANA DB based SAP system using liveCache

livecache, sql error 10, database connection, secondary database connection, DBCO , KBA , HAN-DB-SEC , SAP HANA Security & User Management , BC-DB-LVC , liveCache , Problem