3694999 - SAP HANA Recovery fails or becomes very slow when log backups are corrupt or backup catalog growth affects recovery

During RECOVERY RECOVER DATA or point-in-time recovery, SAP HANA database recovery fails with Out-of-Memory (OOM) errors or becomes extremely slow, although sufficient physical memory is available and the system size has already been increased.

Typical symptoms include:

• Recovery terminates with
  RECOVERY RECOVER DATA finished with error: [448] recovery could not be completed
• Errors indicating corrupted log backups, for example:
  • [110059] The backup … is corrupt
  • [3040118] Invalid buffer header found in log segment
• Backint errors such as:
  • [110507] Backint exited with exit code 87 instead of 0
• Restore progress is extremely slow during log replay
• OOM dumps generated during recovery
• Additional internal processing errors may be reported during recovery, depending on the affected backup chain and system state.

SAP HANA DB Version 2.0

hana database recovery, oom error, recovery could not be completed, invalid buffer header, corrupt backup, slow restore, log backup, hdbbackupcheck, backup housekeeping, reclaim log, memory pressure, out-of-memory dumps, sap hana backup recovery , KBA , HAN-DB-BAC , SAP HANA Backup & Recovery , Problem