Skip to main content

SAP BASIS tips how to deal with SAP HANA log full situation DiskFullEvent on Log Volume

You observe that the log volume has reached its capacity, causing the database to reject any new incoming requests.And the SAP ERP system or S/4 HANA system is hanging.

To determine whether the operating system path is full, you can use commands such as df -h or bdf to check the disk space usage.👀

Reason:

Due to an architectural limitation, SAP HANA cannot perform a log backup when the log area is completely full, leading to potential system unresponsiveness or failure to start.

Affected Releases:

  • SAP HANA 1: All revisions.

  • SAP HANA 2: Revisions from SPS00 to SPS05.

Prerequisites:

  • The log volume is full, causing the database to become unresponsive or fail to start.

Solution:

Upgrade to one of the following SAP HANA revisions:

  • SAP HANA 2: Revisions >= 060.00 (SPS06) or higher.

Workaround:

If upgrading is not immediately possible, follow these steps to resolve the issue:

  1. Log in as <SID>adm User:
    Ensure you are logged in as the <SID>adm user on the host experiencing the log volume full issue.

  2. Stop the Database:
    Execute the following command to stop the database:

    bash
    /usr/sap/hostctrl/exe/sapcontrol -nr <instance_number> -function StopSystem HDB

    Wait until the database on all hosts is completely stopped.

  3. Navigate to the Log Volume Directory:
    Change to the mnt00001 directory of the log volume (default path: /hana/log/<SID>/):

    bash

    cd /hana/log/<SID>/mnt00001

  4. Free Up Space in the Log Volume:

    • Identify a log volume consuming at least 2 GB of space using:

      bash

      du -sh *

    • Move the identified log volume (e.g., hdb00003) to a location with sufficient space, such as the data volume (default: /hana/data/<SID>):

      bash

      mkdir /hana/data/<SID>/logs_temporary
mv hdb00003 /hana/data/<SID>/logs_temporary

  5. Create a Symbolic Link:
    Create a symbolic link to the moved log volume in its original location:

    bash

    ln -s /hana/data/<SID>/logs_temporary/hdb00003 /hana/log/<SID>/mnt00001/hdb00003

  6. Start the Database:
    Start the database using:

    bash

    /usr/sap/hostctrl/exe/sapcontrol -nr <instance_number> -function StartSystem HDB

    Wait for log backups to complete.

  7. Reclaim Log Space:
    Execute the following SQL statement on both the SYSTEMDB and tenant level to clean up the log volume:

    sql

    ALTER SYSTEM RECLAIM LOG;

  8. Stop the Database Again:
    Stop the database once more:

    bash

    /usr/sap/hostctrl/exe/sapcontrol -nr <instance_number> -function StopSystem HDB

    Ensure the database is fully stopped on all hosts.

  9. Remove the Symbolic Link and Restore the Log Volume:

    • Remove the symbolic link:

      bash

      rm -f /hana/log/<SID>/mnt00001/hdb00003

    • Move the log volume back to its original location:

      bash

      mv /hana/data/<SID>/logs_temporary/hdb00003 /hana/log/<SID>/mnt00001

    • Delete the temporary log folder:

      bash

      rmdir /hana/data/<SID>/logs_temporary

  10. Restart the Database:
    Start the database again:

    bash

    /usr/sap/hostctrl/exe/sapcontrol -nr <instance_number> -function StartSystem HDB

Summary:

This workaround temporarily frees up space in the log volume by relocating a portion of it, allowing the database to start and perform log backups. After reclaiming log space, the log volume is restored to its original state. However, upgrading to SAP HANA 2 SPS06 or higher is the recommended long-term solution to avoid this issue.

Comments

Post a Comment

Popular posts from this blog

MMPV_DATE_CHECK: Error occurred (SAP Note 1082841) how to solve

SAP Note 1082841 - MMPV/Close Periods : Prevent shifting to a future period by mistake You must backup the database before executing following program or function in the Production system! Symptom When running MMPV/ Close Periods, prevent shifting to a future period by mistake (for example, a common mistake is running MMPV twice at the beginning of a month). Other Terms MMPV, MMPI, MARV, period roller, period shift, material ledger, MMPV_READ_NOTE, MMPV_DATE_CHECK, T001, PERIV Reason and Prerequisites In the event that MMPV is mistakenly executed twice at the beginning of a period, the active period could be shifted to a future period. As a consequence, system would accept goods movements with a posting date pointing to this wrong future period. To revert wrong period shift and correct such posting errors is difficult, especially when Material Ledger is active. Solution This note provides a feature to prevent using MMPV to shift into a future period.  The future period is defi...
Post a Comment
Read more

SAP How to mass close open sales orders (Partially or Not Executed)

Sometimes we need to mass close open sales orders (Partially or Not Executed). Using VA02 to close them one by one is inefficient. Method 1: You can use the TCODE MASS . Method 2: You can also use the  TCODE VKM4  to close all open orders. Firstlly use VA06 to choose what SO you wana to mass close, then copy the SO number to VKM4, and execute. Select all item and click Reject.
Post a Comment
Read more

SAP Error message FPUIFB086: Could not start Layout Designer (see long text) Please read SAP Note 1121176

SAP Error message FPUIFB086: Could not start Layout Designer (see long text) It means SAP require to open Adobe LiveCycle Designer locally. But your PC do not install any version of Adobe LiveCycle Designer. Form SAP Note 1121176 is obsoleted, and LiveCycle Designer 8.0 is quite an old release and newer Windows operating systems are not supported (for example Windows 7/Windows 8). Please use Designer 9.8 (SAP note 1658830) or higher instead of Designer 8.0. SAP Note 1658830 Adobe LiveCycle Designer 9.8 - Installation Symptom You want to install Adobe LiveCycle Designer (LCD) 9.8 on your local computer or upgrade your existing installation. Other Terms Adobe Document Services, ADS, Adobe LiveCycle Designer, SAP Interactive Forms by Adobe, PDF form Reason and Prerequisites You can use Adobe LiveCycle Designer 9.8 with the following versions of Adobe Document Services (ADS): SAP NetWeaver 7.31 and higher For lower releases of SAP NetWeaver, see SAP Note 1317925. This describes the ret...
Post a Comment
Read more

Newest version of Adobe LiveCycle Designer 11.0 download

As SAP Note 1121176  descripts, Adobe LiveCycle Designer 8.0 is quite an old release and newer Windows operating systems are not supported (for example Windows 7/Windows 8). Please use Designer 9.8 (SAP note 1658830) or higher instead of Designer 8.0. The newest version of Adobe LiveCycle Designer is 11.0.  SAP release a patch at 17.07.2024. PL 28 for ADOBE LIVECYCLE DESIGNER 11.0 Adobe LiveCycle Designer 11.0 Click here to download. PL 28 for ADOBE LIVECYCLE DESIGNER 11.0 Click here to download.
Post a Comment
Read more