I'm migrating a Hyperion Planning application (184.108.40.206) to a complete other environment (due to the split of the companies). I have read most post on otn, but unfortunately nothing that helped me to solve the issue, yet... I hope someone can help me. Thanks in advance!
I have executed the following steps:
1. Create a new Oracle database
2. Create a datasource to the Oracle database and to Essbase (both tested succesfully)
3. Create a fresh planning application (I have used a native Admin account and not the original owner)
4. Go into the database tables for the planning app and look at table HSP_USERS, store the SID value against user 50001
5. Go into the database planning system tables and HSPSYS_APPLICATION, clear out the version field for the application you have created - I did not do this since I could not delete this value. null is not accepted.
6. Stop Planning
7. Restore the planning application database over the one created in the first step (I had to drop the existing tables first)
8. Go into the HSP_USERS table and update the SID for user id 50001
9. Start planning
10. Log on to planning and I did see the webforms, etc as expected.
11. Now, when I try to refresh the database, I receive an error:
Cube refresh/create in progress
Step 4 Adding dimensions
Does anyone has an idea? Hope someone can help me since the deadline is getting closer and closer.
Are you definitely sure everything was migrated correctly, how did you restore the Oracle schema, usually you would drop the schema and recreate and then use something like impdp to import.
Thanks for your reply.
I have exactly done what you have described. I droped the schema and recreated it with an impdp to import.
But, in the meantime I have been investigating the dimensions and there's indeed something very wrong. Some dimensions have been mixed up. In the 'old' environment I have 10 stored dimensions and 4 attribute dimensions (as well as in EAS as in Planning, offcourse as you expect). In the 'new' environment, two stored dimensions have been mixed up with two attribute dimensions.... How is that possible?
I have never seen that. Could this be caused by the reason that we use a different version of Oracle (11G release 2 vs 10G (10.2.0.4))? Or went something wrong with exporting the schema...? Can you tell me what I can do to investigate this?
I shall describe how we did the migration.
We did a simple export (by the export uitility of Oracle, not datapump).
After we received the dump files we imported the data with the import uitility of Oracle.
The import goes fine without any errors. If the dump files were corrupt then the import would have failed.
Is it possible that something goes wrong during the export?
I can only give my opinion but if the tables don't match between source and target then problems will be experienced. If everything matches then you shouldn't get this sort of problem.
If you use expdp and impdp then both should produce a log to check whether everything was successful, you should also be able to compare that the export matches the import.
Solved the problem!
It was probably a corrupted file or the way of exporting which caused my error. I made another export via datapump and that one did the magic.
Now 'it seems' everything is working.