E1: KER: How to Define the JDEDEBUG.LOG for a Large Log File Without Truncation
(Doc ID 1522056.1)
Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
To check the performance of a UBE, debug is turned on. The jdedebug.log is started at 21:24:50 and ends at 21:45:45. This means the UBE (batch) ran for 21 minutes. In actuality the batch was submitted at 20:28:04 by the user. What is the batch doing that during UBE submitted and debug.log opened? The jdedebug.log appears to be truncated.
What needs to be done to define the jdedebug.log settings so that the jdedebug.log is not being truncated?
The log file creation time is shown below:
-rw-r--r-- 1 jde900 jde900 589340703 Dec 31 21:45 R30822A_VERS_16044_PDF.jdedebug.log
-rw-r--r-- 1 jde900 jde900 1073682030 Dec 31 21:40 R30822A_VERS_16044_PDF_1.jdedebug.log
-rw-r--r-- 1 jde900 jde900 991 Dec 31 20:28 R30822A_VERS_16044_PDF.jde.log
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