So you did a fresh install of FDMEE, applied the latest patch, and then ran the config tool to "Create Database" and "Deploy To Application Server". This is how I do it, as I hate repeating the same activity twice (before and after patching).
But lo' and behold, the ODI tables (SNP* etc) are missing within the FDMEE repository. What's going on here?
On your FDMEE server, inspect this file. If FDMEE is clustered across multiple servers, you need to do this on just one server only. Let's assume your 1st FDMEE server is hosted on Windows and resides on the D drive:
Click the image if it doesn't render completely. I'm an EPM Infrastructure guy and am thus graphically-challenged. But the key nugget of information is this: Do you see "126.96.36.199.00" or "188.8.131.52.00"? Change that 3 to a 4!
The "FinancialDataQuality\odi\184.108.40.206.00" folder doesn't exist in this patch, so your ODI Master and Work repository tables never get created! The config wizard doesn't bark at you that you hit this problem.
Oh, there's one other thing. In the later FDMEE 220.127.116.11.2xx patches, you get only one shot at creating the ODI tables within FDMEE. Look within the same createODIRepos.bat file mentioned above. You'll see a line remarked out that was NOT remarked out in the unpatched 18.104.22.168.0 version of the software. Do you see it? Post in the comments below and I'll give you a hint. This remarked line is what makes the configurator wizard create the ODI Master and Work tables!
Fix the .bat file, re-run FDMEE's "Configure Database" task from the EPM Configurator on just one server. No need to redeploy to WebLogic. Restart FDMEE and you're good.
I can understand why Oracle decided to remark out that line; if you need to re-run "Configure Database" for FDMEE for any reason, maybe you don't want to lose your ODI customizations. But what if the ODI tables never got created to start with? Best to backup the original file, make your edits, run the configurator, and then when things are working OK you can restore your backup copy of the file to its original name.
Will this remain a bug in 11.2, or will it be fixed? Time will tell!
yes it worked. Thankyou very much for this information!!ReplyDelete