Implementing Query Logs

Query logging enables Essbase administrators to track query patterns of an Essbase database. The query log file tracks all queries performed against the database, regardless of whether the query originated from Spreadsheet Add-in or Report Writer. Query logging can track members, generation or level numbers of members belonging to specific generations or levels, and Hybrid Analysis members. Query logging also offers the flexibility to exclude logging of certain dimensions and members belonging to generations or levels. Because the query log file output is an XML document, you can import the log file to any XML-enabled tool to view the log. For information about the query log file structure, refer to querylog.dtd in the ESSBASEPATH/bin directory.

Query logging is available for both block storage and aggregate storage databases.

To enable query logging, create a query configuration file (distinct from the essbase.cfg file) and add to the file the configuration settings that control how query logging is performed.

In the ARBORPATH/app/appname/dbname directory, create a query log configuration file. The configuration file must be named dbname.cfg, where dbname matches the name of the database. For example, the query log configuration file for Sample.Basic is basic.cfg. The output query log file is located, by default, at ARBORPATH/app/appname/dbname00001.qlg.

See the Oracle Essbase Technical Reference.