Restoring log space settings in upgraded databases

You can restore log space settings for logsecond database configuration and infinite active logging to their previous values in your upgraded Db2® server.

Before you begin

To make changes to the database configuration, you must have SYSCTRL, SYSADM, or SYSMAINT authority.

You can reverse database configuration changes for logsecond and infinite active logging settings that were made before the upgrade. The previous-value variable refers to the setting that you had before upgrade and sample is the database name.

For a partitioned database environment, you only need to change the log space related database configuration parameters on the catalog database partition.

To adjust table space or log file sizes, see the pre-upgrade task, Increasing table space and log file sizes before upgrade for more information.

Procedure

Restore log space settings to the previous-value you had before upgrade:

If you changed only the logsecond database configuration in the pre-upgrade task, you can restore the previous-value:

db2 UPDATE DB CFG FOR <sample> using LOGSECOND <previous-value>
If you enabled infinite active logging and changed the logsecond database configuration in the pre-upgrade task, you can restore the previous-value:
db2 UPDATE DB CFG FOR <sample> using LOGARCHMETH1 <previous-value>
db2 UPDATE DB CFG FOR <sample> using LOGSECOND <previous-value>

What to do next

See Activating a database after upgrade