Scribd
Upload
3 views2 pages

SAP HANA Log Volume Full

The document addresses issues related to SAP HANA log volume becoming full on secondary or tertiary sites during system replication, highlighting common causes such as stuck savepoints and network interruptions. It provides a resolution process including checking log segment status, identifying space consumption by services, and releasing log segments using specific commands. The importance of addressing the root cause to prevent recurrence is emphasized, along with references to relevant SAP notes for further guidance.

Uploaded by

ksundarr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
3 views2 pages

SAP HANA Log Volume Full

The document addresses issues related to SAP HANA log volume becoming full on secondary or tertiary sites during system replication, highlighting common causes such as stuck savepoints and network interruptions. It provides a resolution process including checking log segment status, identifying space consumption by services, and releasing log segments using specific commands. The importance of addressing the root cause to prevent recurrence is emphasized, along with references to relevant SAP notes for further guidance.

Uploaded by

ksundarr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 2
[D7 SAP Knowledge Base Arle 2409471 - SAP HANA Log Volume Full on Secondary or Tertiary Site with System Replication Component: HAN-DB-HA (SAP HANA > SAP HANA Database > SAP HANA High Availability (System Replication, DR, ete.)), Version: 16, Released On: 09.04.2024 | Symptom + Receiving alerts that log volume is reaching full; + Secondary or tertiary database is going to a hung status; | Environment SAP HANA, platform edition | Cause + HANA Log volume can be full due to various reasons. You can refer to SAP Note 2083715 to find more about the cause, but most commonly the secondary system becomes full due to: © Savepoints getting stuck; © Bad 1/0 in secondary/tertiary; © Network interruptions; © Service erashdumps on secondary; © Less memory on secondary site so services are either crashing or constantly performing resman shrinks and so are not able to keep up with replication and logs are accumulating. + It is important to find why the log volume became full. The steps of this article will help release the log space but if their is an underlying issue such as the above situations, itis highly likely that the log volume will become full again, | Resolution ‘The purpose of this KBA is not for analyzing the log volume full situation, but to prevent or resolve such situation especially in Secondary ‘Tertiary systems. 1. First check the log segment status by executing following command on each of the log volume directories. It will give you a count of number of free log segments that are in status FREE. © HOST:/ust/sap//SYS/global/hdb/custom/config> hdblogdiag seglist /hana/log//mntoooXX/hdbo000X.0000X | grep -oP ‘\bFree\b' | we-1 2. You can also run "du" command to obtain which service's log volume has consumed higher disk space. It will give the used space in GB and so you can determine which service has consumed higher space by correlating its volume. © HOST:/hana/log//mntoooXX> du -sh /hana/log//mntoooXX/* 3. Ifyou are seeing higher count in hdbindexserver volume, run the corresponding log release command like: hdbeons ‘log release! 4, Ifyou are seeing higher count in service other than indexserver, e.g nameserver, OR, if the issues happens on multiple indexservers, you may follow steps below. © Find the PID of the service from OS level: ps -ef | grep hdb © Connect to the service: hdbcons -p © Release the log segments: log release Exit from hdbcons: exit «Repeat step 2) ~ 4) for the remaining problem HANA services. © Please note that we cannot connect to HDBSQL or run SQL. command in secondary system. This is the reason we use HDBCONS utility. This should reclaim the log space and this operation will take some time and will not finish immediateh If this does not reclaim the space, you will have to either follow SAP Note 1679938 or in worst case disable and reconfigure the system replication again as per the Resolution part of the KBA 2821539 - Volume /hana/log is full with Jog segments in status RetainedFree 6, It is important that you have found and resolved the root cause for the log volume full situation as per the steps in the note 2083715 - Analyzing log volume full situations, so that you don't face the issue again | Keywords logsegment, disk full, no disk space, secondary site, no free space, Free, system replication | Attributes Key Value Other Components SAP HANA > SAP TIANA Database > SAP IIANA Database Persistence (1AN-DB-PER) | Products Produets SAP HANA 1.0, platform edition SAP HANA, platform edition 2.0 | This document refers to SAPNote/KBA Component ‘Title 2821539 HAN-DB-HA Volume /hana/log s full with log segments in status RetainedFree 2083715 HAN-DB ‘Analyzing log volume full situations 1679938 HAN-DB DiskéullEvent on Log Volume | This document is referenced by SAP Note/KBA Component Title 3047379 Monitoring hana/log volume consumption

You might also like