The overflowlogpath parameter specifies
a location for DB2® databases
to find log files needed for a rollforward operation, as well as where
to store active log files retrieved from the archive. It also gives
a location for finding and storing log files needed for using db2ReadLog API.
- Configuration type
- Database
- Parameter type
- Configurable online
- Propagation class
- Immediate
- Default [range]
- NULL [any valid path ]
This parameter can be used for several functions,
depending on your logging requirements.
- Use the overflowlogpath parameter to specify
a location for DB2 databases
to find log files that are needed for a rollforward operation. It
is similar to the OVERFLOW LOG PATH option on
the ROLLFORWARD command. Instead of always specifying OVERFLOW
LOG PATH on every ROLLFORWARD command,
you can set this configuration parameter once. However, if both are
used, the OVERFLOW LOG PATH option overwrites
the overflowlogpath configuration parameter,
for that particular rollforward operation.
- If logsecond is set to -1,
you can specify a directory for DB2 to
store active log files retrieved from the archive with the overflowlogpath parameter.
Active log files have to be retrieved for rollback operations if they
are no longer in the active log path. Without the overflowlogpath parameter
set, DB2 databases retrieve
the log files into the active log path. Use the overflowlogpath parameter
to provide additional resource for DB2 databases
to store the retrieved log files. The benefit includes spreading the
I/O cost to different disks, and allowing more log files to be stored
in the active log path.
- If you need to use the db2ReadLog API
for replication, for example, use the overflowlogpath to
specify a location for DB2 databases
to search for log files that are needed for this API. Before DB2 Version 8, db2ReadLog was
called sqlurlog. If the log file is not found (in
either the active log path or the overflow log path) and the database
is configured to archive logs by using the logarchmeth1 or logarchmeth2 parameters, DB2 retrieves the log file. Also
use the overflowlogpath parameter to specify
a directory for DB2 databases
to store the log files retrieved. The benefit comes from reducing
the I/O cost on the active log path and allowing more log files to
be stored in the active log path.
- If you have configured a raw device for the active log path, the overflowlogpath parameter
must be configured if you want to set the logsecond parameter
to -1, or if you want to use the db2ReadLog API.
- You can specify a location for DB2 databases to retrieve log files that are
required for a BACKUP DATABASE INCLUDE LOGS operation.
To
set overflowlogpath, specify a string of up to
242 bytes. The string must point to a path name, and it must be a
fully qualified path name, not a relative path name. The path name
must be a directory, not a raw device. You cannot specify overflowlogpath as
an empty string.
Note: The database partition number and a log stream ID
are automatically appended to the path, for example, /home/dbuser/dblogs/NODE0000/LOGSTREAM0000/.
If you are creating logs in a multiple partition database environment,
such as DB2 pureScale® or a partitioned database environment,
you must copy log files into the log directories, otherwise your logs
might be incomplete.