DB2 10.5 for Linux, UNIX, and Windows
DB2 10.5 for Linux, UNIX, and Windows
This parameter can be set to prevent disk full errors from being generated when the DB2® database system cannot create a new log file in the active log path.
Instead of generating a disk full error, the DB2 database system will attempt to create the log file every five minutes until it succeeds. After each attempt, the DB2 database system writes a message to the Administration Notification log. The only way that you can confirm that your application is hanging because of a log disk full condition is to monitor the Administration Notification log. Until the log file is successfully created, any user application that attempts to update table data will not be able to commit transactions. Read-only queries might not be directly affected; however, if a query needs to access data that is locked by an update request, or a data page that is fixed in the buffer pool by the updating application, read-only queries will also appear to hang.
Setting blk_log_dsk_ful to yes causes applications to hang when the DB2 database system encounters a log disk full error, thus allowing you to resolve the error and allowing the transaction to complete. You can resolve a full log disk situation by either increasing the file system capacity or by removing extraneous files on the same file system.
If blk_log_dsk_ful is set to no, then a transaction that receives a log disk full error will fail and be rolled back.
Set blk_log_dsk_ful to yes when using infinite logging; that is, when the database configuration parameter logsecond is set to -1. With infinite logging, the database might go offline in some situations if a transaction causes a log disk full error.