Demantra Engine hangs at Database Connect string when launched from the Demantra Workflow (Web Server and Demantra Engine are on the same WINDOWS server)
(Doc ID 1109433.1)
Last updated on MARCH 28, 2016
Applies to:Oracle Demantra Real-Time Sales and Operations Planning - Version 7.3.0 and later
Information in this document applies to any platform.
***Checked for relevance on 22-March-2012***
When launching the Demantra engine from the workflow it gets only as far as:
File creation date time: Tue May 18 17:23:03 2010
17:23:03:225 http://EngLogger.cpp,196 Logger General Level: message, CacheLevel: message, OtherLevel: message, SQLLevel: message, UserLevel: message
17:23:03:225 Working with Oracle RDBMS
17:23:03:225 Database connection string: Provider=MSDAORA;Data Source=ASCP User: dp
All non-workflow ways of launching the engine worked and no obvious errors in the Collaborator.log were observed
In this instance the Demantra Engine and WebServer (OAS) are indeed the same machine and it is a Windows machine so this is not the same issue as when the Web Server is on Linux or Unix and the Demantra Engine is on Windows. The Engine Executable does actually get launched successfully but it hangs at the Database Connect string.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document