Your provisioning system design should specify the transaction-logging support required for each namespace and its procedures. The transaction log requires no daily maintenance. If specific conditions require changes to your auditing support, you can use Provisioning Manager to administer the transaction log as follows:
The information provided in Provisioning Manager about each transaction log includes the name of the server hosting the transaction log, the status (active or inactive) of the transaction log, the name of the database where the transaction log is maintained, and the name of the server acting as an auditing and recovery manager for the transaction log.
For more information, see To view the names and status of provisioning servers.
You can activate or deactivate a transaction log. Deactivating a transaction log suspends all transaction logging on a server. When you deactivate a transaction log, MPF completes any requests currently running, but no new transactions can be run using the deactivated transaction log. If you deactivate all transaction logs, MPF stops processing all requests and returns an error code to the user, indicating that the transaction cannot be initiated.
For more information, see To activate or deactivate a transaction log.
For more information about transaction logs, see Transaction logs.