- Table Consistency Check (CHECK_TABLE_CONSISTENCY) reports error 5099 - Check skipped: metadata version changed while running checks: <from> -> <to>.
- In case the Table Consistency Check is run by an application job, it may complete successfully, but the error still appears in the result of consistency checks as table_consistency_check trace and monitoring view M_CONSISTENCY_CHECK_HISTORY_ERRORS.
In the table_consistency_check trace, there are the following entries:
tcc_result_w Request.cc(01186) : === Table consistency check request is constructed ===
tcc_result_w Request.cc(01188) : User name: SAPHANADB
tcc_result_w Request.cc(01401) : (Arg 1) Check Action: CHECK
tcc_result_w Request.cc(01405) : (Arg 2) Target Schema: All
tcc_result_w Request.cc(01406) : (Arg 3) Target Table: All
tcc_result_w Request.cc(02092) : Table consistency check request executed
tcc_result_w Request.cc(02275) : Errors are detected
tcc_result_w Request.cc(02276) :
SchemaName,TableName, ColumnName, ErrorCode, ErrorMessage, ActionName, AffectedCount, Details
SCHEMA,TABLE,,5099,Check skipped: metadata version changed while running checks: <from> -> <to>,CHECK,0,
- SAP HANA, platform edition 1.0
- SAP HANA, platform edition 2.0
checks, corruption, errors, inconsistencies, inconsistency, found , KBA , HAN-DB , SAP HANA Database , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.