SAP Knowledge Base Article - Preview

3394189 - HANA Index server trace files filled with "unique constraint violated" errors for different applications/tables


  1. HANA Index server trace files are spammed with "unique constraint violated" messages generated every few minutes for different applications/tables and you want to prevent this to reduce the trace file size and make it easier to use the trace files to troubleshoot other issues. 
  2. The messages in the Index server trace have the following format:
w SQLSession : (sockfd:731, channel:0x00007c2ce2fc6500, event:0x00007f0eb3a469c0, part:59) SQL exception occurred: code=301, 
message=unique constraint violated: Table(Table_Name) with error: unique constraint violation on pos=0 for table SID::SCHEMA_NAME:Table_NAME
key: $trexexternalkey$=3,010;4,GLT0;10,0000052305;4,0054;4,2023;0, already exists as udiv=6213 at



SAP HANA, platform edition


SAP HANA, platform edition all versions


sqlsession, warning, error, Default Trace Level , KBA , HAN-DB , SAP HANA Database , HAN-DB-ENG , SAP HANA DB Engines , 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.