SAP HANA Forum
What are common errors reported by CHECK_TABLE_CONSISTENCY?
Kindly share your valuable views here.
Thanks in advance.
In general you should execute the consistency check another time on a table with critical errors. If the error isn't reproducible, it was most likely a timing issue in combination with concurrent workload, and so the error can be ignored. If the error is reproducible and can't be eliminated with a save workaround, it is recommended to open a SAP incident in order to request assistance.
The following table lists popular errors and provides some further details like criticality or possible cleanup activities:
no error found
This entry indicates that a consistency check finished without errors.
Could not replay delta log for table <schema>:<table>: exception during deltalog replay. See trace file for more information
Could not replay delta log for table <schema>:<table>: Attribute engine function not implemented
This error indicates a critical delta storage related inconsistency. The message "attribute engine function not implemented" is displayed when an INVERTED HASH index (SAP Note 2109355) is used on a table with paged attributes and data aging.
Retry exceeded maximum
This error is normally caused by a high workload on the underlying index.
Schedule CHECK_TABLE_CONSISTENCY runs at times of low activity on the system in order to minimize the occurrences of this error.
Failed to lock table <schema>:<table> for consistency check: ERROR [CODE-2561] distributed metadata error: cannot find table object
This error indicates that the underlying table was dropped in parallel to CHECK_TABLE_CONSISTENCY, e.g. because it was a temporary table.
table does not exist
metadata version changed while running checks: <from> -> <to>
This error indicates that the underlying table was adjusted with a DDL operation in parallel to CHECK_TABLE_CONSISTENCY. As a consequence you can't rely on the result of the consistency check for this table.
Key column value is NULL at udiv <udiv> in <schema>:<table>
This error indicates that NULL values exist in the primary key, what is generally not allowed. If there are NULL combinations in the underlying columns, you can repair this inconsistency by recreating the primary key. Otherwise you have to analyze and resolve the NULL values in the underlying columns.
Found duplicate primary key <key>
This error indicates that duplicate values exist in the primary key, what is generally not allowed. If there are no duplicate combinations in the underlying columns, you can repair this inconsistency by recreating the primary key. Otherwise you have to analyze, combine and remove duplicate combinations in the underlying columns.
Corrupt value at udiv <udiv>
This error indicates a wrong value in a CONCAT attribute. Technically this corruption can be repaired by dropping and recreating the involved CONCAT attribute. It is recommended to perform an analysis beforehand, because in the worst case (CONCAT attribute correct, underlying columns wrong) the recreation of the CONCAT attribute will remove the correct values and overwrite them with wrong values from the underlying columns.
See SAP Note 1986747 for more information regarding CONCAT attributes.
Found NULL rowid at udiv <udiv> in <schema>:<table>
This error indicates a NULL value for the $rowid$ of a record.
Duplicate rowid <rowid> at udivs <udiv1> and <udiv2> in <schema>:<table>
This error indicates a duplicate $rowid$ values. This problem may happen with the history partition of an in-memory optimized DSO. SAP generally recommends not to use in-memory-optimized DSOs.
Could not retrieve maximum rowid in <schema>:<table>
This error indicates problems evaluating the maximum $rowid$ values.
Maximum rowid in table (<max_rowid1>) is larger than max rowid in runtime data (<max_rowid2>) in <schema>:<table>
Externalkey concat at udiv <id> is not equal to value computed from key columns (<key_column_list>) in <schema>:<table>
This error indicates an inconsistency between the primary key and the underlying individual primary key columns. Technically this inconsistency can be repaired by recreating the primary key. It is recommended to perform an analysis beforehand, because in the worst case (primary key correct, underlying columns wrong) the recreation of the primary key will remove the correct values and overwrite them with wrong values from the underlying columns.
Consistency check failed for disk lob
A hybrid LOB on disk is corrupted. See SAP Note 2220627 for more information related to SAP HANA LOBs.
The partition specification is invalid. The table has a primary key. RoundRobin is only allowed for tables without primary keys.
Make sure that tables with ROUNDROBIN partitioning doen't have a primary key defined.
At least one replicate does not match the master replicate.
An inconsistency exists in the area of table replication. You can correct the inconsistency be re-establishing a table replication from scratch.
This error indicates a problem with a table column.
Found invalid v-slot binding while checking sid=<sid>
This error can be a consequence of changes in the row store table handling as of SAP HANA SPS 07 See SAP Note 1997637 for more details.
Found unseparated v-slot;sid=<sid>
This error indicates that metadata was found at an unexpected position in memory.
Found invalid length value;sid=<sid>
This error is a consequence of column values being longer than the defined column length. Check and - if possible - adjust the field lengths or field values to make both consistent.
Found NULL at udiv <udiv>, rowid <rowid> for <schema>:<table>
broken not null constraint; rowid=<rowid>
This error indicates that a NULL value was found in a NOT NULL column.
IndexMgr: index not found
This error is reported by lower SAP HANA layers rather than CHECK_TABLE_CONSISTENCY. It indicates that a table exists in metadata, but it is not physically accessible. TABLES lists the column table, but M_CS_TABLES doesn't show it.
This situation can be a consequence of errors like "Table.cpp(00111) : Exception in Table::Table <table_name>" and a restart of the nameserver may resolve the issue.
Sign up for STechies