Administering Reports › Administering the Reporting Database

Administering the Reporting Database

If you do not routinely purge the CA Process Automation Reporting database, this database continues to grow.

Important! When CA Process Automation attempts to add data to a full Reporting database, that data is lost. If the Reporting database is not isolated from other CA Process Automation databases, a full database can cause CA Process Automation to stop working. If other applications share the Reporting database server space, the outage could extend beyond CA Process Automation.

If you require reporting data to be retained for compliance with regulations, back up the reporting data and move your backup to a secure location. Then, purge the reporting database. Purging the database prevents the loss of data that is caused by attempting to add data to a full database.

Administrators can purge reporting data on demand or on a configured schedule.

Follow these steps:

1. Click the Configuration tab.
2. From the Configuration Browser, select the Domain, and click Lock.
3. Click the Properties tab.
4. Specify the requirements for purging reporting data that was generated on Orchestrators in this domain.
   1. Specify whether to purge reporting data daily, and if so, specify the time of day to start the purge. For example, to start the purge at 6:30 PM, specify the military time equivalent, 18:30.
   2. If you specified a purge schedule, indicate the number of days to retain reporting data before it is purged. For example, an entry of 14 specifies to purge all reporting data that is more than two weeks old.
5. Alternatively, purge reporting data on demand where you specify the date range for when the reports were generated.

   Click the Delete Reporting Data button and specify a date range for the reporting data to delete.

6. Click Save.
7. Click Unlock.