What are Common Errors reported by CHECK_TABLE_CONSISTENCY?
In general, you should execute the consistency check again on any table displaying critical errors. If the error isn’t reproducible, it was most likely a timing issue due to concurrent workload, and it can generally be ignored. However, if the error is reproducible and cannot be resolved with a known workaround, it is recommended to open an SAP incident to request assistance.
The following table lists popular errors reported by CHECK_TABLE_CONSISTENCY and provides further details, such as criticality and possible cleanup activities.
| Error Code | Error String | Error Details | Severity | Description |
|---|---|---|---|---|
| 0 | no error found | This entry indicates that a consistency check finished without errors. | harmless | - |
| 5094 | ERROR_DELTA_REPLAY_FAILED | Could not replay delta log for table <schema>:<table>: exception during deltalog replay. See trace file for more information. | critical | This error indicates a critical inconsistency related to delta storage. The message "attribute engine function not implemented" is displayed when an INVERTED HASH index (SAP Note 2109355) is used on tables with paged attributes and data aging. |
| 5096 | ERROR_INDEX_SCAN_TIMEOUT | Retry exceeded the maximum. | harmless | This error is typically caused by a high workload on the underlying index. To minimize occurrences, schedule CHECK_TABLE_CONSISTENCY during low-activity times. |
| 5097 | ERROR_TABLE_LOCK_TIMEOUT | Failed to lock table <schema>:<table> for consistency check: ERROR [CODE-2561] distributed metadata error: cannot find table object | harmless | This error indicates that the underlying table was dropped in parallel with CHECK_TABLE_CONSISTENCY, possibly because it was a temporary table. Run the check during low-activity times to minimize occurrences. |
| 5098 | ERROR_CANNOT_PROCEED_TO_CHECK | Table does not exist. | harmless | Indicates that the underlying table was dropped in parallel with CHECK_TABLE_CONSISTENCY, likely due to being a temporary table. Running the check during low-activity times helps minimize occurrences. |
| 5099 | ERROR_METADATA_OUTDATED | Metadata version changed while running checks: <from> -> <to>. | harmless | Indicates that the underlying table was modified with a DDL operation parallel to CHECK_TABLE_CONSISTENCY. As a result, you can’t rely on the result of the check for this table. Run checks during low-activity periods. |
| 5100 | ERROR_PRIMARY_KEY_NULL | Key column value is NULL at udiv <udiv> in <schema>:<table>. | critical | NULL values exist in the primary key, which is generally not allowed. You can repair this by recreating the primary key, or by analyzing and resolving NULL values in the underlying columns. |
| 5101 | ERROR_PRIMARY_KEY_DUPL | Found duplicate primary key <key>. | critical | Duplicate values exist in the primary key, which is generally not allowed. If no duplicate combinations exist in the columns, recreate the primary key. Otherwise, analyze and remove duplicates in the underlying columns. |
| 5110 | ERROR_CONCAT_ATTRIBUTES_NULL | Corrupt value at udiv <udiv>. | critical | This error indicates a wrong value in a CONCAT attribute. Repair by dropping and recreating the CONCAT attribute. Perform an analysis beforehand, as recreating may overwrite correct values if the underlying columns are inconsistent. See SAP Note 1986747 for more information on CONCAT attributes. |
| 5120 | ERROR_ROWID_NULL | Found NULL rowid at udiv <udiv> in <schema>:<table>. | critical | This error indicates a NULL value for the $rowid$ of a record. |
| 5121 | ERROR_ROWID_DUPL | Duplicate rowid <rowid> at udivs <udiv1> and <udiv2> in <schema>:<table>. | critical | Duplicate $rowid$ values, often in the history partition of an in-memory optimized DSO. SAP generally recommends not using in-memory-optimized DSOs. |
| 5122 | ERROR_ROWID_NOMAX | Could not retrieve maximum rowid in <schema>:<table>. | critical | Problems evaluating the maximum $rowid$ values. |
| 5123 | ERROR_ROWID_RUNTIME | Maximum rowid in table (<max_rowid1>) is larger than max rowid in runtime data (<max_rowid2>) in <schema>:<table>. | critical | This inconsistency may be introduced by an SAP HANA upgrade to SPS 09. See SAP Note 2125399 for details. |
| 5130 | ERROR_PRIMARY_KEY_CONCAT_DIFF | External key concat at udiv <id> is not equal to value computed from key columns (<key_column_list>) in <schema>:<table>. | critical | Indicates inconsistency between the primary key and individual columns. Repair by recreating the primary key. Perform an analysis first to ensure the recreation does not overwrite correct values with incorrect data. |
| 5199 | ERROR_CHECK_FAILED | Consistency check failed for disk LOB. | critical | A hybrid LOB on disk is corrupted. See SAP Note 2220627 for more on SAP HANA LOBs. |
| 5204 | SPEC_NOT_VALID | The partition specification is invalid. The table has a primary key. RoundRobin is only allowed for tables without primary keys. | critical | Make sure that tables with ROUNDROBIN partitioning do not have a primary key. |
| 5209 | REPLICATE_INCONSISTENT | At least one replicate does not match the master replicate. | critical | An inconsistency exists in table replication. Re-establish the table replication to correct the inconsistency. |
| 5990 | ERROR_INVALID_FIELD | Invalid field; rowid=<rowid>; offset=<offset>; typeid=<typeid>. | critical | Indicates a problem with a table column. |
| 5991 | ERROR_VARIABLE_PART_BINDING | Found invalid v-slot binding while checking sid=<sid>. | critical | This could result from row store table handling changes as of SAP HANA SPS 07. Refer to SAP Note 1997637 for details. |
| 5993 | ERROR_METADATA_SEGMENT_SEPARATION | Found unseparated v-slot; sid=<sid>. | critical | Metadata was found at an unexpected position in memory. |
| 5995 | ERROR_LENGTH | Found invalid length value; sid=<sid>. | critical | This error is caused by column values that exceed the defined length. Check and adjust field lengths or values to correct the inconsistency. |
| 5996 | ERROR_NULLITY | Found NULL at udiv <udiv>, rowid <rowid> for <schema>:<table>. | critical | Indicates a NULL value in a NOT NULL column. |
| - | IndexMgr: index not found | - | critical | Reported by lower SAP HANA layers rather thanCHECK_TABLE_CONSISTENCY, this indicates a table exists in metadata but is not physically accessible. Restarting the nameserver may resolve this issue. |
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.
ERROR_DELTA_REPLAY_FAILED
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.
ERROR_INDEX_SCAN_TIMEOUT
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.
ERROR_TABLE_LOCK_TIMEOUT
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.
Schedule CHECK_TABLE_CONSISTENCY runs at times of low activity on the system in order to minimize the occurrences of this error.
ERROR_CANNOT_PROCEED_TO_CHECK
table does not exist
This error indicates that the underlying table was dropped in parallel to CHECK_TABLE_CONSISTENCY, e.g. because it was a temporary table.
Schedule CHECK_TABLE_CONSISTENCY runs at times of low activity on the system in order to minimize the occurrences of this error.
ERROR_METADATA_OUTDATED
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.
Schedule CHECK_TABLE_CONSISTENCY runs at times of low activity on the system in order to minimize the occurrences of this error.
ERROR_PRIMARY_KEY_NULL
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.
ERROR_PRIMARY_KEY_DUPL
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.
ERROR_CONCAT_ATTRIBUTES_NULL
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.
ERROR_ROWID_NULL
Found NULL rowid at udiv <udiv> in <schema>:<table>
This error indicates a NULL value for the $rowid$ of a record.
ERROR_ROWID_DUPL
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.
ERROR_ROWID_NOMAX
Could not retrieve maximum rowid in <schema>:<table>
This error indicates problems evaluating the maximum $rowid$ values.
ERROR_ROWID_RUNTIME
Maximum rowid in table (<max_rowid1>) is larger than max rowid in runtime data (<max_rowid2>) in <schema>:<table>
ERROR_PRIMARY_KEY_CONCAT_DIFF
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.
ERROR_CHECK_FAILED
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.
SPEC_NOT_VALID
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.
REPLICATE_INCONSISTENT
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.
ERROR_INVALID_FIELD
invalid field;rowid=<rowid>;offset=<offset>;typeid=<typeid>
This error indicates a problem with a table column.
ERROR_VARIABLE_PART_BINDING
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.
ERROR_METADATA_SEGMENT_SEPARATION
Found unseparated v-slot;sid=<sid>
This error indicates that metadata was found at an unexpected position in memory.
ERROR_LENGTH
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.
ERROR_NULLITY
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.