E1: KER: EnterpriseOne Services Are Not Starting Clean on Secondary AS400 Enterprise Server
(Doc ID 964507.1)
Last updated on NOVEMBER 07, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
EnterpriseOne 8.12 with Tools Release 8.98.1.x is installed on two AS400 Enterprise Servers (two LPAR's running on the same box). The primary Enterprise Server kernels start clean, but the secondary Enterprise server kernels do not start properly. The kernels die soon after starting services on the second Enterprise Server.
EDRSQL is running on both primary and secondary servers.
The server JDE.LOG has the following error:
OS400QL001 - ConnectDB:Unable to connect to DS 'System - 812' in DB 'System - 812' on Server DB 'STAGING' with RDB Name 'Not Applicable' via 'T' with Commitment 'N'. QCPFMSG *LIBL - CPI2A5A - Not authorized to access the remote system
1243/147 SYS:Dispatch Thu Nov 5 16:33:04.667448 jdb_drvm.c909
JDB9900164 - Failed to connect to System - 812
1243/147 SYS:Dispatch Thu Nov 5 16:33:04.667504 jtp_cm.c284
JDB9909003 - Could not init connect.
1243/147 SYS:Dispatch Thu Nov 5 16:33:04.667560 jtp_tm.c1134
JDB9909100 - Get connect info failed: Transaction ID =
1243/147 SYS:Dispatch Thu Nov 5 16:33:04.667616 jdb_rq1.c2392
JDB3100013 - Failed to get connectinfo
1243/147 SYS:Dispatch Thu Nov 5 16:33:04.667680 dbdrv_log.c196
OS400CN004 - IsValidConnection:DBC is NULL
1243/147 SYS:Dispatch Thu Nov 5 16:33:04.667728 jdb_drvm.c964
JDB9900166 - Failed to free db connection
1243/147 SYS:Dispatch Thu Nov 5 16:33:04.667784 jdb_omp1.c1887
JDB9900251 - Failed to shut down connection.
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