PI Data Archive file types

Files that comprise:

Description

Point Database (PI Base Subsystem)

pipoints.dat

Point definitions. This binary file stores the point database.

piptattr.dat

Attribute set definitions.

piptclss.dat

Point class definitions.

pidigst.dat

Stores the digital sets. This file references names stored in pidignam.dat.

pidignam.dat

A binary file that stores each unique digital state name.

piptsrcind.dat

Point source index (allows for quick lookup by point source). Automatically rebuilt if it does not exist.

Module Database (PI Base Subsystem)

PIModuleDb.dat

PI Module Database.

PIModuleUnitDb.dat

Batch process unit index; an index of all modules with the IsPIUnit flag set to true. Automatically rebuilt if it does not exist.

Note: Delete this file before a backup restoration.

Security (PI Base Subsystem)

piidentity.dat

PI identity definitions; upgraded Data Archive servers contain piusr.dat and piusrgrp.dat

piidmapping.dat

PI user contexts; a simplistic mechanism to tag PI users. This file is deprecated, but the PI SDK has a public interface for it.

piidentmapping.dat

PI mapping definitions.

piacl.dat

Access control list (ACL) definitions for all Data Archive secure objects (points, modules, and database security databases).

pidbsec.dat

PI database security definitions.

pitrstrl.dat

PI trusts definitions.

pifirewall.tbl

PI firewall table.

piusrctx.dat

PI user context database.

Time-Series Database (PI Snapshot Subsystem and PI Archive Subsystem)

piarcmem.dat

Snapshot table. This binary file contains the most recent values that were sent to the Data Archive server. PI Snapshot Subsystem periodically writes the latest snapshot values to this file.

pimapevq.dat (or pimq####.dat)

Memory-mapped event queue files. Most systems use the default single file pimapevq.dat. In situations that require multiple event queues, the files take the naming convention of pimaNNNN.dat, where NNNN is an integer.

The memory-mapped event queue serves two purposes. First, it used for moving events from PI Snapshot Subsystem to PI Archive Subsystem. PI Snapshot Subsystem places events which pass compression into this queue. PI Archive Subsystem takes these events and writes them to the archive. Second, this file stores events when PI Archive Subsystem cannot process events, such as during archive shifts and when the archive process is shut down.

This file is a memory-mapped file, which allows for high speed in-memory access with the security of being safely backed up to disk.

piarstat.dat

List of registered archive files. This binary file, called the archive manager data file, keeps track of registered archives. PI Archive Subsystem requires this file. If you are having trouble with archive file registration, do not delete this file. Instead, see Repair the archive manager data file.

Data Archive Messages (PI Message Subsystem)

pimsgtxt.dat

Message text resource. This binary file stores formatted message strings used by the pigetmsg utility.

pimdf.dat

Message definitions.

pimsg_yymmdd.dat

Message logs, where yymmdd represents date covered by file.

Batch Database (PI Batch Subsystem)

piptunit.dat

Legacy Batch Units (deprecated)

piptalia.dat

Legacy Batch Aliases (deprecated)

Miscellaneous

shutdown.dat

A text file that contains directives that tell the PI Shutdown Interface which points should receive shutdown events.

pilastsnap.dat

Determines the Data Archive shutdown time. This binary file stores the timestamp of the last completed snapshot flush to disk. On Data Archive startup, this timestamp is assumed to be the shutdown time and is used as the timestamp for shutdown events. On orderly shutdown, this file contains the true shutdown time. With a system crash, such as a power failure, the snapshot may be as old as the snapshot flush cycle time period. The snapshot flush cycle is controlled by the SnapFlushCycle timeout parameter, which is 15 minutes by default.

pitimeout.tbl

Tuning parameter definitions.