Skip to Content

Log file has reached its saturation point

Hello SAP Gurus,

I got the follow error in DB2 Database: "Log file has reached its saturation point". When i try to take a full backup the database no make it, also try to shutdown database and neither.

Someone knows, how can i resolve this issue?

Enclose image

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Dec 10, 2015 at 10:51 PM

    Hi Anderson

    It will be difficult to give exact recommendation with out complete db2daig.log information. Based on info from attached screenshot, noticed that you are hitting transaction log full case.

    This could be because either all the logs files LOG_PRIMARY and LOG_SECOND number of files reached limit (or) Total logspace allocated might exhausted. You need to check these values first.

    In such cases, I am afraid you need to issue DB2FORCE, but this will trigger abrupt showdown of DB.
    During restart of DB it need crash recovery to bring system to consistent status. As there could be longest transaction running without commit, DB needs to Roll Forward all the active log files. This roll forward must finish with out interruption.

    You can find lots of scenarios regards to such transaction log full cases.

    In future to avoid such DB stuck cases you need to set these DB parameter MAX_LOG or NUM_LOG_SPAN parameters as per SAP Note : 495297.

    Hope my info helps

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 11, 2015 at 11:09 AM

    Hi Anderson,

    just try to clear the log files in db2/<SID>/log_dir/NODE0000 path and try again.

    please tell if it has worked.


    Narendran V

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Anderson,

      This is because one of the processes has consumed log files (Primary+Secondary)

      You can find this by below commands..

      1. Command to get the current secondary log allocation

      $ db2 get snapshot for database on <DBSID> | grep -i 'allocated currently'

      2. Command to get the details on oldest transaction consuming secondary log

      $ db2 get snapshot for database on <DBSID> | grep -i oldest

      3. Command to get the SAP work process ID

      $ db2 get snapshot for application agentid <agentid> | grep -i 'Process ID'

      Here agent id is the one returned from point 2 (olderst)

      If the process is still running you will have to either terminate it or allow it to complete bu increasing the secondary log.

      To change the secondary log

      $ db2 connect to <DBSID>

      $ db2 update db cfg using logsecond xx immediate

      Hope this helps you.

      Further you can try to increase the log file numbers, log file size or setting NUM_LOG_SPAN accordingly.



  • Posted on Dec 12, 2015 at 05:49 AM


    To get the issue resolved, we need firstly find out the root cause.

    KBA#2141933 should help with intiial analysis.
    2141933 - DB6: How to initially trouble shoot transaction log full issue

    By the way, in any case, please never do manual 'touch' on the transaction log path. Otherwise, it may cause expected result, which is much more servere than the log full issue itself.

    Kind regards

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.