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.
Administrator's ReferenceThe HCL OneDB™ Administrator's Reference includes comprehensive descriptions of HCL OneDB™ configuration parameters, the system-monitoring interface (SMI) tables in the sysmaster database, the syntax of database server utilities such as onmode and onstat, logical-log records, disk structures, event alarms, and unnumbered error messages.
Configuring and monitoring HCL OneDB™
Database configuration parametersThe HCL OneDB™ database server uses a configuration file, which is called the onconfig file, during initialization. This file contains default configuration parameter values. You can modify the parameter values to improve performance and other characteristics of the instance or database.
TEMPTAB_NOLOG configuration parameterUse the TEMPTAB_NOLOG configuration parameter to disable logging on temporary tables.

TEMPTAB_NOLOG configuration parameter

Use the TEMPTAB_NOLOG configuration parameter to disable logging on temporary tables.

onconfig.std value

TEMPTAB_NOLOG 0

values

0 = Enable logical logging on temporary table operations

1 = Disable logical logging on temporary table operations

2 = Enable logical logging on temporary table operations for primary server and disable logical logging on temporary table operations for secondary servers(HDR, RSS and SDS).

On primary/standard server: same behavior as 0

On secondary servers: same behavior as 1

takes effect

After you edit your onconfig file and restart the database server.

When you reset the value dynamically in your onconfig file by running the onmode -wf command.

When you reset the value in memory by running the onmode -wm command.

Usage

This parameter can improve performance in application programs because it prevents HCL OneDB™ from transferring temporary tables over the network. The setting can be updated dynamically with the onmode -wf utility.

If you enable this setting, be aware that because no data is logged when using temporary tables, rolling back a transaction on a temporary table will no longer undo the work in the temporary table.

For HDR, RSS and SDS secondary servers in a high-availability cluster, logical logging on temporary tables should always be disabled by setting the TEMPTAB_NOLOG configuration parameter to 1 or 2.

When server type changes, logging for temporary tables will be enabled/disabled depending on the current server role. It will be effective for temporary tables created afterwards.

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.