3603932 - Resolving Authentication Failed Errors in DB13 Scheduled Jobs or DBACOCKPIT SQL Execution

• Jobs scheduled in DB13, such as the "Consistency Check" job, fail with an "authentication failed" error.
  

  Example error messages:

  04.05.2025    00:00:10    Exception CX_DBA_ADBC in class CL_HDB_ADBC method line 87
  04.05.2025    00:00:10    Execution of the Command:
  04.05.2025    00:00:10    call "CHECK_TABLE_CONSISTENCY"( ?, ?, ? )
  04.05.2025    00:00:10    On host: hostname
  04.05.2025    00:00:10    Command failed
  04.05.2025    00:00:10    authentication failed
  04.05.2025    00:00:10    SQL Error code 10
  

• Executing any SQL statement, such as SELECT * FROM m_databases; in DBACOCKPIT -> SQL Editor, fails with the following error:
  

  Exception CX_DBA_ADBC in class CL_HDB_SQL_EXECUTOR method EXEC_QUERY_DYN line 142 
        Kernel Error ID:       
        WP ID:      13  
        WP PID:      8778 
        Application Server:      hostname
        SYSID:      SID 
        SY-SUBRC:      0  
        SQL statement: select * from M_databases; 
        Database: SID
   caused by 
   Exception CX_SQL_EXCEPTION in class CL_SQL_CONNECTION  
        Kernel Error ID:       
        DB Error:           Yes 
        SQL Code:           10  
        SQL Message:      authentication failed 
        DB Object Exists:      No 
        Duplicated Key:      No 
        Internal Error:      1  
        Invalid Cursor:      No 
        Unknown Connection:      No 
        Connection Closed:      No
  

• The dev_w* trace files contain the following error messages:
  

  B Wed May  7 01:44:09:447 2025
  B  Connect to SID as SYSTEM with hostname:30615
  C  Try to connect SECONDARY as SYSTEM@hostname:30615 on connection 1 ...
  C  connect property [APPLICATION = ABAP:SID]
  C  connect property [APPLICATIONVERSION = 753 PL 1410]
  C  connect property [UNICODE = 1]
  C  connect property [SQLMODE = SAPR3]
  C  connect property [VARCHARMODE = ABAP]
  C  connect property [PACKETSIZE = 1048576]
  C  connect property [COMPLETEARRAYEXECUTION = 1]
  C  connect property [CONNECTTIMEOUT = 30000]
  C  connect property [CACHEDVIEWTS = 1]
  C  connect property [STATEMENTROUTINGWARNINGS = TRUE]
  C  connect to SYSTEM/<pwd>@hostname:30615 on connection 1 ...
  C  *** ERROR => Connect to database failed, rc=1, rcSQL=10
   [dbhdbsql.cpp 860]
  C  {root-id=0A26DE3A3C6A1FD08ADB60CAC2C0AF4C}_{conn-id=00000000000000000000000000000000}_0
  C  SQLCODE    : 10
  C  SQLERRTEXT : authentication failed
  B  ***LOG BY2=> sql error 10 performing CON [dbds         1007]
  B  ***LOG BY0=> authentication failed [dbds         1007]
  

• In DBACOCKPIT -> System Landscape -> Database Connections, the "DB User" of "DEFAULT" connection (in this case, BW4) shows a different user rather than the schema user, e.g., SAPHANADB. In the example below, it shows "SYSTEM".
  
  
  
• In DBCO, a secondary connection with the same name as SID is created.
  
  
  

  The connection test for this secondary connection fails with the same "authentication failed" error.
  To test the connection:

  1. Go to T-code SE38.
  2. Execute Program: ADBC_TEST_CONNECTION.
  3. Input DB Connection Name: BW4 (example) and click Execute (F8).
  
  
  

 "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, platform edition 2.0       

HANA, authentication failed, SQL Error code 10, CX_DBA_ADBC, CL_HDB_ADBC, CL_HDB_SQL_EXECUTOR, EXEC_QUERY_DYN, CL_SQL_CONNECTION, DB13, DBACOCKPIT, SQL Execution , KBA , HAN-DB-SEC , SAP HANA Security & User Management , Problem