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.
Performance GuideThe HCL OneDB™ Performance Guide describes how to configure and operate your HCL OneDB™ database server to improve overall system throughput and to improve the performance of SQL queries.
Effect of configuration on I/O activityThe configuration of your database server affects I/O activity.
Background I/O activitiesBackground I/O activities do not service SQL requests directly. Many of these activities are essential to maintain database consistency and other aspects of database server operation. However, they create overhead in the CPU and take up I/O bandwidth.
Configuration parameters that affect loggingThe LOGBUFF, PHYSBUFF, LOGFILES, LOGSIZE, DYNAMIC_LOGS, AUTO_LLOG, LTXHWM, LTXEHWM, SESSION_LIMIT_LOGSPACE, SESSION_LIMIT_TXN_TIME, and TEMPTAB_NOLOG configuration parameters affect logging. The LOGBUFF, PHYSBUFF, LOGFILES, LOGSIZE, DYNAMIC_LOGS, LTXHWM, LTXEHWM, and TEMPTAB_NOLOG configuration parameters affect logging.
LOGFILES and its effect on loggingThe LOGFILES configuration parameter, which specifies the number of logical-log files, affects logging.
Calculating the space allocated to logical log filesIf all of your logical log files are the same size, you can calculate the total space allocated to the logical log files.

Calculating the space allocated to logical log files

If all of your logical log files are the same size, you can calculate the total space allocated to the logical log files.

To calculate the space allocated to these files, use the following formula:

total logical log space = LOGFILES * LOGSIZE

If you add logical-log files that are not the size specified by the LOGSIZE configuration parameter, you cannot use the LOGFILES * LOGSIZE expression to calculate the size of the logical log. Instead, you need to add the sizes for each individual log file on disk.

Use the onstat -l utility to monitor logical-log files.