Symptom
- The data volume reclaim failed with the following error while system replication was enabled
" * 2: general error: Shrink canceled, probably because of snapshot pages SQLSTATE: HY000 "
"SAP DBTech JDBC: [2]: general error: Reclaim failed: Cannot reclaim data volume partition #0 because one or more pages cannot be moved (reason: snapshot page)."
- There was no active snapshot in M_SNAPSHOTS
- The indexserver trace contains entries indicating a failed reclaim completion
2020-06-04 00:51:16.078011 w PhysicalPageAcce DataVolumePartitionImpl.cpp(00383) : Reclaim[0, '/hana/data/SID/mnt00001/hdb00004/datavolume_0000.dat']:<failed @ step #227>: sizes= (used= 2774403mb / max=7417152mb
| file= 7417152mb), curOverhead= 270%, maxOverhead= 255%, reason= 'Cannot reclaim DataVolume containing unmovable (snapshot) pages.' (9556.239s)
2021-11-07 11:00:02.688139 e PhysicalPageAcce DataVolumePartitionImpl.cpp(01470) : DVolPartCannot reclaim datavolume partition #0 to target overhead (120%) due to snapshot pages. Maximal superblock index in file(s) is 191225, maximal expected superblock index after reclaim should have been 53048
Read more...
Environment
SAP HANA, platform edition
Product
SAP HANA, platform edition all versions
Keywords
reclaim datavolume, snapshot, replication, shrink , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , HAN-DB , SAP HANA Database , 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.