E1: FDA: RDA: BSFN: Fat Client Local JDEDEBUG.LOG File Does Not Show Column Names For SQL Insert Statements (Doc ID 2964512.1)

Last updated on MARCH 04, 2024

Applies to:

Symptoms

On fat client with logging On SQL INSERT statement does not include the column names compared to Server logging.

For example,
INSERT INTO CRPDTA/F4074
VALUES (10156498.000000,'SO','25100',' ',1000.000000,0.000000, ....)

Desired output:
INSERT INTO CRPDTA/F4074
(ALDOCO, ALDCTO, ALKCOO, ALSFXO, ALLNID, ALAKID, ALSRCFD, ALOSEQ, ALSUBSEQ, ALTIER, ALASN, ALAST, ALITM, ALAN8, ALCRCD, ALUOM, ALMNQ, ALLEDG, ALFRMN, ALBSCD, ALFVTR, ALABAS, ALUPRC, ALFUP, ALGLC, ALARSN, ALACNT, ALSBIF, ALMDED, ALPROV, ALATID, ALIGID, ALCGID, ALOGID, ALANPS, ALBSDVAL, ALSRFLAG, ALADJCAL, ALNBRORD, ALUOMVID, ALOLVL, ALADJSTS, ALADJREF, ALACCAN8, ALBNAD, ALADJGRP, ALMEADJ, ALFVUM, ALPDCL, ALCFGID, ALCFGCID, ALAPRP1, ALAPRP2, ALAPRP3, ALAPRP4, ALAPRP5, ALAPRP6, ALNDPI, ALUSER, ALPID, ALJOBN, ALUPMJ, ALTDAY, ALPMTN, ALRULENAME, ALPA04, ALADJQTY, ALQTYPY, ALSTPRCF, ALTSTRSNM)
VALUES (10156498.000000,'SO','25100',' ',1000.000000,0.000000,....)

Changes

Specific to data source using ODBC driver.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.