Essbase Rebuild Procedure

This is on version 11.1.1.3 
Reason: Due to Corrupt openldap, and possibly RDBMS

Symptoms : Essbase service is not starting up, if we start also stops immediately
                      Unable to refresh security from Shared Services

Make sure you have restored the backup of Essbase Database(RDBMS) incase RDBMS is corrupted.

1. Check you have a backup of substitution variables and data, an export from

    CSSImportExport utility, and the Essbase Filters.

2. Stop Essbase if Essbase is running.

3. Delete the existing Essbase Server Project in Shared Services, or just the affected server

    if you have multiple Essbase Servers registered. Right-click on the Project > Delete.

4. Back up 5 files from \Hyperion\products\Essbase\EssbaseServer\bin

            ESSBASE.SEC
            ESSBASE.BAK
            ESSBASE.BAK_startup
            ESSBASE.BAK_preUPM
            ESSBASE.BAK_postUPM

    You may have only 3 of these files if Essbase was not previously externalized.

5. Rename these 5 files from \Hyperion\products\Essbase\EssbaseServer\bin

6. Launch Essbase in the foreground (Start > Run > cmd > essbase)

7. When prompted for a new username and password for the Essbase supervisor user, use

    the same username and password as previously if at all possible.

8. Essbase should start successfully and say “Waiting for client requests”. A new SEC file

    will have been created. (Essbase is not yet running externalized)

     If it is not starting and Saying that Environment Variables ESSBASEPATH and   

     ARBORPATH not present just add them in Environment variables and repeat step 8.

9. Log into the EAS console, add the Essbase Server if it isn’t already visible. Use the
    supervisor user you just started Essbase with to make the connection between EAS and
    Essbase.

10. Recreate Applications:
      Existing applications will not yet be visible in the list of applications under the Essbase
      Server. The physical applications do still exist. The Essbase.SEC file simply does not
      yet contain pointers to them.
     To map them you will need to create “new” applications with the exact same names and
     same application types (ASO or BSO) as the existing Applications:

     Right-click on Applications > Create applications > Using Aggregate storage or block
     storage

    The application names you enter must be exactly the same as your existing applications
    (including the case) for this procedure to pick up the application from the file system.

    You can check application names by looking at the directory names under
    \Hyperion\products\Essbase\EssbaseServer\app\

    Repeat this procedure for all applications that had disappeared from the list.
    Remember that the compression always reverts back to NO COMPRESSION on all
    databases so this will need to be changed as well as your general settings and caches if
    changes were made.

11. Externalize Essbase:
      In EAS Right-click on Security > Externalize Users. Choose the bottom option and put in
      the same password as you used in step 6 as the password.
      After externalizing, Essbase Server will be added to Shared Services.

12. Recreate your substitution variables

13. Re-create your location Aliases

14. Re-create your Essbase Filters

15. Import the security for Essbase from the previously created CSSImportExport to get
      the provisioning back