The following tests are available to run on applications:
Partially deleted—The application partially resides in the Dimension Server database and not in the object repository database. This problem can occur in cases where a database restoration was interrupted or a database has become corrupted. If this test fails, delete the application in Performance Management Architect and recreate the application.
This solution deletes the application from Performance Management Architect only. If this application has been deployed, manually delete the application from Shared Services and from the appropriate Hyperion product.
Inconsistent status—The status of the application is not consistent throughout the database. This scenario can occur if the application status is not consistent in the object repository database. This problem can also occur in cases where a database restoration was interrupted or a database has become corrupted. To resolve the problem: Synchronize the status information in the database.
This solution synchronizes all the status information in the database to ensure consistency.
Incomplete pending deployment—The application is in an incomplete deployment state. To resolve the problem:
Update the application to reflect a deployed state.
This solution is available if the application has been successfully deployed at least once. This reverts the state of the application to the previous successful deployed state—enabling you to redeploy.
Update the application to reflect a not deployed state.
This solution is available if the application has never been successfully deployed. This reverts the application to a not-deployed state—enabling you to deploy the application again.
Incomplete deployment—The application state reflects a partially completed deployment. This scenario can occur when the application is in a “deploy pending” state in the Dimension Server database and in a “deployed” state in the object repository database. This problem can also occur in cases where a database restoration was interrupted or a database has become corrupted. To resolve the problem: Redeploy the application.
This solution completes the deployment in the Dimension Server database and synchronizes the status between the Dimension Server and the object repository.
Partially deployed—The application is currently in a partially deployed state. This scenario can occur when the application is not deployed in the Dimension Server database and is deployed in the object repository database. This problem can also occur in cases where a database restoration was interrupted or a database has become corrupted. To resolve the problem:
Update the application to reflect a “not deployed” state.
You should manually delete the application, if it exists, from any Hyperion products.
Delete the application from Performance Management Architect only.
You should manually delete the application, if it exists, from any Hyperion products.
Partially deploy pending—The application is currently in a partial deploy pending state. This scenario is similar to the “incomplete deployment” scenario, yet there are further inconsistencies. If the application is in a partially deploy pending state, the pending deployment may not be the current deployment; therefore, it is deployment pending from a previously attempted deployment. This scenario can occur if there was a system failure when the application was deployed, followed by a correction to the application (a restoration to a deployed state), followed by another failure to deploy to the Hyperion product. Database corruption can also cause this problem. To resolve the problem:
Update the application to reflect a deployed state.
This solution is available if the application has been successfully deployed at least once.
Update the application to reflect a “not deployed” state.
This solution is available if the application has never been successfully deployed.
Inconsistent deployment state (deploy pending vs. not deployed)—The application is in both a not deployed and deploy pending state. This scenario can occur when the application is not deployed in the Dimension Server database and in a “deploy pending” state in the object repository database. This problem can also occur in cases where a database restoration was interrupted or a database has become corrupted. To resolve the problem: Update the application to reflect a “not deployed” state.
This solution reverts the application to its initial “not deployed” state.
Deploy pending—The application is currently in a “deploy pending” state. This problem can occur in instances where the Hyperion product that the application was deployed to became unresponsive. To resolve the problem:
Update the application to reflect a deployed state.
This solution is available if the application has been successfully deployed at least once. This reverts the state of the application to the previous successful deployed state—enabling you to redeploy.
Note: | If an application has not been deployed, you can resolve the problem by returning the application to a “not deployed” state or you can promote the application to a “deployed state”. |
Update the application to reflect a not deployed state.
This solution is available if the application has never been successfully deployed. This reverts the application to a not-deployed state—enabling you to deploy the application again.
Delete pending—The application is in a “delete pending” state. This scenario can only occur with a deployed application. Since the application is deployed, an application may be in a “delete pending” state when you attempt to delete the application from the Hyperion product, such as Planning, and the product becomes unresponsive. To resolve the problem:
Delete from Performance Management Architect only.
If the application resides in the Hyperion product, such as Financial Management or Shared Services, manually delete it.
Update the application to reflect a deployed state.
This solution reverts the application to “deployed” and removes the “deploy pending” state information, enabling you to attempt to delete the application in the Hyperion product to which it was deployed.
Application reserved for delete—The application has been reserved for deletion by the user but has not been deleted. This scenario can occur if an application is in the update process from a “delete pending” state. For example, if an attempt to delete the application failed, and the Dimension Server database was not updated to reflect that the application is not in a delete pending state. This problem can occur in cases where a database restoration was interrupted or a database has become corrupted. To resolve the problem: Remove the deletion reservation for the user and reset the application as valid.
This solution allows you to delete the application again.
Deployed but missing from Shared Services—The application does not exist in Shared Services but appears in Performance Management Architect. This problem can occur in cases where Shared Services stopped working. To resolve the problem:
Delete from Performance Management Architect only.
Use this solution only if you know that the application has not been deployed to a Hyperion product and currently exists in that product.
Change status in Performance Management Architect to “Not Deployed” and perform necessary cleanup.
Changing the status of the application reverts the application to a “not deployed” state in Performance Management Architect, enabling you to redeploy the application.
Reregister the application with Shared Services.
This solution synchronizes the application in Performance Management Architect and Shared Services.
Not deployed but in Shared Services—The application exists in Shared Services but shows as “not deployed” in Performance Management Architect. This problem can occur in cases where a database restoration was interrupted or a database has become corrupted. To resolve the problem:
Delete the application from Performance Management Architect.
This solution deletes the application from Performance Management Architect only. If the application resides in Shared Services or in the Hyperion product, such as Financial Management, manually delete it.
Manually delete the application from Shared Services.
To delete the application from Shared Services, log in to Shared Services, locate the project that the application was deployed to, and then delete the application.
Inconsistent deployment state (deployed vs. deploy pending)—The application is in both a “deployed” and a “deploy pending” state. This scenario can occur when the Dimension Server database shows that the application is deployed and the object repository database shows that the application is deploy pending. This problem can also occur in cases where a database restoration was interrupted or a database has become corrupted. To resolve the problem: Update the application to reflect a deployed state.
This solution synchronizes the object repository database with the Dimension Server database and places the application into a deployed state.
Inconsistent deployment state (deployed vs. not deployed)—The application is in both a deployed and not deployed state. This problem can occur when the Dimension Server database shows that the application is deployed and the object repository database shows that the application is not deployed. This problem can also occur in cases where a database restoration was interrupted or a database has become corrupted. To resolve the problem:
Delete from Performance Management Architect only.
Available if the application is registered in Shared Services. This solution deletes the application from Performance Management Architect. You should manually delete the application from Shared Services.
Update the application to reflect a not deployed state.
Available if the application has not been registered in Shared Services. This solution reverts the application to a not deployed state.
Invalid deployment information—The application is deployed to an invalid location. To resolve the problem is a two-step process:
Retrieve the instance name and cluster for potential deployed locations.
Select the correct deployment location and synchronize the deployment data with the new location.
Deployed but Classic Application in product—The application is deployed in the web application server and Dimension Server but is a Classic application in Planning or Financial Management. (This test is not applicable for Essbase or Profitability and Cost Management applications.) To resolve the problem:
Delete from Performance Management Architect only. After the application is deleted, you can run the Transform Classic to EPM Architect wizard to move the application to Performance Management Architect. See Transforming Classic Applications into Performance Management Architect.
Manually delete the application from Planning or Financial Management.
Deployed status but not in product—The application has been deployed in Performance Management Architect but has not been deployed to the appropriate product (This test is not applicable for Essbase applications.) To resolve the problem:
Change the status in Performance Management Architect to a “not deployed” status and clean up the application as necessary.
Retrieve the instance name, Web Server, cluster, data source (for Planning applications) and Shared Services ID to view the current deployment location.
If you run this test and the status displays “Error,” no solution is displayed. To resolve the problem, follow the instructions in the error message displayed in the Test Details area.
Not deployed status in EPMA, but in product—The application has not been deployed in Performance Management Architect but appears in the product, such as Planning, Profitability and Cost Management, or Financial Management. (This test is not applicable for Essbase applications.) To resolve the problem:
For Consolidation and Planning applications:
Delete from Performance Management Architect only. After the application is deleted, you can run the Transform Classic to EPM Architect wizard to move the application to Performance Management Architect. See Transforming Classic Applications into Performance Management Architect.
Manually delete the application from Planning or Financial Management.
For Profitability applications:
Clean up the application in Profitability and Cost Management. (Select “Clean up application,” and then select the appropriate instance name for Profitability and Cost Management.) If you choose to clean up the application it is deleted in Profitability and Cost Management.