E1: KER: E1 Services Fail To Start When The ICUDT32E.dat File Is Being Journaled
(Doc ID 654345.1)
Last updated on NOVEMBER 14, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
IBM i on POWER Systems
The Tools Release has recently been upgraded and EnterpriseOne services are successfully started. All application tests work. After testing, E1 services are stopped, a backup is done but when trying to restart services; services will not start. It is determine that when MIMIX backs up the system, it automatically starts journaling on the system library (ex: E812SYS, E900SYS) directory in the IFS. The problem lies when journaling is started on the following file in the IFS:
If journaling is started on this file PORTTEST fails and there are problems with starting services, etc. If journaling is stopped on this file then everything returns to normal. Here are the steps to duplicate:
Steps to replicate the issue:
- Restore the E812SYS and /E812SYS objects to a test system.
- Start E1 services
- Run PORTTEST
- Stop E1 services
- Issue the STRJRN (Start Journal) command on object /E812SYS/LOCALE/XML/ICUDT32E.DAT
- Attempt to start E1 services
- Services fail -- message CPD0005 is found in the AS400 joblog for the NETWORK job.
- Issue the ENDJRN command on the above named object. (ENDJRN OBJ(/E812SYS/LOCALE/XML/ICUDT32E.DAT)
- Start E1 services
- PORTTEST is successful
Errors in iSeries JOBLOG:
CPD0005 Diagnostic 30 04/03/07 13:37:33.424456 QCMDEXC QSYS 0221 QC2SYS QSYS *STMT
To module . . . . . . . . . : QC2SYS
To procedure . . . . . . . : system
Statement . . . . . . . . . : 6
Message . . . . : Command length not valid.
Cause . . . . . . : A length that is not valid was specified in the second parameter that was sent to QCMDEXC or QCMDCHK.
Recovery . . . . : Change the command length to be from 1-32702 characters.
C2M1601 Escape 30 04/03/07 13:37:33.445928 QC2UTIL1 QSYS *STMT JDELIB E811SYS *STMT
From module . . . . . . . . : QC2SIGNL
From procedure . . . . . . : raise
Statement . . . . . . . . . : 8
To module . . . . . . . . . : WINANSI
To procedure . . . . . . . : GetPrivateProfileString
Statement . . . . . . . . . : 56 *PRCLT
Message . . . . : Signal SIGABRT raised (abnormal termination).
Cause . . . . . : The signal SIGABRT was raised to indicate an abnormal termination.
CEE9901 Escape 30 04/03/07 13:37:33.606192 QLEAWI QSYS *STMT QCMD QSYS 01B7
From module . . . . . . . . : QLEDEH
From procedure . . . . . . : Q LE leDefaultEh
Statement . . . . . . . . . : 195
Message . . . . : Application error. C2M1601 unmonitored by QC2UTIL1 at statement 0000000008, instruction X'0000'.
Cause . . . . . : The application ended abnormally because an exception occurred and was not handled. The name of the program to which the unhandled exception is sent is QC2UTIL1 QC2SIGNL raise. The program was stopped at the high-level language statement number(s) 0000000008 at the time the message was sent. If more than one statement number is shown, the program is an optimized ILE program. Optimization does not allow a single statement number to be determined. If *N is shown as a value, it means the real value was not available.
Recovery . . . : See the low level messages previously listed to locate the cause of the exception. Correct any errors, and then try the request again.
You have the following questions:
- What is this file used for?
- Why does enabling journaling for this object causes E1 services to fail?
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