Symptom
- You can get ST22 dump as follows:
===========================================================================
|Short Text |
| SQL error "SQL code: 129" occurred while accessing table "<TABLE_NAME>". |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened? |
| Database error text: "SQL message: transaction rolled back by an internal |
| error: An unexpected error occurred. For further information on this error |
| search SAP notes for one of the following tags: loc=0x807912de80d45817, |
| ctx=#################. ... |
----------------------------------------------------------------------------------------------------
===========================================================================
- In HANA DB indexserver trace file, the following error messages are reported:
===========================================================================
E SQLUpdate ChangeResult.h(00264) : The following assertion failed: !(units[rhs.beginOffset + unitCount] < 0 && rhs.units[unitCount] > 0) && !(units[rhs.beginOffset + unitCount] > 0 && rhs.units[unitCount] < 0)
left and right unit type (error or updated count) should be the same
Correlation id is 0x48b41d8750c71f68
...
e EmbeddedAPI Statement.cc(04652) : unhandled ltt exception was caught: conn_id=360615, stmt_id=##########, stmt_hash=<hash_ number_of_the_failed_dml_sql>, error=An unexpected error occurred. For further information on this error search SAP notes for one of the following tags: loc=$loctag$, ctx=$ctxtag$. If you don't find an according note, open a support ticket and include the trace files containing correlation id $corid$., sql=<SQL_statement_of_the failed_operation>
...
e EmbeddedAPI EAPICommon.cc(00153) : [SQL-129] unexpected exception at handlelttException_: exception=exception 1: no.2120042 (ChangeResult.h:264) TID: ######
An unexpected error occurred. For further information on this error search SAP notes for one of the following tags: loc=0x807912de80d45817, ctx=#############. If you don't find an according note, open a support ticket and include the trace files containing correlation id 0x48b41d8750c71f68.
...
===========================================================================
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Environment
- HANA 1.0
- HANA 2.0
Product
SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0
Keywords
0x807912de80d45817 , KBA , HAN-DB , SAP HANA Database , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview