1. Administering Oracle Analytics Server
  2. Resolve Issues
  3. Diagnose and Resolve Issues
  4. Manage the Query Log

Manage the Query Log

The Oracle BI Server can log query activity at the individual user level. Use logging for quality assurance testing, debugging, and troubleshooting by Oracle Support Services. In production mode, query logging is typically disabled.

The query log file is named nqquery.log, and is located in:

BI_DOMAIN/servers/obisn/logs

Oracle BI Server query logging is tracked at a user level. It is a resource-intensive process if you track the entire user community.

Note:

For production systems, it's recommended that query logging be enabled only for a very targeted user community. In production systems, you can use usage tracking as the production-level logging facility. See Track Usage.

It's recommended that you test users only when the user name clearly indicates it's a test user and have verified that query logging is enabled. If logging is enabled for such users, then it's recommended that they be given names such as sales_admin_with_logging, sales_dev_with_logging, or sales_test_with_logging, so that you can readily identify them. Even production administrator logins shouldn't have query logging enabled, because it strains the available resources.

Also disable query logging for the following:

  • The SQL statement in the initialization string. The Initialization string field is in the Initialization Block dialog, in the General tab.

    The LOGGING column references stored values for the log level.

  • Set the logging level to 0 (zero) for each production user. The Logging level field is in the User dialog, in the User tab. In the Model Administration Tool, select Identity from the Manage option on the main toolbar. In the Identity Manager dialog, double-click a user and select the User tab.

This section contains the following topics: