Logging System Configuration

The logging system implements a circular transaction log file for the management of transactions within the installation. It ensures that log records are written in a way that makes them accessible to the Recovery Server and archiver process. All DBMS and Star Servers in the installation, as well as the archiver process share the logging system. Reconfiguration of the logging system is normally required to provide optimal performance for an installation.

Configurable parameters for the transaction log files include: transfer block size, buffer count, full limit, logging memory status, location, name, and number of partitions.

For instructions on configuring logging parameters, see the following topic in Configuration Manager online help:

• Parameters Page, Logging System Component

For a detailed explanation of the logging system, see the Database Administrator Guide. For instructions on creating and configuring a raw log file for UNIX platforms, see the Installation Guide.

Note: Before making changes to the transaction log, Ingres must be shut down using Ingres Visual Manager, Service Manager, or the ingstop command. This ensures all processes are stopped correctly and completely.

Multiple Log Partition Configuration

Ingres allows both the primary and dual transaction log files to exist on multiple devices (up to 16). Ingres improves logging system performance by allowing it to write to multiple disk devices and, on 32-bit file systems, allowing the total log file size to be greater than 2 GB.

You can configure multiple log partitions using the log_file_parts parameter. When configuring multiple log partitions, keep the following in mind:

• All log partitions must be the same size
• The primary and dual transaction logs must use the same number of partitions

For instructions on configuring multiple log partitions, see the following topic in Configuration Manager online help:

• Parameters Page, Logging System Component

Primary Transaction Log and Dual Transaction Log

If the Ingres installation is running, configurable information on the primary and dual transaction log files is readonly. If Ingres is not running, and no recovery is required from a system failure, various operations are allowed, including editing the log file name, setting the log size per file, and adding, modifying or deleting locations for the primary and dual transaction log files.

For instructions on configuring transaction log parameters, see the following topic in Configuration Manager online help:

• Primary Log Page, Transaction Log Component