Issue: When starting an application after applying a maintenance release, you get an error message.
This error occurs if you do not export linked reporting objects before performing installing and configuring Essbase. (You import the linked reporting objects manually after configuring Essbase.)
Solution: Restore the Release 11.1.2 database, export the linked reporting objects, and restart the process of applying the maintenance release.
Issue: When you apply a maintenance release, the Essbase Server configuration fails. This issue occurs if you do not close Essbase Server before you begin applying the maintenance release.
Note: | Unless Essbase is configured as a service, Essbase Server does not close when you stop all services. |
Solution: Stop all EPM System processes (because a maintenance release affects all components in the Middleware home directory), verify that Essbase Server is stopped, and then try again to apply the maintenance release.
Also ensure that you have met the prerequisites discussed in “Maintenance Release Installation Prerequisites” in Chapter 3, “Installing EPM System Products,” of the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.