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.
AUTO_LLOG and its effect on loggingInsufficient logical logs can affect performance by triggering frequent checkpoints, blocking checkpoints, or long checkpoints. The AUTO_LLOG configuration parameter controls whether the database server automatically adds logical logs to improve performance.

AUTO_LLOG and its effect on logging

Insufficient logical logs can affect performance by triggering frequent checkpoints, blocking checkpoints, or long checkpoints. The AUTO_LLOG configuration parameter controls whether the database server automatically adds logical logs to improve performance.

If you created a server during installation, the AUTO_LLOG configuration parameter is enabled automatically. Otherwise, you can edit the value of the AUTO_LLOG configuration parameter.

If the AUTO_LLOG configuration parameter is enabled, the database server automatically adds logical log files under the following circumstances:

When a substantial portion of the last 20 checkpoints were caused by logical logs filling up
When inadequate logical log space causes a blocking checkpoint
When inadequate logical log space causes a long checkpoint

The AUTO_LLOG configuration parameter also specifies the dbspace for new logical log files and the maximum size of all logical log files before the server stops adding logical logs for performance. The following guidelines show estimates of the maximum amount of space for logical logs that you might need, depending on the number of concurrent users who access your database server:

1 - 100 users: 200 MB
101 - 500 users: 5 MB
501 - 1000 users: 1 GB
More than 1000 users: 2 GB

The settings of the AUTO_LLOG configuration parameter and the DYNAMIC_LOGS configuration parameters do not interact.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box.