Home
AdministeringIn addition to administering the database server, you can tune performance, replicate data, and archive data.
System administrationThese topics contain concepts, procedures, and reference information for database and database server administrators to use for managing and tuning HCL OneDB™ database servers.
Administrator's GuideThe HCL OneDB™ Administrator's Guide provides the information required to administer HCL OneDB™.
High availability and scalabilityA successful production environment requires database systems that are always available, with minimal if any planned outages, and that can be scaled quickly and easily as business requirements change.
Connection management through the Connection ManagerConnection Managers can control automatic failover for high-availability clusters, monitor client connections and direct requests to appropriate database servers, act as proxy servers and handle client/server communication, and prioritize connections between application servers and the primary server of a high-availability cluster. Connection Managers support high-availability clusters, replicate sets, server sets, and grids.
Configuring connection managementTo configure connection management, you must install software, set environments and connectivity information, create Connection Manager configuration files, and run the oncmsm utility.
Creating Connection Manager configuration files
Parameters and format of the Connection Manager configuration fileThe following example shows the format of the Connection Manager configuration file, and shows which parameters and attributes can be set for each connection-unit type.
EVENT_TIMEOUT Connection Manager configuration parameterThe EVENT_TIMEOUT parameter specifies the number of seconds that must elapse with no primary-server events before the active-arbiter Connection Manager starts failover processing. The Connection Manager waits for primary-server events or notifications from secondary servers that the primary server is offline. A primary-server event is an indication from the primary server that the server is still functioning, such as a sent performance-statistics or administration messages, or node-changes.

EVENT_TIMEOUT Connection Manager configuration parameter

The EVENT_TIMEOUT parameter specifies the number of seconds that must elapse with no primary-server events before the active-arbiter Connection Manager starts failover processing. The Connection Manager waits for primary-server events or notifications from secondary servers that the primary server is offline. A primary-server event is an indication from the primary server that the server is still functioning, such as a sent performance-statistics or administration messages, or node-changes.

Syntax

Table 1. Values for the EVENT_TIMEOUT Connection Manager configuration parameter
EVENT_TIMEOUT parameter value	Description
`-1`	Connection Manager waits indefinitely
`0` to `30`	Connection Manager waits 30 seconds.
> `30`	Connection Manager waits the specified number of seconds.

Usage

The EVENT_TIMEOUT parameter is optional, and applies to CLUSTER connection units.

If EVENT_TIMEOUT is not specified in the Connection Manager configuration file, the Connection Manager waits 60 seconds for primary-server events or notifications from secondary servers that the primary server is offline before it starts failover processing.

Example

In the following example, the active-arbiter Connection Manager begins failover processing after 200 seconds elapse with no primary-server events.

EVENT_TIMEOUT 200