solidDB^® Audit Info feature is based on creating audit info files per server instance. In HotStandby, a logical database is represented by a pair of two servers. To establish an audit info track for the logical database, merging audit info files from two servers is required. In merging, following principles should be followed.

Since there is no global sorting key, the field time is best column to be used as a merging key. The value is based on system clock on each server. Hence, synchronizing system times is strongly recommended when collecting an audit trail of HotStandby pair.

Because all write operations are run in primary database and exact order of read operations is not absolutely critical for correct audit results, merging the audit files from two sources will not lead to possible misinterpretations to records having an impact on database state.

In the event of multiple consecutive changes in HotStandby roles within periods that are smaller than time difference in system clocks in the two systems, it is possible that exact order of write operations will be difficult or can not be deducted from audit info records. For example, database state after statements UPDATE X=X*100 and UPDATE X=X+1 depends on the order of statements.