E9.2 JDE web client loggin

Relberg · Apr 24, 2024

Hello.

I am learning about JDE LOG, and upon further investigation, I successfully managed to enable logging on the web client.
I found out about the JAS.INI and that the logs are located in the folder C:\E920_1\system\JAS\EA_JAS_80.ear\webclient.war\logs.

However, I encountered a challenge in analyzing the logs. It seems that the where clause values are passed through variables, and I'm struggling to correlate them.
This complicates the analysis process significantly.

Is there a workaround for this situation?

Any guidance or pointers in the right direction would be greatly appreciated.

Here is the example:
SELECT SDAN8,SDUORG,SDADDJ,SDMCU,SDDOC,SDDCT,SDCNDJ,SDAEXP,SDDELN,SDZON,SDDVAN,SDUOM,SDPA8,SDADTM,SDSRP4,SDSRP2,SDSO16,SDUPRC,SDRLLN,SDSHAN,SDOPTT,SDPSIG,SDRKIT,SDPDTT,SDKCO,SDPMPN,SDITM,SDSHPN,SDCORD,SDCARS,SDIVD,SDSRP1,SDOORN,SDDMCT,SDRSDJ,SDTORG,SDSQOR,SDUNCS,SDLITM,SDTRDJ,SDMOT,SDPSN,SDLNTY,SDDOCO,SDDRQT,SDLTTR,SDFUC,SDRFRV,SDEMCU,SDSOBK,SDNXTR,SDSOCN,SDDCTO,SDLOTN,SDKCOO,SDDSC1,SDSWMS,SDLNID,SDFUP,SDRCTO,SDFRTH,SDUOM4,SDPEFJ,SDSRP5,SDOPDJ,SDPMTN,SDCRCD,SDOCTO,SDOKCO,SDSRP3,SDAITM,SDASN,SDSOQS,SDKITID,SDUOM2,SDRKCO,SDDRQJ,SDRLIT,SDPDDJ,SDFEA,SDSFXO,SDVR01,SDDSC2,SDDGL,SDALLOC,SDSONE,SDRSDT,SDCRR,SDRORN,SDLOCN FROM JDEData920.F4211 WHERE (SDDCTO = ? AND SDKCOO = ? AND SDLTTR <= ? AND SDLTTR >= ? AND SDMCU = ? AND SDDOCO = ? AND SDSO15 <> ? ) UNION ALL SELECT SDAN8,SDUORG,SDADDJ,SDMCU,SDDOC,SDDCT,SDCNDJ,SDAEXP,SDDELN,SDZON,SDDVAN,SDUOM,SDPA8,SDADTM,SDSRP4,SDSRP2,SDSO16,SDUPRC,SDRLLN,SDSHAN,SDOPTT,SDPSIG,SDRKIT,SDPDTT,SDKCO,SDPMPN,SDITM,SDSHPN,SDCORD,SDCARS,SDIVD,SDSRP1,SDOORN,SDDMCT,SDRSDJ,SDTORG,SDSQOR,SDUNCS,SDLITM,SDTRDJ,SDMOT,SDPSN,SDLNTY,SDDOCO,SDDRQT,SDLTTR,SDFUC,SDRFRV,SDEMCU,SDSOBK,SDNXTR,SDSOCN,SDDCTO,SDLOTN,SDKCOO,SDDSC1,SDSWMS,SDLNID,SDFUP,SDRCTO,SDFRTH,SDUOM4,SDPEFJ,SDSRP5,SDOPDJ,SDPMTN,SDCRCD,SDOCTO,SDOKCO,SDSRP3,SDAITM,SDASN,SDSOQS,SDKITID,SDUOM2,SDRKCO,SDDRQJ,SDRLIT,SDPDDJ,SDFEA,SDSFXO,SDVR01,SDDSC2,SDDGL,SDALLOC,SDSONE,SDRSDT,SDCRR,SDRORN,SDLOCN FROM JDEData920.F42119 WHERE (SDDCTO = ? AND SDKCOO = ? AND SDLTTR <= ? AND SDLTTR >= ? AND SDMCU = ? AND SDDOCO = ? AND SDSO15 <> ? ) ORDER BY 44 ASC , 53 ASC , 55 ASC , 58 ASC
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] SQL statement parameter marker values are :
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param1 : SO_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param2 : 00200_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param3 : 999_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param4 : 520_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param5 : M30_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param6 : 2459_Types.NUMERIC,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param7 : 1_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param8 : SO_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param9 : 00200_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param10 : 999_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param11 : 520_Types.VARCHAR,
24 Apr 2024 13:02:00,262 [APP ] DEMO - [JDBJ] Param12 : M30_Types.VARCHAR,
24 Apr 2024 13:02:00,262 [APP ] DEMO - [JDBJ] Param13 : 2459_Types.NUMERIC,
24 Apr 2024 13:02:00,262 [APP ] DEMO - [JDBJ] Param14 : 1_Types.VARCHAR,

