3529290 - Database error text: "SQL message: error while parsing protocol: StatementContextPart is corrupted."  

The following runtime error occurs on different tables in ABAP program for many times:

TYPE                   ABAP Program Error
Runtime Error             DBSQL_SQL_ERROR
Exception                   CX_SY_OPEN_SQL_DB
ABAP Program              SAPLFAGL_AUTHORITY_FI_DATA
Application Component               FI-GL
Date and Time             2024.10.14 14:37:01 (UTC+8)
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Short Text:                                                                                             |
|    SQL error "SQL code: 1033" occurred while accessing table "<TABLE_NAME>".                             |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|What Happened ?                                                                                      |
|    Database error text: "SQL message: error while parsing protocol:                              |
|     StatementContextPart is corrupted."                                                          |
----------------------------------------------------------------------------------------------------

In HANA DB indexserver trace file, the following error messages were reported at the same time: 
-----------------------------------------------------------------------------------------------------
[37858]\{300841\}[-1/-1] 2024-10-14 14:37:01.358015 i TraceContext     TraceContext.cpp(01347) : UserName=SAPHANADB, ApplicationUserName=<app_user_name>, ApplicationName=ABAP:ISP, ApplicationSource=SAPLFAGL_AUTHORITY_FI_DATA:971, Client=800, EppRootContextId=81ECA03735AC1EDFA2BECC20CD16B2E6, EppTransactionId=3FC33295C23002C0E0066DC5B5BF4CE0, EppConnectionId=00000000000000000000000000000000, EppConnectionCounter=0, EppComponentName=ISP/i17isp1_ISP_00, EppAction=START_REPORT, StatementExecutionID=1407389071349012
[37858]\{300841\}[-1/-1] 2024-10-14 14:37:01.358015 e SQLSession       sm_stmt_context_part_token.cc(00121) : Checksum wasn't matched : Actual checksum=1795098501, Expected checksum=2402748354
[37858]\{300841\}[-1/-1] 2024-10-14 14:37:01.358185 e SQLSession       sm_handler.cc(03321) : ===== START OF SESSION DUMP ======================
[37858]\{300841\}[-1/-1] 2024-10-14 14:37:01.358192 e SQLSession       sm_handler.cc(03322) : CHANNEL      : (sockfd:1204, part:389) open_time=3170481358 ms, exp_size(header)=400, act_size(buffer)=400
[37858]\{300841\}[-1/-1] 2024-10-14 14:37:01.358201 e SQLSession       sm_handler.cc(03323) : ACTION       : name=ExecutePrepared, message_type=EXECUTE, stocked_error_code=1033, scrollable=0, oabap_stream=0
[37858]\{300841\}[-1/-1] 2024-10-14 14:37:01.358209 e SQLSession       sm_handler.cc(03324) : CLIENT       : <client_host_address>:<client_port_number>(pid=3938), client_library=SQLDBC 2.13.22.1657658317, client_program=ABAP:ISP
[37858]\{300841\}[-1/-1] 2024-10-14 14:37:01.358216 e SQLSession       sm_handler.cc(03325) : PROTOCOL     : 4.1, internal_session_id=1431760700140091, packet_count(message_id)=2108367, version_exchanged=1, authenticated=1
[37858]\{300841\}[-1/-1] 2024-10-14 14:37:01.358223 e SQLSession       sm_handler.cc(03326) : DISTRIBUTION : mode=2, version=6
[37858]\{300841\}[-1/-1] 2024-10-14 14:37:01.358226 e SQLSession       sm_handler.cc(03327) : ROUTING      : anchor=300841, primary=300841, own=300841, update_tid=0, A/A_origin_site_type=0, A/A_origin_conn=0, A/A_protocol_version=2
[37858]\{300841\}[-1/-1] 2024-10-14 14:37:01.358447 e SQLSession       sm_handler.cc(03371) : (37858:1204) received msg: 400 / 400
...
[37858]\{300841\}[-1/-1] 2024-10-14 14:37:01.358459 e SQLSession       sm_handler.cc(03329) : ===== END OF SESSION DUMP ======================== 

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 1.0
• SAP HANA, platform edition 2.0 

Checksum wasn't matched ; SQL code: 1033; sm_stmt_context_part_token; SQL 1033 , KBA , HAN-DB , SAP HANA Database , HAN-DB-SEC , SAP HANA Security & User Management , Problem