Here's one that struck me:
This entry happens to be the very first thing we see within the log. The [timestamp] just so happens to correspond with the first-time DB Config and WebLogic deployment of FDMEE.
[timestamp] Starting import of the adapters.
[timestamp] [erpi] [ERROR]  [oracle.erpi.localization] [tid: 1] [ecid: 07669c97-8ef1-4a3c-aa80-8e1c25fcd267-00000002,0] Error incountered while importing adapters.[[
java.lang.RuntimeException: Either directory F:\Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\odi\184.108.40.206.00\adapters does not exist or is not a directory
Bear in mind the configtool's graphical interface did not report any errors here. Config/Deploy status for FDMEE was given a green checkmark.
Now, does the directory \Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\odi\220.127.116.11.00\adapters actually exist? Of course not! We're installing EPM 18.104.22.168.
And guess what? Directory \Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\odi\22.214.171.124\adapters does exist and I see adapter XML files in there for JDE and Open Interface.
So I rolled the dice, created an empty directory \Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\odi\126.96.36.199.00 and copied 188.8.131.52\adapters to 184.108.40.206.00\adapters.
Just to be on the safe side, I used epmsys_registry.bat command-line options to blow away the FDMEE stuff from the EPM System Registry, so I could return to configtool and run a fresh DB config and deploy for FDMEE.
This time around, no errors in aif-localization.log and the adapter imports were reported as a success:
I'm curious to know if anyone out there has tried to use FDMEE 220.127.116.11 yet and ran into trouble using either the JDE or Open Interface adapters. If so, please post your observations, then try the above and advise our readers if this info helped!
[new timestamp] [erpi] [NOTIFICATION]  [oracle.erpi.localization] [tid: 1] [ecid: 29cae779-08ae-4e92-a5c8-df87557c5c15-00000002,0] Starting import of the adapters.
[new timestamp] [erpi] [NOTIFICATION]  [oracle.erpi.localization] [tid: 1] [ecid: 29cae779-08ae-4e92-a5c8-df87557c5c15-00000002,0] Importing adapter F:\Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\odi\18.104.22.168.00\adapters/JDE_Adapter.xml
[new timestamp] [erpi] [NOTIFICATION]  [oracle.erpi.localization] [tid: 1] [ecid: 29cae779-08ae-4e92-a5c8-df87557c5c15-00000002,0] Finished Importing adapter F:\Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\odi\22.214.171.124.00\adapters/JDE_Adapter.xml
[new timestamp] [erpi] [NOTIFICATION]  [oracle.erpi.localization] [tid: 1] [ecid: 29cae779-08ae-4e92-a5c8-df87557c5c15-00000002,0] Importing adapter F:\Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\odi\126.96.36.199.00\adapters/Open_Interface_Adapter.xml
[new timestamp] [erpi] [NOTIFICATION]  [oracle.erpi.localization] [tid: 1] [ecid: 29cae779-08ae-4e92-a5c8-df87557c5c15-00000002,0] Finished Importing adapter F:\Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\odi\188.8.131.52.00\adapters/Open_Interface_Adapter.xml
[new timestamp] [erpi] [NOTIFICATION]  [oracle.erpi.localization] [tid: 1] [ecid: 29cae779-08ae-4e92-a5c8-df87557c5c15-00000002,0] Finished importing all adapters.
Hi Dave, yes we started testing FDMEE 11.2, not specifically with JDE adapter though. But in our system, we see the correct path and the JDE_Adapter file below it, in D:\Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\odi\184.108.40.206\adaptersReplyDelete
and we do not have that \odi\220.127.116.11 folder you mention.
the Open_Interface_Adapter.xml is also there in the above mentioned 18.104.22.168\adapters folder.
Hi Karin. Yes, this is exactly what I'm talking about. Please check the top few lines of \Oracle\Middleware\user_projects\\diagnostics\logs\aif\aif-localization.log on your FDMEE server(s) for the error I mentioned.Delete
The config tool seems to expect the 22.214.171.124 folder to be present, likely due to a bug.
Best of luck in your testing!
Put your EPM Instance name "epmsystem1" or whatever in between user_projects\ and diagnostics\ :) The comment editor didn't like how I noted that in my comment above!Delete
thanks Dave. We have actually been testing 11.2 EPM most products (migrated apps/data from .1.2.4) for over 3 weeks now and issues to fix were more of functional nature for data export / scripts.Delete
I have tracked down/compared the aif localization log steps from .1.2.4 with 11.2 and found that the "importing adapters" did put the JDE and Open.. adapter XMLs and their assocated files correctly into Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\odi\126.96.36.199\masterrep and Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\odi\188.8.131.52\workrep in the same way for 11.2 as they are present for .1.2.4
nothing seems to be missing there. Also in ODI studio and console, we were able to see the oracle JDE data server for example.
Don't think any need for reconfig there.
Good stuff. Testing adapters in in my To-DO list.
ODI is now 12c so adapters must be reconfigured as well.
Will keep you posted.
Plan is to upgrade to 11.2, using JDE adapter as described above. Can anyone confirm that the adapter works in the latest version of 11.2 by copying over the adapters and redeploying?ReplyDelete
Deleted this by accident, so re-posting.Delete
Hi! I've learned the upgrade process for FDMEE+ODI is extremely customer-specific. Some have been flawless, and others required rebuilding ODI from scratch.
The SQL-to-SQL adapter is especially problematic. Oracle posted a knowledge base article about it just within the past 2 weeks. Here's the main bit to be aware of:
If your FDMEE process uses a filter in the Parameter column in the Source Adapter, ODI 12c does not like if the Parameter name is exactly the same as the table column name. You have to manually wipe it out, and recreate it with a different Parameter name.
For example, suppose your source table has a column named ENTITY and your FDMEE source adapter has a parameter in 184.108.40.206 that was named Entity and it always worked..... guess what you get to do in 11.2 / ODI 12.c. You delete it and recreate the parameter name as Entity_P or something like that.
Nice blog. We are upgrading Hyperion 220.127.116.11 to Hyperion 11.2.x and also standalone ODI from 18.104.22.168 to 12c. Oracle said that any version of ODI is not supported for Hyperion 11.2 versions and to use FDMEE.
In the current process, metadata and data comes to Hyperion through ODI. From Hyperion data goes to OBIEE through ODI. Our client don't want to completely cutoff ODI. Hence, we are looking for a way to use the current data flow. Like, using an adapter for FDMEE to connect to ODI to bring in metadata and data from ODI and to send data to ODI.
It would be great if you can suggest a way to achieve this.