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.
CMALARMPROGRAM Connection Manager configuration parameterThe CMALARMPROGRAM parameter specifies the path and file name of a program or script to run if failover processing encounters an error.

CMALARMPROGRAM Connection Manager configuration parameter

The CMALARMPROGRAM parameter specifies the path and file name of a program or script to run if failover processing encounters an error.

Syntax

Usage

The CMALARMPROGRAM parameter is optional, and is supported by the following connection units:

CLUSTER
GRID
REPLSET
SERVERSET

If the Connection Manager cannot find a server capable of receiving failover, it searches for ORDER-attribute servers at increasing intervals, up to 60 seconds, for a maximum of two days. If failover processing fails after eight attempts, the Connection Manager calls the program that is specified by the CMALARMPROGRAM parameter. The first eight failover attempts take approximately one minute.

Before you can use the cmalarmprogram script, you must edit the file, and set the script parameters.

The ALARMADMIN and ALARMPAGER parameters determine the level of Connection Manager event alarms that are sent to specified email addresses.

Table 1. Connection Manager event-alarm levels
Level of Connection Manager event alarm	Alarm type
0 (default)	None
1	Unimportant informational alarms
2	Informational alarms
3	Alarms requiring attention
4	Emergency alarms
5	Fatal error alarms

Example

In the following example, cmalarmprogram.sh is called if failover processing fails after eight attempts:

CMALARMPROGRAM $INFORMIXDIR/etc/cmalarmprogram.sh