FDMEE Migration to 11.2.X
If you are upgrading to Hyperion 11.2.X from 11.1.2.4 and FDMEE is part of your migration, this article is for you. I need to keep up with Dave Shay and Jeff Henkel with the 11.2.X articles.
In my testing and I used 11.2.2 and 11.2.4 I followed the documentation Oracle provides and used the FDMEE integration package. I used Microsoft SQL. In my lab and my tests I always use Microsoft SQL. I don't know if the same issue exists in Oracle, but since the issue is table related, I would presume YES. Notice that I am not "assuming".
After you run the SSIS integration package the first time, check the new 11.2.X FDMEE application to see what metadata artifacts are missing. You will find them.
The issue occurs when you run the SSIS or FDMEE integration package. While it will run and show 100% success, you will get "Warnings" and then Warnings translate into not everything migrating over. I found load rules and some mappings did NOT migrate over. See the warnings in the log below.
So how to we correct the issue:
- Identify the tables on the data source referencing to FDMC_* and APPLICATION_ID columns in the new 11.2.X Database Table
- Delete the two columns FDMC_* and APPLICATION_ID from those tables – sample screenshots below.
- The tables are TDATASEG, TDATAMAP and confirm no other tables have an FDMC_* or Application _ID table.
Right click on the column and select "Delete Column"/
Once all the columns are deleted, take an LCM export of the Global Rules, Maps and any other artifacts that are missing. Load the artifacts via LCM import.
Your FDMEE application in 11.2.X should now be ready to go.
Any questions or comments please feel free.
And a big THANK YOU to John P (last name withheld so as not to alert the Hyperion police) for all the help with this issue.
Hi Michael Fredericks can you share your email Id ? And I can send you the details of the errors. Sorry I am not able to send you DM since it is locked.
Hi Michael Fredericks, so I should delete those missing columns in source db and re run the utility? And do LCM for those missing artifacts ? We tried to add all those missing columns in Target db and tried the LCM and also re running the utility but nothing really worked 😞
Hi Michael, Thank you for the extremely helpful doc. We are currently running the same process but we are stuck now, we don't see data load rules and mapping coming over with the utility. As per doc we delete the columns in Target db and try importing the data load rules & mapping but LCM throws us an error. Any suggestions?
Thanks Michael