Skip to end of metadata
Go to start of metadata

 

Overview


This document explains how to change the maximum number of sessions that can be connected to the ALTIBASE HDB server at the same time.

The number of concurrent sessions can be limited by the Altibase server property MAX_CLIENT, and there are some things to consider when changing this property.

 

Version


All the ALTIBASE HDB versions

Changing Procedure


  1. Secure service downtime
  2. Shutdown ALTIBASE HDB server
  3. Change ALTIBASE server properties (refer to 'Considerations' below)
  4. Check OS user resources and change them if necessary (refer to' Considerations' below)
  5. Startup ALTIBASE HDB server

 

Considerations


MAX_CLIENT property


Set the maximum number of sessions that can be connected to the ALTIBASE HDB server at the same time.

The default value is 1000, which can be changed more if necessary. Since this property cannot be changed during operation, the ALTIBASE HDB server must be restarted if changes are required.

How to check the current settings

How to change the settings

TRANSACTION_TABLE_SIZE


This property sets the maximum number of transactions that can be performed concurrently on the ALTIBASE HDB server. As the number of concurrently connected sessions increases, the number of concurrent transactions may increase. Therefore, it is recommended to change them together.

Since this property cannot be changed during operation, the ALTIBASE HDB server must be restarted if it needs to be changed.

Transactions should be set to be larger than MAX_CLIENT because not only transactions performed by users, but also system transactions and replication transactions.

How to check the current settings

How to change the settings

Icon

The TRANSACTION_TABLE_SIZE property setting value can be set to 2^n, which is larger than the current value, and cannot be changed from a large value to a small value.

Icon

Since the change method differs depending on the ALTIBASE HDB server version, be sure to refer to this page (Considerations when changing TRANSACTION_TABLE_SIZE) to proceed.

Changing OS user resource open files


open files are the number of files that can be opened by a process, including not only files accessed by the process, but also communication sockets.

For example, if the ALTIBASE HDB server is operated in a user environment where this value is limited to 10, 10 sessions can be connected at the same time. (In fact, considering the files used by the ALTIBASE HDB server, there may not be an accessible session.)

It is recommended to set it to the maximum value allowed by the operating system (if possible, unlimited).

Check the setting value

The soft limit is the value set by the OS user, and the hard limit is the value set by the root user. The soft limit cannot be greater than the hard limit.

If the user needs to set it to a value greater than the hard limit, the user also needs to change the setting of the root user.

How to change
How to change user preferences

Add the following command to the environment configuration file (.bash_profile or .profile).

How the root user changes
HP-UX
AIX
SunOS

 

Reference


  • For information on ALTIBASE HDB server properties, refer to the General Reference manual at https://github.com/ALTIBASE/Documents/tree/master/Manuals/.
  • MAX_CLIENT and related settings are the maximum values, so large changes do no affect DB performance or system resources.
  • System resources may increase if the number of concurrent connection sessions and concurrent transactions increases due to configuration changes. However, it is difficult to answer how much impact it will have as it depends on the operating environment.

 



  • No labels