General Guidelines for Migrating a Classic Hyperion Planning Application (Environment Migration –Oracle Db)

Scenario 1: When a single application user (schema) resides in an Oracle Database.

A: When the application is not created in the target environment

Steps to be followed

Create a user in Oracle (same name as the source database). Create a Data Source with the Hyperion Configuration Utility. Create an application for the above mentioned Oracle user. Continue with the below mentioned steps.

B: When an application resides in the target environment.

Stop the Hyperion Planning in the “Services.msc” Console. Log in Oracle with the appropriate login credentials. Check/verify the Oracle SID by executing the command

SQL> select INSTANCE_NAME from v$instance;

Delete (cascade option) the oracle user (created above) in the target database. Re-create the user, keeping the name same. Now, Import the restore file dump(source application) into the target database as

Imp user/password file=C:\filename.dmp full=y

Upon a successful import, start the Hyperion Planning service.

Import the data into Essbase database and execute the appropriate (aggregation) scripts if required.

You should be able to see the restored (migrated) application with all the dimensions, data forms, etc.

Verify the application availability by logging into it with different usernames, accessing the forms and data values.

NOTE : If Encountered with a “Failed to sync the user provisioning error”