Corruption of a single application database
If only one application database is corrupted, use the following procedure.
Restore a corrupted single application database
Launch Planning Administration Console and connect to Planning Server. On the navigation pane, click Applications.
Select the corrupted application, and then click Take Offline.
Select Planning Process Service, and then click Take Async-Offline. It is possible that the database corruption might cause the Planning Process Service to have errors. Even after the application is in Async-Offline state, you might continue to see the errors because of the corrupted state of the application database.
Note
If the application list on Planning Administration Console does not show that application database, the Planning System database is corrupted.
Stop Planning Process Service on all servers running Planning Server before restoring the application databases.
Restore the application database from the backup. Do not rename the application database here.
Restore all available application database transaction logs that were good up to the failure point. This will bring the application database to the latest state possible. The failure point is usually only a few minutes away from the latest state of the database. In all production systems, transaction logs must be enabled so that customers will always have transactional logs to apply over the last backup.
Enable Service Broker on the restored application databases.
For example:
ALTER DATABASE [PlanningApplicationDatabase] SET ENABLE_BROKER
Perform an IISRESET on Planning Process Service and restart Planning Server.
From the Applications page within Planning Administration Console, select Planning Process Service, and then click Take Online.
Examine the operational report to identify the jobs that were not completed. Resubmit any job that failed.