SQL/MP Installation and Management Guide

Planning Database Security and Recovery
HP NonStop SQL/MP Installation and Management Guide—523353-004
4-13
Guidelines for Configuring TMF
audited. Consider using the TMF subsystem to audit all tables, views, and indexes to
ensure both the integrity of the database and a timely recovery from media failures or
incomplete transactions.
As a general rule, the TMF subsystem must be available when users are running SQL
application programs or using SQLCI. In particular, the TMF subsystem is required for
these operations:
•
DDL statements
•
SQL compilations, whether explicit or requested interactively through SQLCI or
through dynamic SQL applications
•
DML statements performing INSERT, UPDATE, or DELETE operations on audited
tables or views
•
SELECT statements not using BROWSE ACCESS on audited tables or views
Some previously compiled programs or previously prepared DML statements, however,
do run successfully when the TMF subsystem is unavailable, provided that the
statements do not require TMF transactions. These DML statements include:
•
Queries (SELECT statements or cursor operations) that specify BROWSE access
on audited tables and views
•
SELECT, INSERT, DELETE, and UPDATE statements that access only nonaudited
tables and views
Nevertheless, these queries and statements also fail if automatic recompilation is
required; for example, if an object in the access path becomes unavailable.
Guidelines for Configuring TMF
The appropriate version of the TMF subsystem (as described under Hardware and
Software Requirements on page 2-1) must be installed, configured correctly, and active
for transaction processing on a system before you install SQL/MP.
These guidelines apply to configuring the TMF subsystem for use with SQL/MP.
Determining What to Audit
You should audit all volumes on your system except the TMF audit-trail volume. Tables
in which data changes, during INSERT, UPDATE, or DELETE operations, need
auditing to protect the consistency of the database. This configuration enables you to
place SQL objects throughout the system. Normally, the volume that contains the audit
trails is not audited; therefore, SQL objects would not reside on this volume.
For certain systems with limited disk space, you can configure the TMF subsystem with
SELFAUDIT, which allows the volume containing the audit trails to be audited also.
With this configuration, SQL objects can reside on the same volume as the audit trails.
Certain tables should not be audited. For example, a log file should not be audited
because it typically records various events. If a log file is audited, the TMF subsystem