Corruption of the Planning Service Database
Planning Process Service processes three types of requests: workflow jobs, audit, and logging.
For workflow jobs, all data used by the Planning Process Service server is stored in the application database for each application. For audit and logging purposes, the data used by the Planning Process Service server is stored in the service database for all applications within the same Planning Server system.
If you have the last backup of the service database, you can restore it and all transactional log backups after the last database backup. If the restored service database backup is a few minutes older than the latest service database, the only possible data loss is the auditing and logging data for all applications within that few minutes of failure.
Recovery steps when the service database is down and no application is online
Launch Planning Administration Console.
On the left navigation pane, click Applications, and then select all applications.
Click Take Async-Offline.
Stop Planning Process Service before you restore the Planning Service Database.
Restore the last backup of the service database. Note that the service database contains all auditing and logging requests for the application database. The unprocessed auditing and logging requests from the time of recovery state and the time the service database failed will be lost.
Restore all transactional log backups up to the latest point available. Usually, it is a few minutes away from the latest state of the database.
Perform an IISRESET on the server running Planning Process Service, and restart Planning Process Service.
After the system is restored, review all pending jobs. Cancel any jobs that were processed between the time of the latest backup and the time the system was restored.
On the Applications page of Planning Administration Console, select each application.
Click Take Online to bring all the applications to an online state.