Tuesday 23 June 2020

2083715 - Analyzing log volume full situations

HANA Log volume can be full due to various reasons

below are a few important reasons

1: The disk usage of log volumes only grows, if there are no more segment files available for overwriting/re-use ( having state FREE, see Database view  M_log_segments).

 Log segments are available for re-use when they have been successfully backed up (in log_mode = normal) and are not required for a database restart. Aim of this SAP Note is to help you identify the root cause, why log segments are not getting freed, and remain in state TRUNCATED (indicating that the log-segment has not yet been backed up successfully). In a log volume full situation, no free log-segments are available for re-use & no more new log segments can be allocated due to limited disk quota/size, thus the database cannot be started or stops accepting requests. Apart from bringing the system up again as soon as possible, the root cause needs to be investigated and resolved. Otherwise, you may run into a log volume full situation again soon.

2: SAP HANA Log Volume Full on Secondary or Tertiary Site with System Replication

sap note 20837