SAP Knowledge Base Article - Preview

3467934 - "AttributeStoreFile error while deserializing from file" due to corrupt persistency page

Symptom

An ABAP dump similar to the following is encountered:

Category               External Error
Runtime Errors         DBSQL_SQL_INTERNAL_DB_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          <date> <timestamp>
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Short Text                                                                                        |
|    SQL error "SQL code: 129" occurred while accessing table "<table_name>".                      |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|What happened?                                                                                    |
|    An internal error has occured on the database while preparing or                              |
|    executing an SQL command. You can find more details from the SQL                              |
|    error.                                                                                        |
|                                                                                                  |
|                                                                                                  |
|    Database error number: SQL code: 129                                                          |
|    Database error text: "SQL message: transaction rolled back by an internal                     |
|     error: AttributeStoreFile error while deserializing from file                                |
|     '<schema>:<table>.<column_name>': AttributeEngine: error reading file filepos              |
|     135399709109792 buffer mode paged null size 0 pos 135399707500544 end nul"                   |
----------------------------------------------------------------------------------------------------

Reviewing the indexserver service database trace, you notice a trace entry similar to the following:

[13630]\{200840\}[34/1792376701] <date> <timestamp> e LogicalPageAcces LogicalPageAccessImpl.cpp(02203) : handleFailedChecksumCheck: Page 0x1b80492L@DefaultPageAccess loaded from 0xa000018f2100P [0x18f2100000,1M,0] with incorrect checksum or header: exception  1: no.3020043  (DataAccess/PageAccess/impl/PageImpl.cpp:475) TID: 13630
    Wrong checksum: Calculated 151290010 with checksum algorithm 3 (CRC32), stored 1375601078.; $pno$=0x1b80492L; $ppno$=0xa000018f2100P [0x18f2100000,1M,0]


Read more...

Environment

  • SAP S/4HANA
  • SAP HANA, platform edition

Product

SAP HANA, platform edition all versions ; SAP S/4HANA all versions

Keywords

disk failure , KBA , 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.