IKM SQL to Hyperion Planning Does Not Release Log File Locks when an Error Aborts Execution
Last updated on JULY 28, 2016
Applies to:Hyperion Planning - Version 220.127.116.11.000 and later
Information in this document applies to any platform.
Errors in the Planning IKM can leave the error log file locked.
IKM SQL to Hyperion Planning has: log options true, error options true, and static log and error log files -- not the default (e.g. "c:\odi\results.txt" for log)
If an error occurs during the load to Planning (e.g. server goes down) the error log, where lines that failed to be loaded to Planning are written (NOT the log file), remains 'open'. When you run the package again in the same agent, an error occurs because the IKM it cannot overwrite the error log. Any attempt to run the scenario again in the same agent fails: the scenario is hung and the agent must be restarted. Note that other scenarios may still be run in the agent.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms