Report Query Status

Last Updated : May 26, 2024 |

Two types of report query logs are being added with release R16.2. These logs track the queries made by historical reports and they show the queries that have completed and the queries that are currently being run. This information can be used to determine who is running what reports and if those report queries are affecting system performance.

Information about query logs

  • Types of report query logs:

    - qlog: a log where entries are made upon query completion

    - idbm log: a log showing the query that is currently running

  • These logs are always in operation implying that they do not need to be turned off/on

  • Comparison between the report query logs

    - qlog has more detail, but is only updated after the report query has completed

    - idbm log shows currently running queries and is updated at completion of the query to add completion status

  • Uses of report query logs

    - qlog can show past report execution to determine who ran queries and how long the queries took

    - idbm log can be used to determine what queries are running currently. This can be used to determine if a particular query is taking a long time and thus negatively impacting system performance.

    - Log information in either logs cannot be used to kill a particular report; it is debug information only

  • qlog features

    - Entries are made upon query/report completion

    - Applies to historical report queries only

    - Log entries have information about start time, user, run time, completion status, task ID and query text

    - qlogs are store in directory /cms/db/log as qlog, qlog.01, qlog.02, etc.

    - The size and number of qlog files are administered in the file /cms/db/LogAdmin/qlog on the server

    - Example entry:
    vdn, starttime, intrvl, acdcalls, acdtime, abncalls, busycalls,disccalls,incalls,othercalls from hvdn where row_date = 40432 and acd = 1 order by vdn, starttime
  • idbm log features

    - Entries are made for currently running queries.

    - Applies to historical report queries only.

    - IDBM stands for Informix Database Manager. These are the processes that interface with the historical database.

    - log entries contain information about start time, user and query text.

    - The idbm logs are kept in the server in directory /cms/db/log as idbm.’process ID’. For example: idbm.17, idbm.1001, idbm.13027, etc.

    - Example entry:
    <timestamp> dsb123 select value, item_name from synonyms where item_type='split' and acd_no=1

    - If no query is running in that idbm process, the log will show the last query run along with its status.

    - Example status entry:
    <timestamp> STATUS=0