Skip to Content
Information

This site will undergo a brief period of maintenance on Friday, 18 December at 12:30 AM Central/12:00 PM IST. During a 30 minute window, site availability may be intermittent.

SQL log

The SQL log is similar to the filter log, but the SQL log file consists of a series of SQL commands (one per line), each of which contains the information listed in the Log-entry-format.

 By default, the log file is named arsql.log. Each line of a plug-in log file begins with <SQL>, which identifies the entry as an SQL logging line.

Warning

Important

This mode of debugging can quickly generate a large amount of information. It is not unusual to have several hundred megabytes of information logged in one day.

If the server is licensed for full-text search, the SQL debug mode also logs FTS searches in this file.

Related topics

Enabling-and-analyzing-logs

Analyzing-logs

 

The following example shows a portion of a SQL log file:

<SQL > <TrID: MArrSxXkRTO7h7yODJZWXQ:0000001> <TID: 0000000035> <RPC ID: 0000000000> <Queue: Init      > <Client-RPC: 10       > <USER: ARSERVER                                     > <Overlay-Group: 0         > /* 2025-04-18T17:02:38.541+0000 */ SELECT J1.C3294 a0, J1.C3295 a1, J0.C1 a2 FROM T4262 J0 INNER JOIN T4261 J1 ON (J0.C3287 = J1.C379) INNER JOIN T4263 J2 ON (J1.C3279 = J2.C379) WHERE ((J2.C3290 = 1) AND (J0.C3288 = 'arserver.sandbox'::citext) AND (J1.C3297 = 1) AND (1 = J1.C3285)) ORDER BY a2 ASC
<SQL > <TrID: MArrSxXkRTO7h7yODJZWXQ:0000001> <TID: 0000000035> <RPC ID: 0000000000> <Queue: Init      > <Client-RPC: 10       > <USER: ARSERVER                                     > <Overlay-Group: 0         > /* 2025-04-18T17:02:38.543+0000 */ OK
<SQL > <TrID: MArrSxXkRTO7h7yODJZWXQ:0000001> <TID: 0000000035> <RPC ID: 0000000000> <Queue: Init      > <Client-RPC: 10       > <USER: ARSERVER                                     > <Overlay-Group: 0         > /* 2025-04-18T17:02:38.543+0000 */ No. of records retrieved=3
<SQL > <TrID: c6u0pPltSSm22MD2XzSK8w:0000001> <TID: 0000000497> <RPC ID: 0000105265> <Queue: Fast      > <Client-RPC: 390620   > <USER: Remedy Application Service                   > <Overlay-Group: 1         > /* 2025-04-18T17:02:38.546+0000 */ BEGIN TRANSACTION
<SQL > <TrID: c6u0pPltSSm22MD2XzSK8w:0000001> <TID: 0000000497> <RPC ID: 0000105265> <Queue: Fast      > <Client-RPC: 390620   > <USER: Remedy Application Service                   > <Overlay-Group: 1         > /* 2025-04-18T17:02:38.546+0000 */ SELECT T58.C1 FROM T58 WHERE (T58.C1 = '000000000000001'::citext)
<SQL > <TrID: c6u0pPltSSm22MD2XzSK8w:0000001> <TID: 0000000497> <RPC ID: 0000105265> <Queue: Fast      > <Client-RPC: 390620   > <USER: Remedy Application Service                   > <Overlay-Group: 1         > /* 2025-04-18T17:02:38.546+0000 */ OK
<SQL > <TrID: c6u0pPltSSm22MD2XzSK8w:0000001> <TID: 0000000497> <RPC ID: 0000105265> <Queue: Fast      > <Client-RPC: 390620   > <USER: Remedy Application Service                   > <Overlay-Group: 1         > /* 2025-04-18T17:02:38.547+0000 */ No. of records retrieved=1

 
The SQL log file includes an OK line that displays the end time for each transaction that is logged.

If an SQL error or warning is encountered as a result of the command, the command is followed by another line with the same header, but the SQL command is replaced with *** ERROR ** or ** WARNING *** along with an error or warning message. The message also associates an operation with the user who performed the operation, and is useful for identifying database issues.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Helix Innovation Suite 25.4