Nonstop Database, HiRDB Version 9 System Operation Guide

[Contents][Index][Back][Next]

24.1.8 Facility for automatically loading audit trail table data

Organization of this subsection
(1) About the facility for automatically loading audit trail table data
(2) Application conditions

(1) About the facility for automatically loading audit trail table data

When an audit trail file is swapped in response to any of the triggers listed below, the facility for automatically loading audit trail table data causes HiRDB to automatically start the database load utility (pdload command), and loads the contents of the audit trail file to the audit trail table. When this facility is used, there is no need for data to be loaded by an auditor, and an audit can be carried out by simply referencing the audit trail table.

The audit trail file to be automatically loaded is swapped when the following events occur:

 
Note
  • When the audit trail file is swapped because of an error, data is not automatically loaded.
  • In the case of a HiRDB parallel server configuration, the pdload command is started for each unit.

(2) Application conditions

The facility for automatically loading audit trail table data provides the advantage of reducing the auditor's workload. There is also a disadvantage, however. Because data loading is executed during online operations, the system load increases, adversely impacting processing performance. Decide whether to use the facility by taking into consideration the advantages and disadvantages described in the following table, the environment, and the operating method.

Table 24-3 Advantages and disadvantages of using the facility for automatically loading audit trail table data

Used? Advantages Disadvantages Recommended environment and operating method
Yes
  • No need to execute the pdload command, and an audit can be carried out by simply referencing the audit trail table.
  • The auditor's workload is reduced because all that is needed is to manage the capacity and status of the audit trail table.

  • Regardless of the traffic level, data is loaded when the audit trail file is swapped, and therefore jobs might be adversely affected.
  • Because both the auditor and the system (pdload command) reference the audit trail table, the locking process must be managed.

  • An environment in which the hardware performance is high and execution of the pdload command will not adversely affect processing performance.
  • An environment in which referencing the audit trail table based on a NOWAIT search is sufficient.
  • An environment in which you want to check the audit trail constantly.
No
  • When you load data, you can select time spans in which the traffic level is relatively low.
  • Because only the auditor references the audit trail table, there is no need to manage the locking process.

  • The pdload command must be executed to carry out an audit.
  • It is necessary to manage the capacity and status of both the audit trail file and the audit trail table.

  • An environment in which processing performance during online jobs must not be affected.
  • An environment in which referencing the audit trail table based on a NOWAIT search is insufficient.
  • An environment in which you want to check the audit trail only when a problem occurs.