Adjusting the log space size in upgraded databases
You need to set the appropriate size for log files since it is one of the important factors in tuning your Db2® server. Also, if you increased the log files sizes as a pre-upgrade task, you can restore additional free space to your Db2 server.
Before you begin
To increase the size of table spaces and log space, you must have SYSCTRL or SYSADM authority.
On a partitioned database environment, you must adjust the log space size on the catalog database partition server.
- Connect to the database that you upgraded:
where sample is the database name.
db2 CONNECT TO sample
- Restore your log file size settings to the values you had
where previous-value is the setting that you save before upgrade and sample is the database name. In the pre-upgrade task, only the logprimary and the logsecond parameters were changed. If you change the setting for the logfilsiz parameter, you should restore the previous value.
db2 UPDATE DB CFG FOR sample using LOGSECOND previous-valueIf you enabled infinite active logging, disable it by running the following commands:
where previous-value is the setting that you save before upgrade and sample is the database name.
db2 UPDATE DB CFG FOR sample using LOGARCHMETH1 previous-value db2 UPDATE DB CFG FOR sample using LOGSECOND previous-value
- To support larger log record headers, increase the log space setting, by approximately 10% - 15% over what you used for Db2 version 9.7.
To support larger log record headers, increase the softmax parameter by
10% - 15% over what you used for Db2
db2 UPDATE DB CFG FOR sample using SOFTMAX 1.15 * previous-valueImportant: The softmax database configuration parameter is deprecated and might be removed in a future release. For more information, see Some database configuration parameters are deprecated.
Double the value for the logbufsz parameter:
db2 UPDATE DB CFG FOR sample using LOGBUFSZ 2 * previous-value
- Disconnect from the database that you upgraded:
logfilsiz changes take effect only when the database is reactivated. All applications must first disconnect from the database then deactivate and activate the database again.
db2 CONNECT RESET