• Article

Corruption of the Planning System Database

When the system database is corrupted, application-level property changes might get lost, including any new applications that you have created or any security data changes that you have performed.

When the system database is corrupted, it is possible that the BizSystem table or the security tables are corrupt. In that case, taking the application offline might not work.

Use the following procedure to restore the system database.

Restore the system database

  1. Verify that all Microsoft Office PerformancePoint Server 2007 applications are in an offline state by directly updating the BizSystem table. Because Planning System Database is corrupted, you cannot use Planning Administration Console to set all applications to an offline state. Run the following command:

    UPDATE BizSystem SET ApplicationStatusID = 32

  2. Verify that Planning Process Service and Planning Web Service are turned off.

  3. Restore the system database from the system database backup. You cannot change the system database name.

  4. Restore all available system database transaction logs that were good up to the failure point. This will bring the system 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, the transaction log must be enabled so that customers will always have transaction logs to apply over the last backup.

  5. Perform an IISRESET on the server running Planning Process Service, and then restart Planning Process Service and Planning Web Service.

  6. Launch Planning Administration Console, and then click Applications.

  7. Select all applications, and then click Take Online.

    Note

    Manually reset any security data changes you have made to your most recent good transactional log backup and system downtime.

See Also