Log in to the
node that the transaction log belongs to.
Check how many times the transaction log has stalled,
using LMCP's SHOW LOG/CURRENT command:
$RUN SYS$SYSTEM:LMCPLMCP>SHOW LOG/CURRENT
Note the number of checkpoints and stalls displayed by this
command.
Wait for five minutes, then repeat the SHOW LOG/CURRENT
command. Note the number of checkpoints and stalls again.
Compare the information from the SHOW LOG/CURRENT
commands: If the number of checkpoints has not changed, wait until the
system is busier, then try this task again. If the number of checkpoints has increased, and the number
of stalls has increased by more than one, the transaction log is
too small.
If the transaction log is too small, increase its
size. For information about how to change the size of a transaction
log, see
Changing the Size of a Transaction Log.
This example shows how to check whether node BLUE's transaction
log is too small.
Log in to node BLUE. Then check how many times the transaction
log has stalled:
$RUN SYS$SYSTEM:LMCPLMCP>SHOW LOG/CURRENTCheckpoint starts/ends 2464/2464Stall starts/ends 21/21Log status: no checkpoint in progress, no stall in progress.
The number of checkpoints is 2464, and the transaction log
has stalled 21 times.
Wait for five minutes, then repeat the SHOW LOG/CURRENT command:
LMCP>SHOW LOG/CURRENT
Checkpoint starts/ends 2514/2514
Stall starts/ends 28/28
Log status: no checkpoint in progress, no stall in progress.
The number of checkpoints has increased since the previous
reading, and the transaction log has now stalled 28 times, an increase
of 7. This means that the transaction log is too small.