This section provides notes about version upgrading when the security audit facility is used. For details about version upgrading, see the manual HiRDB Version 8 Installation and Design Guide.
If version upgrading changes the audit trail format for audit trail files, take the following action before version upgrading:
Version upgrading may 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.
If version upgrading increases the number of audit trail events, the volume of audit trail output may increase. Therefore, before version upgrading, 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 may arise:
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 older 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.