How To Recover From Application Server Corruption After Changing JVM Settings Through dnConfig.exe In Oracle Enterprise Data Quality (EDQ)
(Doc ID 1385491.1)
Last updated on JULY 19, 2019
Applies to:Oracle Watchlist Screening - Version 4.2.1 and later
Oracle Enterprise Data Quality - Version 8.0.1 and later
Information in this document applies to any platform.
After following information from "Recommendations For Setting The Java Heap Space For Oracle Enterprise Data Quality Configurations On Tomcat (<Note 1352134.1>)" , the administrator could face one of the following issues
1- Failure to change the service to use 64-bit JVM, Below screenshot shows the possible error message
2- The original service was successfully unregistered but the new service has failed to register.
3- The original Service is still present but has been disabled and marked for deletion.
The above 3 behaviors depends on the precise Windows version.
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