SAP Knowledge Base Article - Preview

3369899 - "SQL code: -10512" occurred while accessing table "<TableName>"

Symptom

  • Following ABAP Dump is observed in ST22 on a SAPGUI client , during attempts to insert records on a target HANA DB table :
Category               ABAP programming error
Runtime Errors         DBSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
ABAP Program           SAPLBSVU
Application Component  CA-GTF-TS-SMT
Date and Time          08.08.2023 10:00:04 (CET)
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Short Text                                                                                        |
|    SQL error "SQL code: -10512" occurred while accessing table "JEST".                           |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|What happened?                                                                                    |
|    Database error text: "SQL message: Row not processed due to previous error"                   |
----------------------------------------------------------------------------------------------------

..........

----------------------------------------------------------------------------------------------------
|Database Interface Information                                                                    |
----------------------------------------------------------------------------------------------------
|C|E|status of row 2/2, status=-2, rc=-10512 [D:/depot/bas/789_REL/src/dbs/hdb/dbsdbsql.cpp#3835]  |
|C|E|  execute() of C_0291, #rec=0, rc=1, rcSQL=-10512 [D:/depot/bas/789_REL/src/dbs/hdb/dbsdbsql.c|
|C|E|EXECUTE C_0291 on connection 0, rc=-10512 [D:/depot/bas/789_REL/src/dbs/hdb/dbslsdb.cpp#8619] |
|C|1|SQLCODE    : -10512 [D:/depot/bas/789_REL/src/dbs/hdb/dbsdbtrc.cpp#610]                       |
|C|1|SQLERRTEXT : Row not processed due to previous error [D:/depot/bas/789_REL/src/dbs/hdb/dbsdbtr|
|C|1|sc_p=000001EE71175E80,no=291,idc_p=000001EE711AF710,con=0,hit=3,cnt=138,act=1,slen=116,smax=25|
|C|1|prepared=0,lastPrepareTime=20230808100005,nativeSQL=0,ignoreStmtId=0 [D:\depot\bas\789_REL\src|
|C|1|statementHash=1fefd028748a97626d3c6cccc68dddc5 [D:\depot\bas\789_REL\src\dbs\hdb\dbsdbsql.h#21|
|C|1|stmtid = <13/JEST                                    /0/20230724233913> [D:/depot/bas/789_REL/|
|C|1|stmtid = <0/SAPLBSVU                                /105906628/20210908091953> [D:/depot/bas/7|
|C|1|INSERT INTO "JEST" ( "MANDT" , "OBJNR" , "STAT" , "INACT" , "CHGNR" , "_DATAAGING" ) VALUES( ?|
|C|1| ? , ? , ? , ? ); [D:/depot/bas/789_REL/src/dbs/dbfun/dbsc.c#2992]                            |
|B|E|***LOG BY4=> sql error -10512 performing INS on table JEST [dbdbslst#5742]                    |
|B|E|***LOG BY0=> Row not processed due to previous error [dbdbslst#5742]                          |
|B|1|DbDbslStatement::handleDbslRc: dbsl_rc=99, exeception=CX_SY_OPEN_SQL_DB_Sql_Error, program=LBS|
----------------------------------------------------------------------------------------------------

  • indexserver trace files reveal the underlying reason for the failed insert 

[38431]\{216481\}[54/20878698] 2023-08-08 04:04:47.369943 i TraceContext     TraceContext.cpp(01347) : UserName=SAPHANADB, ApplicationUserName=<>, ApplicationName=ABAP:PRD, ApplicationSource=SAPLV50U:686, Client=100, StatementHash=f3314da4a00f046f842cd54bd8c579b9, EppRootContextId=005056BC64841EDBB7F73C49F58720D8, EppTransactionId=8C0B670201460280E0064D0BBEFF3AEC, EppConnectionId=00000000000000000000000000000000, EppConnectionCounter=0, EppComponentName=PRD/hostname, EppAction=<>, StatementExecutionID=844434236350432
[38431]\{216481\}[54/20878698] 2023-08-08 04:04:47.369943 e table_update     TableUpdate.cpp(03960) : execute_context() caught exception for table SAPHANADB:JEST, rc=301: ERROR [SQL-301] unique constraint violated: Table(/1CADMC/00000216), Index(/1CADMC/00000216~0) with error: unique constraint violation on pos=1 for table PRD::SAPHANADB:/1CADMC/00000216en, key: IUUC_SEQUENCE=76468 already exists as udiv=2063688; indexname=/1CADMC/00000216~0 at SQLUpdate/Storage/Impl/ColumnStorageChange.cc:210
exception  1: no.71000301  (SQLUpdate/Storage/Impl/ColumnStorageChange.cc:210) TID: 38431
    Table(/1CADMC/00000216), Index(/1CADMC/00000216~0) with error: unique constraint violation on pos=1 for table PRD::SAPHANADB:/1CADMC/00000216en, key: IUUC_SEQUENCE=76468 already exists as udiv=2063688; indexname=/1CADMC/00000216~0
NO exception throw location recorded. Stack generation suppressed.
exception type information:
 - 0: public ptime::SQLException@0x00007fb115e5e370 SI
   - 0: public ptime::SQLExceptionBase@0x00007fb115e5d1a8 SI
     - 0: public Diagnose::SQLExceptionBase@0x00007fb115e5b800 SI
       - 0: public ltt::exception@0x00007fb0ed1bd878


 

[11264]{243500}[66/22629029] 2023-08-08 18:33:57.959766 e table_update     TableUpdate.cpp(01279) : trace_basics called from 'setLastError', this=0x00007f90db9f9400, *getPreparedInfo()=0x00007f86da7b1f80, table 'SAPHANADB:JEST', action=UPDATE
, flags=46181098979328, itsUseRowIds=0, itsIsChunkWise=0, itsUseBatchUpdate=1, itsAcquireRowLocks=1, itsColumnEntriesChangeKey=0, beforeTriggerChangeKey=0, numRows (if set) =2
[11264]\{243500\}[66/22629029] 2023-08-08 18:33:57.959771 e table_update     TableUpdateTrace.cpp(00288) : trace_trans: TransactionId=22629029, own ConsistentView=CVID=140154872523104 RefCnt=1 MVCCCV[snapshot=22852028,own=TS[tcbidx=1759,ssn=any],tcb=TCB[ACTIVE,refcnt=4,tempTS=TS[tcbidx=1759,ssn=3],commitTS=9223372036854775807,transactionID=22629029,pseudoTransactionID=-1,hasCursor=false,factory=default]@0x00007f962e4ca150]
[11264]\{243500\}[66/22629029] 2023-08-08 18:33:57.959779 e table_update     TableUpdateTrace.cpp(00266) : executed statement: 'UPDATE "JEST" SET "INACT" = ? , "CHGNR" = ? , "_DATAAGING" = ? WHERE "MANDT" = ? AND "OBJNR" = ? AND "STAT" = ?', user: 'SAPHANADB',  called from 'setLastError'
[11264]\{243500\}[66/22629032] 2023-08-08 18:33:58.018053 i TraceContext     TraceContext.cpp(01347) : UserName=SAPHANADB, ApplicationUserName=BATCH, ApplicationName=ABAP:PRD, ApplicationSource=SAPLOS_UPDATE_TASK:126, Client=100, StatementHash=f3314da4a00f046f842cd54bd8c579b9, EppRootContextId=005056BC64841EDD94F1DC792E09A0EE, EppTransactionId=8C0B670201460280E0064D20217DDD00, EppConnectionId=00000000000000000000000000000000, EppConnectionCounter=0, EppComponentName=<instance_name>, EppAction=<>, StatementExecutionID=844434662093267
[11264]{243500}[66/22629032] 2023-08-08 18:33:58.018053 e table_update     TableUpdate.cpp(03960) : execute_context() caught exception for table SAPHANADB:JEST, rc=301: ERROR [SQL-301] unique constraint violated: Table(/1CADMC/00000216), Index(/1CADMC/00000216~0) with error: unique constraint violation on pos=1 for table PRD::SAPHANADB:/1CADMC/00000216en, key: IUUC_SEQUENCE=94930 already exists as udiv=273762indexname=/1CADMC/00000216~0 at SQLUpdate/Storage/Impl/ColumnStorageChange.cc:210
exception  1: no.71000301  (SQLUpdate/Storage/Impl/ColumnStorageChange.cc:210) TID: 11264
    Table(/1CADMC/00000216), Index(/1CADMC/00000216~0) with error: unique constraint violation on pos=1 for table PRD::SAPHANADB:/1CADMC/00000216en, key: IUUC_SEQUENCE=94930 already exists as udiv=273762; indexname=/1CADMC/00000216~0
NO exception throw location recorded. Stack generation suppressed.
exception type information:
 - 0: public ptime::SQLException@0x00007fb115e5e370 SI
   - 0: public ptime::SQLExceptionBase@0x00007fb115e5d1a8 SI
     - 0: public Diagnose::SQLExceptionBase@0x00007fb115e5b800 SI
       - 0: public ltt::exception@0x00007fb0ed1bd878

 

 

  • The "/1CADMC/00000216" is an SLT replication table for target table "JEST"

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

SAP HANA Platform Edition 2.0       

Product

SAP HANA, platform edition 2.0

Keywords

KBA , HAN-DB , SAP HANA Database , CA-LT-SLT , SAP Landscape Transformation Replication Server (SLT) , 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.