onstat -g cmsm command: Print Connection Manager information

Use the onstat -g cmsm command to display information about a specific Connection Manager, or all of the Connection Managers that are attached to the database server the command is run on.

Figure 1: Syntax:

Usage

onstat -g cmsm displays information about connection units the Connection Manager connects to, the number of connections each Connection Manager service-level-agreement (SLA) has processed, SLA definitions, failover-order rules, failover arbitration, and primary server status.

Use connection_manager_name to display information for a specific Connection Manager instance. If connection_manager_name is not specified, onstat -g cmsm displays information about all Connection Manager instances that are connected to the database server.

Example output 1: Output for a specific Connection Manager

In the following example, onstat -g cmsm connection_manager_1 is run on the primary server of my_cluster_1.

Unified Connection Manager: connection_manager_1                Hostname: my_host_1

CLUSTER         my_cluster_1      LOCAL
   SLA          Connections   Service/Protocol   Rule
   oltp_1                35     19910/onsoctcp   DBSERVERS=primary
   report_1              33     19810/onsoctcp   DBSERVERS=(HDR,SDS,RSS)

   Failover Arbitrator: Active Arbitrator, Primary is up
   ORDER=SDS,HDR,RSS PRIORITY=1

The command displays output for connection_manager_1. connection_manager_1 manages a CLUSTER connection unit, and is the active failover arbiter.

Example output 2: Output for a high-availability cluster

In the following example, onstat -g cmsm is run on the primary server of my_cluster_2.

Unified Connection Manager: connection_manager_2                Hostname: my_host_2

CLUSTER         my_cluster_2      LOCAL
   SLA          Connections   Service/Protocol   Rule
   sla_1               1535     19910/onsoctcp   DBSERVERS=primary
   sla_2               2133     19810/onsoctcp   DBSERVERS=(HDR,SDS,RSS)

        Failover Arbitrator: Active Arbitrator, Primary is up
        ORDER=SDS,HDR,RSS PRIORITY=1

CLUSTER         my_cluster_3
   SLA          Connections   Service/Protocol   Rule
   sla_3                730     19930/onsoctcp   DBSERVERS=primary
   sla_4                901     19830/onsoctcp   DBSERVERS=(HDR,SDS,RSS)

   Failover Arbitrator: Active Arbitrator, Primary is up
   ORDER=SDS,HDR,RSS PRIORITY=1

Unified Connection Manager: connection_manager_3                Hostname: my_host_3

CLUSTER         my_cluster_2      LOCAL
   SLA          Connections   Service/Protocol   Rule
   sla_5                614     19920/onsoctcp   DBSERVERS=primary
   sla_6                483     19820/onsoctcp   DBSERVERS=(HDR,SDS,RSS)

   Failover Arbitrator: Failover is enabled
   ORDER=SDS,HDR,RSS PRIORITY=2

CLUSTER         my_cluster_3
   SLA          Connections   Service/Protocol   Rule
   sla_7                678     19940/onsoctcp   DBSERVERS=primary
   sla_8                270     19840/onsoctcp   DBSERVERS=(HDR,SDS,RSS)

        Failover Arbitrator: Failover is enabled
        ORDER=SDS,HDR,RSS PRIORITY=2

The command displays output for the two Connection Managers that connect to the primary server of the cluster. connection_manager_2 and connection_manager_3 are installed on separate hosts, and together they manage two CLUSTER connection units. connection_manager_2 is the active failover arbiter for both CLUSTER connection units.

Example 3: Output for a replicate set

In the following example, onstat -g cmsm is run on a replicate server in my_replicate_set_1.

Unified Connection Manager: connection_manager_4                Hostname: my_host_4

REPLSET         my_replicate_set_1
   SLA          Connections   Service/Protocol   Rule
   sla_1                160     19810/onsoctcp   DBSERVERS=ANY

Unified Connection Manager: connection_manager_5                Hostname: my_host_5

REPLSET         my_replicate_set_1
   SLA          Connections   Service/Protocol   Rule
   sla_2                240     19820/onsoctcp   DBSERVERS=ANY

The command displays output for the two Connection Managers that connect to the replicate server. connection_manager_4 and connection_manager_5 are installed on separate hosts, and together they manage the replication servers.

Example 4: Output for a grid

In the following example, onstat -g cmsm is run on a node of my_grid_1.

Unified Connection Manager: connection_manager_6                Hostname: my_host_6

GRID    my_grid_1
   SLA          Connections   Service/Protocol   Rule
   sla_1                456     19830/onsoctcp   DBSERVERS=(group_name_1,group_name_2) POLICY=FAILURE

Unified Connection Manager: connection_manager_7                Hostname: my_host_7

GRID    my_grid_1
   SLA          Connections   Service/Protocol   Rule
   sla_2                785     19840/onsoctcp   DBSERVERS=(group_name_1,group_name_2) POLICY=FAILURE

The command displays output for the two Connection Managers that connect to the grid. The command displays output for the two Connection Managers that connect to the node. connection_manager_6 and connection_manager_7 are installed on separate hosts, and together they manage the grid.

Example 5: Output for a server set

In the following example, onstat -g cmsm is run on a stand-alone server in the server set.

Unified Connection Manager: connection_manager_8                      Hostname: my_host_8

SERVERSET       server_1,server_2
   SLA          Connections   Service/Protocol   Rule
   sla_1                 63     19810/onsoctcp   DBSERVERS=(server_1,server_2) POLICY=ROUNDROBIN

Unified Connection Manager: connection_manager_9                      Hostname: my_host_9

SERVERSET       server_1,server_2
   SLA          Connections   Service/Protocol   Rule
   sla_2                 63     19810/onsoctcp   DBSERVERS=(server_1,server_2) POLICY=ROUNDROBIN

The command displays output for the two Connection Managers that connect to the server set. connection_manager_8 and connection_manager_9 are installed on separate hosts, and together they manage the server set.

Output description

The output of the onstat -g cmsm command contains sections for each Connection Manager. Each section displays the Connection Manager instance name and host name, followed by subsections that contain information on each connection unit the Connection Manager connects to.

Unified Connection Manager: The name of the Connection Manager instance.
Hostname: The name of the Connection Manager's host.
SLA: The names of service level agreements, as defined in the Connection Manager's configuration file.
Connections: The numbers of connections each SLA processed since the Connection Manager started.
Service/Protocol: The port number or service name that is associated with the SLA, followed by the connection protocol type.
Rule: The SLA definition.
Failover Arbitrator:: Specifies whether the Connection Manager is the active failover arbiter, if the primary server is active, and if failover is enabled. Displays only for CLUSTER connection units.
ORDER: Specifies the failover order for a cluster. Displays only for CLUSTER connection units.
PRIORITY: Specifies the priority of the connection between the Connection Manager and the primary server of a cluster. Displays only for CLUSTER connection units.