Skip to end of metadata
Go to start of metadata

This describes resource limits, environment variables, and various environment settings of user accounts in the system for operating Altibase on the Solaris OS.

For details related to configuration refer to the guide provided by Solaris.

Resource Limitations

In the UNIX operating system, logical limits are set for available resources on a user account basis. Among the resource limit items, the items that need to be expanded for stable service operation as follows.

ClassificationDescriptionRecommended Value
data seg size(data)The maximum size of one process data areaunlimited
file size (fsize)The maximum size of files that can be createdunlimited
open files (nofiles)The maximum number of files that can be accessed simultaneously by one processunlimited
max memory size (rss)The maximum size of available memoryunlimited
virtual memory (memory)The maximum size of available virtual memoryunlimited
max user processThe number of processes that can be created per userunlimited

It is intended to remove problems that may occur due to logical limitations even when expanding the memory and data file area used by a specific user. This setting has no effect on other processes. It is recommended to set the maximum value allowed by (unlimited if possible).

For example, the meaning of open files includes not only the files accessed by the process, but also the number of communication sockets. If Altibase is operated in an environment where this value is limited to 10, it means that more than 10 sessions can be accessed simultaneously. (Considering the file used by Altibase, there may not be an accessible session.)

To change the method, edit the environment configuration file using the ulimit command, edit the system resource configuration file, or use the kernel-related utilities provided for each operating system.

Hard-Limit & Soft-Limit

Resource limit values are divided into the concept of hard-limit and soft-limit. The hard-limit means the maximum value of the kernel-level resource limit that cannot be changed except the system administrator account (root), and the soft-limit means that the current user account can change up to the hard-limit. (Refer to the ulimit -S / -H option for details.)

The soft-limit is effective while the user maintains a session by accessing it, and changes are immediately reflected. However, when other sessions of the same user account are connected, the existing soft-limit is reflected, so the ulimit command is often added to the user account configuration file.

However, this method may not be intended due to the hard-limit, so it is recommended to systematically apply it through editing system-wide resource configuration files rather than applying user account units using environment configuration files.

For reference, Solaris does not have a system configuration file related to user resource limitation, and is described in /etc/system. There are also other way to use /etc/default/login or /etc/profile.

Environment Variables

The essential environment variables are as follows. The following environment variables must be set in the environment configuration file of the user account according to the syntax of the user's shell.

Environment VariableDescription
ALTIBASE_HOMESpecifies the path where Altibase is installed.
PATHSpecifies the path where Altibase's utilities and shell scripts. Adds ALTIBASE_HOME/bin.
LD_LIBRARY_PATHSpecifies the path where Altibase's dynamic library. Adds ALTIBASE_HOME/lib.

In addition, the following environment variable that exists only in Solaris must be added.

LD_LIBRARY_PATH_64Sets when linking dynamic library to 64-bit.

Character Set Consideration

Prior to Altibase 5.3, a separate property existed in relation to the NLS_USE item in relation to the character set but has been replaced by an environment variable starting from Altibase 5.3.

For this reason, if the user sets KO16KSC5601/MS949/UTF8, etc. for the DB character set in the US version of Altibase 5.3 or later, the user must set the environment variable ALTIBASE_NLS_USE. Otherwise, it is connected to the default setting of US7ASCII, and after input, it is searched in the form of an unknown string at the time of inquiry.

Terminal Configuration

In addition to the considerations regarding the use of the character set mentioned in the [Environment Variables] section, the font of the terminal to be used must also be set the same as the character set in the DB.

  • No labels