Updated: 11 December 1998 |
OpenVMS System Manager's Manual
Previous | Contents | Index |
Changes to your system, such as increase in work load, can affect transaction performance. Once a month, monitor transactions on the node to make sure that transaction performance has not deteriorated. In an OpenVMS Cluster environment, monitor transaction performance on all the nodes in the cluster.
MONITOR TRANSACTION/SUMMARY[=file-spec]/ENDING=time/NODE=(nodename,...) |
where:
file-spec | is the file specification of the summary file. Information about transactions is summarized and recorded in the summary file. If you omit the file specification, the information is recorded in MONITOR.SUM in your default directory. |
time | is the time that the monitoring session ends. |
nodename | is the name of a node. In an OpenVMS Cluster, list all the nodes in the cluster. |
This example shows how to monitor transaction performance on an OpenVMS Cluster that consists of two nodes whose SCSNODE names are BLUE and RED.
Monitor transactions on nodes BLUE and RED for one day:
$ MONITOR TRANSACTION/SUMMARY=DISK$LOG1:[LOGFILES]TRANSACTIONS.SUM - _$ /ENDING="+1-"/NODE=(BLUE,RED) |
Examine the summary file:
DISTRIBUTED TRANSACTION STATISTICS on node BLUE From: 16-OCT-1998 14:23:51 SUMMARY To: 17-OCT-1998 14:23:51 CUR AVE MIN MAX Start Rate 49.02 43.21 31.30 49.02 Prepare Rate 48.70 43.23 30.67 48.70 One Phase Commit Rate 0.00 0.00 0.00 0.00 Total Commit Rate 48.70 43.19 31.30 48.70 Abort Rate 0.00 0.00 0.00 0.00 End Rate 48.70 43.19 31.30 48.70 Remote Start Rate 0.00 0.00 0.00 0.00 Remote Add Rate 0.00 0.00 0.00 0.00 Completion Rate 0-1 21.42 13.57 0.63 21.42 by Duration 1-2 25.97 29.15 24.59 33.87 in Seconds 2-3 1.29 0.47 0.00 4.47 3-4 0.00 0.00 0.00 0.00 4-5 0.00 0.00 0.00 0.00 5+ 0.00 0.00 0.00 0.00 SUMMARIZING DISTRIBUTED TRANSACTION STATISTICS on node RED From: 16-OCT-1998 14:23:52 SUMMARY To: 17-OCT-1998 14:23:52 . . . |
Make a note of the following values:
Compare the results from this monitoring session to those of previous sessions:
Session | End Rate | Completion Rates | ||
---|---|---|---|---|
0--1 Secs | 1--2 Secs | 2--3 Secs | ||
June | 42.13 | 12.98 | 28.13 | 1.02 |
July | 38.16 | 10.35 | 25.80 | 2.01 |
August | 43.19 | 13.57 | 29.15 | 0.47 |
The results for node BLUE show no signs of deteriorating performance.
25.6 Checking Whether a Transaction Log Is Too Small
If transaction performance has deteriorated on a node, check whether its transaction log is too small.
Section 25.5 describes how to find out whether transaction performance has deteriorated.
$ RUN SYS$SYSTEM:LMCP LMCP> SHOW LOG/CURRENT |
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:LMCP LMCP> SHOW LOG/CURRENT Checkpoint starts/ends 2464/2464 Stall starts/ends 21/21 Log 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.
25.7 Changing the Size of a Transaction Log
To determine if changing the size of a transaction log is necessary, see Section 25.6.
Follow all the steps carefully. Taking shortcuts can lead to data corruption. |
SHOW LOG SYSTEM$node.LM$JOURNAL |
where node is the name of the node that the transaction
log belongs to.
RENAME dirspecSYSTEM$node.LM$JOURNAL dirspecSYSTEM$node.LM$OLD |
where:
dirspec | is the full specification of the directory containing the transaction log. |
node | is the name of the node that the transaction log belongs to. |
Yes |
Close the transaction log as follows:
|
||||||||||||
No | Close the transaction log by rebooting the node. Log in to the node when it has rebooted. |
CONVERT LOG/SIZE=size dirspecSYSTEM$node.LM$OLD dirspecSYSTEM$node.LM$JOURNAL |
where:
size | is the new size of the transaction log in blocks. |
dirspec | is the full specification of the directory containing the transaction log. |
node | is the name of the node that the transaction log belongs to. |
DELETE dirspecSYSTEM$node.LM$OLD; |
where:
dirspec | is the full specification of the directory containing the old transaction log. |
node | is the name of the node that the transaction log belongs to. |
This example shows how to change the size of node RED's transaction log to 6000 blocks. Node RED is in an OpenVMS Cluster, and its transaction log is in DISK$LOG2:[LOGFILES].
Log in to node RED. Find out which directory RED's transaction log is in, then rename the transaction log:
$ RUN SYS$SYSTEM:LMCP LMCP> SHOW LOG SYSTEM$RED.LM$JOURNAL Directory of DISK$LOG2:[LOGFILES] SYSTEM$RED.LM$JOURNAL;1 Total of 1 file. LMCP> EXIT $ RENAME DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$JOURNAL - _$ DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$OLD |
Stop all software that uses DECdtm services. Then close the transaction log:
$ RUN SYS$SYSTEM:LMCP LMCP> CLOSE LOG Transaction log closed, TP_SERVER process stopped LMCP> EXIT |
Restart the TP_SERVER process:
$ @ SYS$STARTUP:DECDTM$STARTUP.COM |
Change the size of the transaction log:
$ RUN SYS$SYSTEM:LMCP LMCP> CONVERT LOG/SIZE=6000 DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$OLD - _LMCP> DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$JOURNAL Log file DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$JOURNAL;1 created. Log file DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$OLD converted. LMCP> EXIT |
Restart the software that uses DECdtm services.
Delete the old transaction log:
$ DELETE DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$OLD; |
You may want to move a transaction log if:
Follow all the steps carefully. Taking shortcuts can lead to data corruption. |
SHOW LOG SYSTEM$node.LM$JOURNAL |
where node is the name of the node that the transaction
log belongs to.
RENAME dirspecSYSTEM$node.LM$JOURNAL dirspecSYSTEM$node.LM$OLD |
where:
dirspec | is the full specification of the directory containing the transaction log. |
node | is the name of the node that the transaction log belongs to. |
Yes |
Close the transaction log as follows:
|
||||||||||||
No | Close the transaction log by rebooting the node. Log in to the node when it has rebooted. |
DEFINE/SYSTEM/EXECUTIVE_MODE SYS$JOURNAL dirspec[,...] |
where dirspec is the full specification of a directory
containing one or more transaction logs. List all the directories that
will contain transaction logs after you have moved the transaction log.
You can list the directories in any order.
In an OpenVMS Cluster,
use SYSMAN to redefine SYS$JOURNAL clusterwide.
CONVERT LOG old-dirspecSYSTEM$node.LM$OLD new-dirspecSYSTEM$node.LM$JOURNAL |
where:
old-dirspec | is the full specification of the directory that currently contains the transaction log. |
node | is the name of the node that the transaction log belongs to. |
new-dirspec | is the full specification of the directory that you are moving the transaction log to. |
DELETE dirspecSYSTEM$node.LM$OLD; |
where:
dirspec | is the full specification of the directory containing the old transaction log. |
node | is the name of the node that the transaction log belongs to. |
This example shows how to move BLUE's transaction log. BLUE is in an OpenVMS Cluster. The cluster members and the locations of their transaction logs are as follows:
Node | Directory Containing Log |
---|---|
BLUE | DISK$LOG1:[LOGFILES] |
RED | DISK$LOG2:[LOGFILES] |
Neither node has a node--specific version of SYLOGICALS.COM.
Decide where you want to move BLUE's transaction log to. In this example, assume that you want to move it to DISK$LOG3:[LOGFILES].
Log in to node BLUE. Then mount the disk clusterwide, and create a new directory for the transaction log:
$ MOUNT/CLUSTER/SYSTEM DUA3: LOG3 $ CREATE/DIRECTORY DISK$LOG3:[LOGFILES] |
Find out which directory BLUE's transaction log is in, then rename the transaction log:
$ RUN SYS$SYSTEM:LMCP LMCP> SHOW LOG SYSTEM$BLUE.LM$JOURNAL Directory of DISK$LOG1:[LOGFILES] SYSTEM$BLUE.LM$JOURNAL;1 Total of 1 file. LMCP> EXIT $ RENAME DISK$LOG1:[LOGFILES]SYSTEM$BLUE.LM$JOURNAL - _$ DISK$LOG1:[LOGFILES]SYSTEM$BLUE.LM$OLD |
Stop all software that uses DECdtm services. Then close the transaction log:
$ RUN SYS$SYSTEM:LMCP LMCP> CLOSE LOG Transaction log closed, TP_SERVER process stopped LMCP> EXIT |
Restart the TP_SERVER process:
$ @SYS$STARTUP:DECDTM$STARTUP.COM |
Redefine SYS$JOURNAL:
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO DEFINE/SYSTEM/EXECUTIVE_MODE SYS$JOURNAL - _SYSMAN> DISK$LOG2:[LOGFILES], DISK$LOG3:[LOGFILES] SYSMAN> EXIT |
Edit the SYS$MANAGER:SYLOGICALS.COM command procedure to update the SYS$JOURNAL definition. Then move the transaction log:
$ RUN SYS$SYSTEM:LMCP LMCP> CONVERT LOG DISK$LOG1:[LOGFILES]SYSTEM$BLUE.LM$OLD - _LMCP> DISK$LOG3:[LOGFILES]SYSTEM$BLUE.LM$JOURNAL Log file DISK$LOG3:[LOGFILES]SYSTEM$BLUE.LM$JOURNAL;1 created. Log file DISK$LOG1:[LOGFILES]SYSTEM$BLUE.LM$OLD converted. LMCP> EXIT |
Restart the software that uses DECdtm services. Then delete the old transaction log:
$ DELETE DISK$LOG1:[LOGFILES]SYSTEM$BLUE.LM$OLD; |
Previous | Next | Contents | Index |
Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal |
6017PRO_100.HTML
|