DB2 logfilsiz parameter settings

How should I set the DB2 logfilsiz parameter? If the log file gradually becomes full, you need to increase the value of the DB2 logfilsiz parameter. The following describes how to set the DB2 logfilsiz parameter.

Configuration type

Database

Parameter type

Configurable

Default Value [range]

UNIX®

1000 [4-524 286]

Windows®

1000 [4-524 286]

Measurement Unit

Page 4 KB)

This parameter defines the size of each primary log file and secondary log file. Before these log files are full and new log files are required, the size of these log files limit the number of log records that can be written to these log files.

The usage of the main log file and auxiliary log file and the operations performed when the log file is full depend on the type of log records being executed:

Cyclic Logging
When the changes recorded in the primary log file have been implemented, the primary log file can be reused. If the log file size is small and the application has processed a large number of changes to the database but these changes are not implemented, the main log file may quickly become full. If all the main log files become full, the Database Manager allocates auxiliary log files to save New log records.

Log Record
When the master log file is full, archive the log and allocate a new master log file.

Suggestion: the log file size must be balanced with the number of master log files:

If the database needs to run a large number of update, delete, or insert transactions, which will cause the log file to quickly become full, the value of the logfilsiz parameter should be increased.

Note: The maximum size of log files is the same as the maximum number of log files. logprimary + logsecond) the maximum size of active log space is 512 GB.
If the log file is too small, the system performance will be affected by the overhead of archiving old log files, allocating new log files, and waiting for available log files.

If the disk space is insufficient, the value of logfilsiz should be reduced because the primary log is pre-allocated based on this size.
A large log file reduces the flexibility of managing archived log files and log file copies, because some media may not be able to save the entire log file.

If logs are being retained, close and truncate the current active log file when the last application is disconnected from the database. Use the next log file when you connect to the database. Therefore, if you understand the logging requirements of your concurrent applications, you may be able to determine the size of a log file that will not allocate excessive space waste.
 

Online Implementation of changing the DB2 page size

Create a DB2 tablespace in windows

How to Set garbled characters in the DB2 code page

Implementation of DB2 string connection

Introduction to DB2 datetime Data Types