During normal operation, messaging databases work independently of each other under the direction of a set of software and hardware processes. These processes coordinate the files, databases, and system hardware.
Since databases are handled separately, it is possible for one database to contain information that conflicts with another database. For example, if a subscriber is removed from the messaging database, other databases could still contain messages addressed to that subscriber or mailing lists that include that deleted subscriber's name.
To reconcile possible conflicts among databases, software programs called auditsrun automatically (or can be performed on demand) to check for inconsistencies and, when possible, update information in databases to correct problems. For example, audits remove all references to a deleted subscriber, which includes deleting the subscriber's name from mailing lists and canceling message deliveries to that subscriber.
The messaging feature package performs many regular internal audits on the databases of information it maintains. These databases include:
The networking database audit consists of a series of internal checks. For example, these checks verify that files are not corrupted and that values within the files are within the proper ranges. The networking database consists of two parts, the networking administration database and the remote subscriber update status database.
The switch integration software in the system is part of a layer that is accessible to all the software applications. Therefore, the software maintains its own database of subscribers to execute the switch-related requests from the applications. Subscribers are added to the switch integration database automatically after being added to an application, such as messaging.
Because the switch integration software maintains its own database, it must be synchronized periodically with the other application databases. This synchronization is accomplished through several audits.