My Oracle Support Banner

E1: DB: Enhancement Request to Show Bind Value of SQL in JDE Log (Doc ID 3056189.1)

Last updated on OCTOBER 29, 2024

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When trying to see the actual values for failed SQL statements in the JDE.log instead of the bind variables, they are not visible.

Presently, we see the BIND values like 'BND1,:BND2,:BND3,:BND4' in JDE log file for the failed SQL statements in JDE log file.

The actual values of the bind variables can only be seen when logging is turned on. In the jdedebug log, the INSERT SQL statement with the actual values is displayed before the OCI error statement.
In this case, it isn't desired to enable the JDEDEBUG logging in production. Can these actual values be enabled in the JDE log file?

Cause

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
Symptoms
Cause
Solution
References


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