jean_driscoll · Apr 24, 2024

20 years ago, JDE gave us the performance workbench (pw.exe). Using this tool and reading the jdedebug logs you can get back to the SQL statements, showing variables. You can still download this from Oracle support, but virus scanners don't like it, and you need to download an old MS Runtime and when you run it, you generally have to take the option to update the log file back to an old conversion. But it does still work. I've been trying to talk oracle into giving us an updated version.

jean_driscoll · Apr 24, 2024

jean_driscoll said:
20 years ago, JDE gave us the performance workbench (pw.exe). Using this tool and reading the jdedebug logs you can get back to the SQL statements, showing variables. You can still download this from Oracle support, but virus scanners don't like it, and you need to download an old MS Runtime and when you run it, you generally have to take the option to update the log file back to an old conversion. But it does still work. I've been trying to talk oracle into giving us an updated version.

EnterpriseOne Performance Workbench (Doc ID 747328.1)

craig_welton · Apr 24, 2024

Relberg said:
Hello.

I am learning about JDE LOG, and upon further investigation, I successfully managed to enable logging on the web client.
I found out about the JAS.INI and that the logs are located in the folder C:\E920_1\system\JAS\EA_JAS_80.ear\webclient.war\logs.

However, I encountered a challenge in analyzing the logs. It seems that the where clause values are passed through variables, and I'm struggling to correlate them.
This complicates the analysis process significantly.

Is there a workaround for this situation?

Any guidance or pointers in the right direction would be greatly appreciated.

