Depending upon you migrate FDMEE from Hyperion / Oracle EPM 11.1.2.4 to EPM 11.2.x, you may have an issue when trying to run your load jobs.
In 11.2, Oracle included a handy migration package specifically to migrate the AIF* tables from 11.1.2.4 to 11.2. You'll find it on your 11.2 FDMEE server in \Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\database\migrate. There's a package each for MSSQL and Oracle - check the subfolders for the packages and instructions.
As per Oracle's documentation, you want to run this in 11.2 after you've executed "Configure Database" for FDMEE. This because the migration package only migrates the AIF* (FDMEE) tables, and does not migrate the ODI-specific tables (SMP* etc.).
Now let's say you're in 11.2's Data Management and you're trying to run an import job. It fails. You check the log and see a reference to JAVA_HOME=%EPM_ORACLE_HOME%\..\jdk160_35.
This simply won't do! Don't be tempted to just copy jdk160_35 from your 11.1.2.4 server to your 11.2. Java SE 6 is out of support and won't be patched anymore.
You can run a simple SQL statement to fix the problem. Here's how it looks in MSSQL, and Oracle's version of this would be the same:
Bounce your 11.2 FDMEE service(s) just to be on the safe side, and now when you go back in to Data Management, you won't see that reference to jdk160_35 in your process log anymore.
I don't think that reference is used for anything, doesn't hurt to update it tho.
ReplyDeleteIn both 11.1.2.4 and 11.2 it comes from the file X:\Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\database\Common\aif_misc.sql so your base 11.2 also have that reference baked in.
When Oracle first release their Java 7 upgrade doc (2351499.1), I sent them a bunch of questions regarding a lot of references I found. Mostly as I found the document severely lacking. Most of them are still not even in the doc. This was one of them, never got an answer to it ;) Their doc is getting close to where I was back in early 2018 >_<
Oh yeah, these were among the files that point to 1.6 still
Delete## These still point to java 1.6...
##/EPMSystem11R1/products/FinancialDataQuality/database/Common/aif_misc.sql
##/EPMSystem11R1/products/FinancialManagement/Utilities/MetadataMerge/MetadataMerge.bat
##/EPMSystem11R1/products/FinancialManagement/Utilities/MetadataMerge/MetadataMerge.sh
There are other but they point to even older versions, so I never bothered with them.
"Funnily" enough, seem this is used by VB rules. None of my customers use VB, all went for jython when going for 11.1.2.4. But if you are running VB rules and they don't work. Well, here's your reason.
DeleteHello Dave, Did you get any chance to test Open batch or Data batch which takes more than 2minutes ? We have observed and raised SR with Oracle FDMEE batches are failing beyond 2minutes time frame. DLR which take more than 2 min also failing
ReplyDeleteError in AIFUtil.callBatchExecutionServlet
Traceback (most recent call last):
File "", line 1079, in callBatchExecutionServlet
File "D:\Oracle\Middleware\odi\sdk\lib\Lib\urllib2.py", line 124, in urlopen
return _opener.open(url, data)
File "D:\Oracle\Middleware\odi\sdk\lib\Lib\urllib2.py", line 387, in open
response = meth(req, response)
File "D:\Oracle\Middleware\odi\sdk\lib\Lib\urllib2.py", line 497, in http_response
response = self.parent.error(
File "D:\Oracle\Middleware\odi\sdk\lib\Lib\urllib2.py", line 425, in error
return self._call_chain(*args)
File "D:\Oracle\Middleware\odi\sdk\lib\Lib\urllib2.py", line 360, in _call_chain
result = func(*args)
File "D:\Oracle\Middleware\odi\sdk\lib\Lib\urllib2.py", line 506, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
HTTPError: HTTP Error 503: Service Unavailable
Hi Dinesh,
DeleteLong-running FDMEE jobs can hit a timeout in OHS Find your mod_wl_ohs.conf file and scroll through it until you find the odiagent entry. Crank up the session timeout setting. If the setting is missing, then it is running under a default setting that is too low. You should be able to scroll through the file and find another web service that has the timeout setting applied... copy and paste it into the odiagent section if it is missing.
Good luck!