Moving Db2 transaction log files for good performance
Periodically move old Db2 transactional logs that the IBM® Security Guardium® Key Lifecycle Manager database creates. Otherwise, large numbers of transactional logs might affect performance.
About this task
Db2 transactional logs occur in these directories:
- Windows systems:
INSTANCEHOME:\sklmdbarchive\
KLMDB42
\KLMDB42\NODE0000\LOGSTREAM0000\C0000000where:
INSTANCEHOME
is the drive letter that you specified during the installation.KLMDB42
is the database instance owner.KLMDB42
is the name of the IBM Security Guardium Key Lifecycle Manager database.NODE0000
,LOGSTREAM0000
, andC0000000
might be different on your system.
- Systems such as Linux or AIX:
~sklmdbarchive/klmdb42/
KLMDB42
/NODE0000/LOGSTREAM0000/C0000000Where,
KLMDB42
is the database instance owner.KLMDB42
is the name of the IBM Security Guardium Key Lifecycle Manager database.NODE0000
,LOGSTREAM0000
, andC0000000
might be different on your system.
If IBM Security Guardium Key Lifecycle Manager manages many keys and if the
disk partition that contains the sklmdbarchive
directory has low free disk space,
move the old transaction logs to a different disk partition.
Note: As you carry out this task, be careful not
to move the current active log.
Take these steps on a periodic basis: