Symptom
Page level corruption is the most common form of corruption faced with SAP HANA. There a number of clear indicators when you are facing page level corruption:
- <service>_<host>.<port>.rtedump.<timestamp>.page.trc dumps are created in your trace folder.
- <host>_<service>.perspage.<timestamp>.<logical_page_id>L.<file_pos_4k>P.0.corrupt.dmp are created in your trace folder.
- You may also encounter Wrongchecksum errors in your applications and in your SAP HANA service traces:
- Wrong checksum: Calculated <calc_checksum> with checksum algorithm <algorithm>, stored <act_checksum>.; $lpno$=<log_pageno>; $ppno$=<phys_pageno
- Wrong savepoint version: Expected <expected_savepoint_version> but found <actual_savepoint_version>
- Invalid checksum algorithm <act_checksum>.; $verifiedForInternalReorganization$=false; $ppno$=<phys_pageno>
Read more...
Environment
SAP HANA, platform edition
Product
SAP HANA, platform edition all versions
Keywords
HANA corruption, .page.trc, .corrupt.dump. page corruption, wrong checksum, physical corruption, disks, flipped bits, lost writes, hardware failure , KBA , HAN-DB , SAP HANA Database , HAN-DB-PER , SAP HANA Database Persistence , 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.