This document describes the properties in of the altibase.properties file for effective use of Altibase, and how to specify values. This document does not include a description of the hidden property.
When changing the properties in the configuration file, the following format is used.
Property name = Property value Ex) PORT_NO = 20300
The items that the user must configure at least when creating the DB are as follows. For the sake of understanding, it is assumed that the disk volume is configured as followfollows.
|Path where Altibase is installed
|Directory where data files will be saved
|Directory where transaction log files will be saved
The resources used by Altibase refers refer to resources such as physical memory/disk space and logical tablespace. This section describes each property that flexibly limits query execution, such as a large number of changes at the session/system level, which can lead to resource shortages. It is recommended that these properties be operated to change//apply only necessary sessions with configuration change at the session-level rather than changing the default configuration.
- Since all the QUERY/IDLE/UTRANS/FETCH Timeout properties and errors related to the session are recorded in altibase.boot.log, find the session and take action when it occurs.
- Notes/Considerations for ALTER SYSTEM and ALTER SESSION: ALTER SYSTEM changes will take effect from the subsequent sessions. Therefore, since the currently connected session is not applied, the desired result can be applied only by performing ALTER SESSION for individual connected sessions.
Disk I/O Performance-related properties
This describes the property items related to Altibase's disk I/O performance.
|If it is set to 2, all DDL performance records can be checked, so when a problem occurs, which can be helpful for analysis if DDL performance is based.
|If it is set to 6, a log of DML occurs when a replication conflict is recorded. which can be helpful for analysis.
The default value is 0. To know the execution times of each SQL statement related to performance, it can be activated in real time as follows.
iSQL> ALTER SYSTEM SET timed_statistics = 1 ;
When activated, the execution times of each SQL statement starts start to be recorded in v$statement.