If the log is running out of space, the current transaction
is rolled back, and the server issues an error message and halts.
You cannot restart the server until the active log size is increased.
Procedure
To increase the size of the active log while the server
is halted, complete the following steps:
- Issue the DSMSERV DISPLAY LOG offline
utility to display the size of the active log.
- Ensure that the location for the active log has enough
space for the increased log size. If a log mirror exists, its location
must also have enough space for the increased log size.
- Halt the server.
- In the dsmserv.opt file, update the ACTIVELOGSIZE option
to the new maximum size of the active log, in megabytes. For
example, to change the active log to its maximum size of 128 GB, enter
the following server option:
activelogsize 131072
- If you plan to use a new active log directory, update the
directory name specified in the ACTIVELOGDIRECTORY server
option. The new directory must be empty and must be accessible to
the user ID of the database manager.
- Restart the server.
Results
Log files of 512 MB are automatically defined until the
size specified in the ACTIVELOGSIZE option is reached.
If a log mirror exists, log files are also defined automatically.