What Messages Are Included in the System Log?

8-14 System Administrators Guide for Oracle Business Intelligence Enterprise Edition The request ID is unique among the active requests, but not necessarily unique during the session. Request IDs are generated in a circular manner, and if a request is closed or if the session is long enough, then a request ID is reused. You can also locate user names, session IDs, and request IDs through the Session Manager. See Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for information. Administrators can view the query log using the Manage Sessions option in the Presentation Services Administration page.

8.4.2.2 Interpreting the Log Records

After you have logged some query information and started the log viewer, you can analyze the log. Log entries for levels 1 and 2 are generally self-explanatory. The log entries can provide insights to help database administrators DBAs in charge of the underlying databases tune them for optimum query performance. The query log can also help you check the accuracy of applications that use the BI Server. The log is divided into the following sections: ■ SQL Request — This section lists the SQL statement that is issued from the client application. You can use this information to rerun the query from the same application, or from a different application. ■ General Query Information — This section lists the repository, the business model, and the subject area from which the query was run. You can use this information to provide statistics on query usage that you can use to set priorities for future application development and system management. ■ Database Query — This section begins with an entry that reads Sending query to the database named data_source_name, where data_source_name is the name of the data source to which the BI Server is connecting. Multiple database queries can be sent to one or more data sources. Each query has an entry in the log. The database query section has several uses, such as recording the SQL statement that was sent to the underlying databases. You can use this logged SQL statement to run queries directly against the database for performance tuning, results verification, or other testing purposes. You can also use this information to examine the tables that are being queried to verify that aggregate navigation is working as you expect. If you understand the structure of the underlying database, then it might also provide some insights into potential performance improvements, such as useful aggregate tables or indexes to build. ■ Query Status — The query success entry in the log indicates whether the query completed successfully, or failed. You can search through the log for failed queries to determine why they failed. For example, all the queries during a particular time period might have failed due to database downtime.

8.5 Logging in Oracle BI Presentation Services

This section describes logging specifically in Presentation Services and contains the following topics: ■ Section 8.5.1, Using the Oracle BI Presentation Services Logging Facility ■ Section 8.5.2, Structure for the Oracle BI Presentation Services Configuration File ■ Section 8.5.3, Examples of the Formats of Logged Messages ■ Section 8.5.4, Oracle BI Presentation Services Message Structure