Audit Database file access

The Audit Database files and the records within them cannot be accessed except by the associated subsystem. To access these files to perform maintenance activities, you must close the database files. The Audit Database files can remain closed for limited periods, after which they automatically are re-opened. To change this time period, change the value of the audit file shift tuning parameter for the associated subsystem:

While an Audit Database file is closed, the associated subsystem accepts new, edited, and deletion requests and caches them for the PI Audit Database. When the database file is re-opened, the cache is processed and audit records are written to the Audit Database. Caching activity is written to the message log.

Several AVEVA™ PI System™ features are unavailable when the PI Audit Database files are closed. For example, you cannot create or edit points. To copy, delete, export, or move an PI Audit Database file, you must close the file, perform the required activity, and then promptly re-open the file. The schedule for removing and creating new PI Audit Database files depends on the frequency and number of audit records that are created. For example, PI AutoPointSynch (PI APS) modifies a property of a module to indicate the latest scan, which results in two audit records. If PI APS scans every five minutes, then hundreds of audit records are generated every day.

Note: On version 3.4.370 and later, it is not necessary to close audit files for backup.