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.
SECONDARY_EVENT_TIMEOUT Connection Manager configuration parameterThe SECONDARY_EVENT_TIMEOUT parameter specifies the number of seconds that must elapse with no secondary-server events before the Connection Manager disconnects from a secondary server. A secondary-server event is an indication from a secondary server that the server is still functioning, such as a sent performance-statistics or administration messages.

SECONDARY_EVENT_TIMEOUT Connection Manager configuration parameter

The SECONDARY_EVENT_TIMEOUT parameter specifies the number of seconds that must elapse with no secondary-server events before the Connection Manager disconnects from a secondary server. A secondary-server event is an indication from a secondary server that the server is still functioning, such as a sent performance-statistics or administration messages.

Syntax

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

Usage

The SECONDARY_EVENT_TIMEOUT parameter is optional, and applies CLUSTER connection units.

If the SECONDARY_EVENT_TIMEOUT parameter is not specified in the Connection Manager configuration file, the Connection Manager waits 60 seconds for secondary-server events before it disconnects from the server.

Example

In the following example, the Connection Manager disconnects from a secondary server after 300 seconds elapse with no secondary-server events.

SECONDARY_EVENT_TIMEOUT 300