Log in to thenode 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 thiscommand.
Wait for five minutes, then repeat the SHOW LOG/CURRENTcommand. Note the number of checkpoints and stalls again.
Compare the information from the SHOW LOG/CURRENTcommands: If the number of checkpoints has not changed, wait until thesystem is busier, then try this task again. If the number of checkpoints has increased, and the numberof stalls has increased by more than one, the transaction log istoo small.
If the transaction log is too small, increase itssize. For information about how to change the size of a transactionlog, see Changing the Size of a Transaction Log.
This example shows how to check whether node BLUE's transactionlog is too small.
Log in to node BLUE. Then check how many times the transactionlog 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 loghas stalled 21 times.
Wait for five minutes, then repeat the SHOW LOG/CURRENT command:
LMCP>SHOW LOG/CURRENTCheckpoint starts/ends 2514/2514Stall starts/ends 28/28Log status: no checkpoint in progress, no stall in progress.
The number of checkpoints has increased since the previousreading, and the transaction log has now stalled 28 times, an increaseof 7. This means that the transaction log is too small.