If version upgrading changes the audit trail format for audit trail files, take the following action before version upgrading:

• Use the pdaudswap command to swap audit trail files and use the pdload command to register the content of the file before swapping in the audit trail table.
  

  Reference note

  Because there are no triggers for output of an audit trail during HiRDB termination and for swapping audit trail files before HiRDB starts after a version upgrade, an audit trail in the old format collected during HiRDB termination and an audit trail in the new format collected during HiRDB startup will both exist in the same file. For this reason, HiRDB is designed to permit you to load data into the audit trail table even when audit trails in old and new formats coexist in the same file.

Version upgrading might add columns to the audit trail table. The column structure of the audit trail table can be changed by HiRDB by executing the pdvrup command. If data already exists in the audit trail table, NULL values are set in the added columns.

Furthermore, adding columns might cause the length of the lines in the audit trail table to exceed the RDAREA page size. Because this causes audit trail table search performance to decline, we recommend that you estimate the length of the lines in the audit trail table and increase the page size of the RDAREA that stores the audit trail table. For details about page size design, see 24.4.3(2)(a) Estimating the size of the RDAREA to store the audit trail table in the HiRDB Version 9 Installation and Design Guide.

If version upgrading increases the number of audit trail events, the volume of audit trail output might increase. Therefore, before performing a version upgrade, re-estimate the size required on the disk that stores audit trail files.

This is applicable when audit trails are to be output for all events (CREATE AUDIT FOR ANY is specified). In such a case, if version upgrading increases the number of new events (such as utility manipulation events), audit trails are also collected for the utility manipulation events.

If you do not wish to collect an audit trail for a newly added audited event, do not use CREATE AUDIT FOR ANY when defining audit trail collection. Instead, define individual audit trails (CREATE AUDIT FOR SESSION, CREATE AUDIT FOR PRIVILEGE, ...).

Execute the pdload command only after version upgrading succeeds. If this command is executed before version upgrading succeeds, the following problems might arise:

• Upgrading to version 07-02 or later from a version earlier than 07-02 (but later than version 07-00)
  When HiRDB is started after version upgrading, an audit trail in the new format is output to the audit trail file. If the earlier version is restored from this status, and then the pdload command is used to register an audit trail in the audit trail table, correct operation cannot be guaranteed. In such a case, after the earlier version has been restored, use the pdfmkfs command to initialize the HiRDB file system area for audit trail files.
  
• Upgrading from version 07-02 or later
  In 07-02 or later versions, if the format of the audit trail that is output does not match the format supported by the applicable version, the KFPS05753-W message is output and the audit trail is deleted.
  

Before version upgrading, make a backup of the RDAREAs that store an audit trail table. If version upgrading fails and you need to revert to the earlier version, restore the RDAREAs that store the audit trail table from the backup.

If no backup was made, use DROP TABLE to delete the audit trail table, then use the pdmod command to re-create the audit trail table. In this case, the data stored in the audit trail table is deleted.