This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers.
Legacy ID:KA395595
You can notice on SQL log that long queries sometimes are written using "..." at the end - see example below:
......(T1195.C60900 LIKE '%;20218;%') OR (T1195.C60900 LIKE '%;1000000008;%') OR (T1195.C60900 LIKE '%;3004;%') OR (T1195.C112 LIKE '%;''E015806'';%') OR (T1195.C112 LIKE '%;0;%') OR (T1195.C112 LIKE '%;-1098;%') OR (T1195.C112 LIKE '%;-20313;%') OR (T1195.C112 LIKE '%;-20315;%... ---> you can see "..." at the end.
The real SQL statement in database is longer but due to very long sentence is not written fully on SQL log.
To have the full SQL statement be written in the SQL log perform the following:
1- In the ARSystem installation directory go to the Conf directory.
2- Backup the ar.cfg/ar.conf file.
4- Edit the original ar.cfg/ar.conf file and add the following parameter:
Enable-Unlimited-Log-Line-Length: T
5- Save ar.cfg/ar.conf file.
6- Restart the ARSystem when possible.
Note: in versions 9.x onwards, BMC recommends that you use the AR System Configuration Generic UI form to modify the configuration settings. Do not use the ar.cfg file to modify the configuration settings on the AR System Configuration Generic UI form. --- as mentioned in our documentation: https://docs.bmc.com/docs/display/public/ars91/Configuration+settings+E-M
After making the changes toggle the SQL logging from on to off, hit apply, then back on and hit apply from the Server Information > Log Files tab. (this should refresh the log mechanism and allow now the full text of the sql statement to be written on the log)
The SQL log file will capture all SQL statements without being trimmed/truncated.