Configuring the Distributed Lock Manager (OPS 7.3.x)

This section describes DLM configuration, which you do only when using Oracle Parallel Server 7.3.3. To do this in SAM, read the next section "“Using SAM to Configure the Distributed Lock Manager (OPS 7.3.x)”." If you want to use HP-UX commands for DLM configuration, skip ahead to the section "“Using HP-UX Commands to Configure the Distributed Lock Manager (OPS 7.3.x)”."

Using SAM to Configure the Distributed Lock Manager (OPS 7.3.x)

Use the following steps on the configuration node:

From the High Availability Clusters menu in SAM, choose the DLM Configuration option. SAM displays a Distributed Lock Manager Configuration screen. If no cluster has yet been configured with the DLM, the list area will be empty.
NOTE: If you have already configured Group Membership Service (GMS), you will not be able to complete DLM configuration steps. You can configure DLM or GMS, but not both.
Select the Actions menu, and choose Create DLM Configuration. A new screen appears, containing a list of clusters eligible for DLM configuration. The list contains only clusters that are not currently running. Select the cluster you wish to configure with the DLM, then select Specify DLM Parameters. A step menu appears.
Choose each step in sequence, filling in the dialog boxes with required information, or accepting the default values shown. For information about each step, choose Help.
When finished with all steps, select at the Step Menu screen. This action propagates the DLM configuration among all nodes and returns you to the Distributed Lock Manager Configuration screen.
Exit from the Distributed Lock Manager Configuration screen.

Skip ahead to the section "“Verifying the Cluster Configuration ”."

Using HP-UX Commands to Configure the Distributed Lock Manager (OPS 7.3.x)

This section describes how to set the DLM's internal lock database parameters using HP-UX commands. DLM internal parameters are stored in a file known as /etc/opt/dlm/dlmconfig. This file is not editable, so you must create an ASCII file first, then convert it into binary form. First, use the following command to generate an editable template file:

# dlmquery -v -C /etc/opt/dlm/dlm.asc

Edit the file /etc/opt/dlm/dlm.asc to incorporate the appropriate DLM internal parameters from the Distributed Lock Manager worksheet (defaults shown here are appropriate for the Oracle demo database, which can be installed at the same time you install Oracle software). The file looks like the following:

CLUSTER_NAME                    cluster1
MAXPROCESSES                    2400
MAXRESOURCES                    6000
MAXLOCKS                        12000
DEADLOCK_DETECTION_INTERVAL     300
PROCESS_MONITORING_INTERVAL     300
 
NODE_NAME                        node1
    IPADDR                      15.27.217.9
 
NODE_NAME                        node2
    IPADDR                      15.27.217.10

Review and complete the file, supplying appropriate values as needed. Verify the cluster name, and ensure that the IP addresses used for IPADDR on each node belong to the same subnet. As necessary, you can substitute the values from your own Distributed Lock Manager worksheet for the defaults that are shown.

Use the following command to verify the configuration you enter into the template file:

# dlmcheckconf -v -C /etc/opt/dlm/dlm.asc

This command checks the content of the ASCII template file and displays messages. If there are errors, edit the file again to correct them, then issue the dlmcheckconf command again. Use the following command to copy the configuration to all the nodes in the cluster:

# dlmapplyconf -v -C /etc/opt/dlm/dlm.asc




	NOTE: The `dlmquery` command should be used only for template creation; the output of the command does not necessarily reflect the current cluster configuration. For diagnostic information, refer to the section "“Using DLM Diagnostic Tools (OPS 7.3.x)”" in the chapter "Chapter 8 “Troubleshooting Your Cluster”."

Configuring the Distributed Lock Manager (OPS 7.3.x)

Technical documentation

» Table of Contents

» Index

Using SAM to Configure the Distributed Lock Manager (OPS 7.3.x)

Using HP-UX Commands to Configure the Distributed Lock Manager (OPS 7.3.x)