EXCEPTION_ACCESS_VIOLATION Error when Trying to Start EDQ Managed Server
(Doc ID 2194962.1)
Last updated on JANUARY 14, 2020
Oracle Enterprise Data Quality - Version 12.2.1 and later Generic Windows
On an instance of Oracle Enterprise Data Quality (EDQ) 12.2.1 running on WebLogic on Windows Server 2008, the EDQ server starts very slowly then shows "Failed_not_restartable" in the State field, throwing this error:
# A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000010176f468, pid=12236, tid=0x0000000000002724 # # JRE version: Java(TM) SE Runtime Environment (8.0_101-b13) (build 1.8.0_101-b13) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.101-b13 mixed mode windows-amd64 compressed oops) # Problematic frame: # C [lqtcr.dll+0x13f468] # # Core dump written. Default location: F:\oracle\SP\oedq\admin\hs_err_pid12236.mdmp # # An error report file with more information is saved as: # F:\oracle\SP\oedq\admin\hs_err_pid12236.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Stopping Derby server... Derby server stopped.
This happens when running startWebLogic.cmd & startNodeManager.cmd as the administrator. The error is appears in WebLogic Deployments when trying to start the EDQ Managed Server.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!