This content has been marked as final. Show 7 replies
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.