E1: KER: Metadata Kernel Does Not Reconnect To Database After Cluster Failover
(Doc ID 1382489.1)
Last updated on APRIL 04, 2019
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
EnterpriseOne 9.0 is running with Tools Release 188.8.131.52 and a SQL Server 2008 database cluster. When the database fails over from the primary database node to the secondary database node, the Metadata kernel on the Enterprise server loses its database connection and is unable to reconnect. The following errors are in the server JDE.LOG:
JDB9900164 - Failed to connect to DBSRV1
3884/480 SYS:Metadata Tue Nov 22 10:13:14.576005 JTP_CM.C1306
JDB9900257 - Cannot re-establish the database connection for (System - 900).
3884/480 SYS:Metadata Tue Nov 22 10:13:14.576006 JTP_CM.C1347
JDB9900255 - Database connection to F988259 (System - 900) has been lost.
In a normal instance where the connection is reestablished, the following sequence of messages will be logged in the server JDE.LOG:
JDB9900401 - Failed to execute db request
JDB9900255 - Database connection to F986180 (System - 900) has been lost.
JDB9900256 - Database connection to (System - 900) has been re-established.
As long as the sequence of messages ends with message code JDB9900256 - the connection to the database is re-established.
In this case, all other kernels also lose their connection, but they are able to reconnect:
JDB9900255 - Database connection to F986110 (ENT1 - 900 Server Map) has been lost.
2780/1268 MAIN_THREAD Tue Nov 22 10:15:06.843003 JTP_CM.C1301
JDB9900256 - Database connection to (ENT1 - 900 Server Map) has been re-established.
Is there anything that can be done for this problem or automate the recovery? Currently you have to stop and start the E1 service and this brings the Metadata kernel back up.
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