DM1823E - Log file has reached its saturation point

20 March,2010 by Tom Collins

This set of messages appeared as separate , but in a row - which indicates it's one underlying problem

ADM1822W  The active log is being held by dirty pages.
DM1823E  The active log is full and is held by application handle 
  "79".  Terminate this application by COMMIT, ROLLBACK or FORCE 
Log File has reached its saturation point"
  DIA8309C Log file was full.

 There is an  DB2 error message indicating that the transaction log for the database is full.

Cause: The LOGFILSIZ_DB2 parameter is set too low.

Solution: Increase the LOGFILSIZ_DB2 parameter using the following command:

db2 update database configuration for myDB using LOGFILSIZ 10000

Ensure that there is enough file space in the DB2 instance owner's home directory.

Author: Rambler(


Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment on DM1823E - Log file has reached its saturation point

Comments are moderated, and will not appear until the author has approved them. | DB2 Performance Tuning | DBA DB2:Everything | FAQ | Contact | Copyright