Last updated on MARCH 08, 2017
Applies to:Oracle Demantra Demand Management - Version 12.2.3 and later
Information in this document applies to any platform.
Customer mentions that the engine was running fine until they implemented a change since the last successful engine run: they set up the month calendar.
Now the engine crashes (the Engine.exe process ends and then restarts) when receiving a simulation request.
Nothing is reported as error on the simulation worksheet. The process status is "started". A second simulation request will crash the newly started process.
This happens on both modes(batch and simulation run) which cause the Engine process to crash
Checked the Engine Manager web application is started
Checked EngineStarter is running
Started the simulation engine:which Returns -1
Checked Engine process is running: ps -e | grep Engine
Shows EngineStarter and Engine running
Open a worksheet and started simulation for the selected combination
Process monitor shows status "running"
The Engine process crashes, and ps command returns only EngineStarter
Engine restarts on its own (Engine process is seen again when checking with ps)
Engine logs show the engine is frozen (no new logged info once initialized)
When customer changed EnginePlatform to 0 and executed the batch and simulation engine on Windows, the simulation run didn't crash the engine, but no forecast was generated due to errors:
ERROR Failed to execute : ProcFillArrays. ExecuteHook threw Matlab exception: All matrices on a row in the bracketed expression must have the same number of rows.
ERROR Failed to execute : ProcForecast9. ExecuteHook threw Matlab exception: Matrix dimensions must agree.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms