Enabling SQL Trace for versions 9.3 and later can be done without restarting the application server:

1. Log into Web Client as the user with administrator role, go to Administration>Logging Configuration

2. CTR-F type SQL in the search field.  Set to “DEBUG” the following selections:com.agile.util.sql.AgileUtil:
com.agile.util.sql.ConnectionFactory:
com.agile.util.sql.SqlLogger:

Enable any other entry as recommended by Support

Note : If com.agile.util.sql.SqlLogger does not appear from Administration>Logging Configuration perform the following:

a) Enable the 2 setting to “DEBUG”

com.agile.util.sql.AgileUtil:
com.agile.util.sql.ConnectionFactory:

b) Save and Logout
c) Login to Web Client as the user with administrator role, go to Administration>Logging Configuration
d) Confirm com.agile.util.sql.SqlLogger will appear. Enable the setting to “DEBUG”

com.agile.util.sql.SqlLogger:

e) Save

3. Save

4. Perform the reproducing stepsNote: Logging Configuration is not get designed to be synched across all the managed severs, so it only works on its own JVM. If you are running on clustered environment, make sure to reproduce the problem on the same managed server which was access to enable Logging Configuration. To ensure, reproduce the issue though the same session which Logging Configuration was enabled.After setting Logging configuration in a Web Client, subsequent WebClient and Java Client sessions will also log sql trace, as long as they point to same managed server. To disable it, reset the Logging configuration to ERROR or restart the application server.

5. The output is logged in the application server log. (In some cases it is generated to sql.log)
The name and location of application server log will depend on the OS and Application Server (OAS or WebLogic) used by your system.
 to understand the how to obtain application server log in your system.
The agile server log file can be opened with any text editor. 

6. To disable SQL Trace debug, set the value of parameters changed in step 2 back to “ERROR”