Here is the example:
SELECT SDAN8,SDUORG,SDADDJ,SDMCU,SDDOC,SDDCT,SDCNDJ,SDAEXP,SDDELN,SDZON,SDDVAN,SDUOM,SDPA8,SDADTM,SDSRP4,SDSRP2,SDSO16,SDUPRC,SDRLLN,SDSHAN,SDOPTT,SDPSIG,SDRKIT,SDPDTT,SDKCO,SDPMPN,SDITM,SDSHPN,SDCORD,SDCARS,SDIVD,SDSRP1,SDOORN,SDDMCT,SDRSDJ,SDTORG,SDSQOR,SDUNCS,SDLITM,SDTRDJ,SDMOT,SDPSN,SDLNTY,SDDOCO,SDDRQT,SDLTTR,SDFUC,SDRFRV,SDEMCU,SDSOBK,SDNXTR,SDSOCN,SDDCTO,SDLOTN,SDKCOO,SDDSC1,SDSWMS,SDLNID,SDFUP,SDRCTO,SDFRTH,SDUOM4,SDPEFJ,SDSRP5,SDOPDJ,SDPMTN,SDCRCD,SDOCTO,SDOKCO,SDSRP3,SDAITM,SDASN,SDSOQS,SDKITID,SDUOM2,SDRKCO,SDDRQJ,SDRLIT,SDPDDJ,SDFEA,SDSFXO,SDVR01,SDDSC2,SDDGL,SDALLOC,SDSONE,SDRSDT,SDCRR,SDRORN,SDLOCN FROM JDEData920.F4211 WHERE (SDDCTO = ? AND SDKCOO = ? AND SDLTTR <= ? AND SDLTTR >= ? AND SDMCU = ? AND SDDOCO = ? AND SDSO15 <> ? ) UNION ALL SELECT SDAN8,SDUORG,SDADDJ,SDMCU,SDDOC,SDDCT,SDCNDJ,SDAEXP,SDDELN,SDZON,SDDVAN,SDUOM,SDPA8,SDADTM,SDSRP4,SDSRP2,SDSO16,SDUPRC,SDRLLN,SDSHAN,SDOPTT,SDPSIG,SDRKIT,SDPDTT,SDKCO,SDPMPN,SDITM,SDSHPN,SDCORD,SDCARS,SDIVD,SDSRP1,SDOORN,SDDMCT,SDRSDJ,SDTORG,SDSQOR,SDUNCS,SDLITM,SDTRDJ,SDMOT,SDPSN,SDLNTY,SDDOCO,SDDRQT,SDLTTR,SDFUC,SDRFRV,SDEMCU,SDSOBK,SDNXTR,SDSOCN,SDDCTO,SDLOTN,SDKCOO,SDDSC1,SDSWMS,SDLNID,SDFUP,SDRCTO,SDFRTH,SDUOM4,SDPEFJ,SDSRP5,SDOPDJ,SDPMTN,SDCRCD,SDOCTO,SDOKCO,SDSRP3,SDAITM,SDASN,SDSOQS,SDKITID,SDUOM2,SDRKCO,SDDRQJ,SDRLIT,SDPDDJ,SDFEA,SDSFXO,SDVR01,SDDSC2,SDDGL,SDALLOC,SDSONE,SDRSDT,SDCRR,SDRORN,SDLOCN FROM JDEData920.F42119 WHERE (SDDCTO = ? AND SDKCOO = ? AND SDLTTR <= ? AND SDLTTR >= ? AND SDMCU = ? AND SDDOCO = ? AND SDSO15 <> ? ) ORDER BY 44 ASC , 53 ASC , 55 ASC , 58 ASC
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] SQL statement parameter marker values are :
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param1 : SO_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param2 : 00200_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param3 : 999_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param4 : 520_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param5 : M30_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param6 : 2459_Types.NUMERIC,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param7 : 1_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param8 : SO_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param9 : 00200_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param10 : 999_Types.VARCHAR,
24 Apr 2024 13:02:00,261 [APP ] DEMO - [JDBJ] Param11 : 520_Types.VARCHAR,
24 Apr 2024 13:02:00,262 [APP ] DEMO - [JDBJ] Param12 : M30_Types.VARCHAR,
24 Apr 2024 13:02:00,262 [APP ] DEMO - [JDBJ] Param13 : 2459_Types.NUMERIC,
24 Apr 2024 13:02:00,262 [APP ] DEMO - [JDBJ] Param14 : 1_Types.VARCHAR,

Have a look at JDETrace. That should put the SQL together with the parameters. Open the JAS log file using File->Open.

It also analyses the jdedebug log to view the SQL and BSFN calls. The panes at the bottom of the app have several tools to see some summaries.

http://www.patwel.com/Downloads

Craig

Relberg · Apr 25, 2024

jean_driscoll said:
EnterpriseOne Performance Workbench (Doc ID 747328.1)

Hello Mr. Jean.
My access to de documentation got denied because my account is not associated to a valid support identifier.
As I am studying JDE on my own, I am getting a lot of that message lately

Thank you for your reply.

Relberg · Apr 25, 2024

craig_welton said:
Have a look at JDETrace. That should put the SQL together with the parameters. Open the JAS log file using File->Open.

It also analyses the jdedebug log to view the SQL and BSFN calls. The panes at the bottom of the app have several tools to see some summaries.

http://www.patwel.com/Downloads

Craig

Hello Mr. Craig.
JDETrace is a great tool.
I tested and it works by joining the SQL together with the parameters.
Thank you for your replay.

MFreitag · Apr 25, 2024

Oracle Support Document 2548299.1 (E1: FDA: JAS: In JAS Log SQL WHERE Clause Display Question Mark ( ? ) Instead of Actual Value) can be found at: https://support.oracle.com/epmos/faces/DocumentDisplay?id=2548299.1

It's called "JDBj SQL Bind Values Inline"

...but using JDETrace is also a MUST if you ask me. Daily driver for me.

E9.2 JDE web client loggin

Relberg

Member

jean_driscoll

VIP Member

jean_driscoll

VIP Member

craig_welton

Legendary Poster

Relberg

Member

Relberg

Member

MFreitag

Reputable Poster

Similar threads

We value your privacy