Setting the Query Logging Level

Diagnosing and Resolving Issues in Oracle Business Intelligence 8-15 ■ Section 8.5.5, Oracle BI Presentation Services Log Filters ■ Section 8.5.6, Diagnosing Issues with Agents For general information about logging in Oracle Business Intelligence, see Section 8.3, Understanding Diagnostic Log and Log Configuration Files.

8.5.1 Using the Oracle BI Presentation Services Logging Facility

By default, Oracle BI Presentation Services is configured to log all error events and informational and warning events of sufficient importance. An example of an important informational event is a server starting up or a server shutting down. Log files are named sawlogxx.log, where the xx is replaced by an incremented number. To debug specific issues that a user might be encountering, the logging level can be increased to log more information than the default configuration. For example, while debugging a particular Oracle BI Presentation Services connectivity issue, you can increase the maximum logging on the saw.odbc log source only. This adds detailed logging for that component, without cluttering the log with detailed logging from other events. All Oracle BI Presentation Services configuration information is loaded from the instanceconfig.xml file.

8.5.2 Structure for the Oracle BI Presentation Services Configuration File

The structure of the configuration file is shown in Example 8–3 . The cardinality of each node is shown in brackets. Example 8–3 Structure of Log Section in instanceconfig.xml File Logging [1..1] Writers [0..1] Writer [0..1] WriterClassGroups [0..1] Filters [0..1] FilterRecord [0..n] An example of an instanceconfig.xml file that has four writers is shown in Example 8–4 . Example 8–4 instanceconfig.xml File with Four Writers ?xml version=1.0 ? Server . . . . . . . Logging Writers Writer implementation=FileLogWriter name=Global File Logger writerClassId=1 dir={ORACLE_BIPS_INSTANCE_LOGDIR} filePrefix=sawlog maxFileSizeKb=10000 filesN=10 fmtName=ODL-Text ODLLogFilePath={ORACLE_ BIPS_INSTANCE_LOGDIR}diagnostic.log Writer implementation=CoutWriter name=Global Output Logger writerClassId=2 Writer implementation=EventLogWriter name=Event Logger writerClassId=3 Writer implementation=CrashWriter name=CrashWriter Caution: Because logging affects performance, do not increase the logging on a production implementation, except to diagnose specific issues. 8-16 System Administrators Guide for Oracle Business Intelligence Enterprise Edition writerClassId=4 Writers WriterClassGroups WriterClassGroup name=All1,2,3,4WriterClassGroup WriterClassGroup name=File1WriterClassGroup WriterClassGroup name=Console2WriterClassGroup WriterClassGroup name=EventLog3WriterClassGroup WriterClassGroup name=Crash4WriterClassGroup WriterClassGroups Filters FilterRecord writerClassGroup=Console path = saw information=1 warning=31 error=31 trace=0 incident_error=32 FilterRecord writerClassGroup=File path = saw information=1 warning=31 error=31 trace=0 incident_error=32 FilterRecord writerClassGroup=File path=saw.mktgsqlsubsystem.joblog information=1 warning=2 error=31 trace=0 incident_error=32 FilterRecord writerClassGroup=File path=saw.httpserver.request information=16 warning=32 error=32 trace=0 incident_error=32 FilterRecord writerClassGroup=File path=saw.httpserver.response information=16 warning=32 error=32 trace=0 incident_error=32 Filters Logging Server Table 8–3 contains a description of each node in the configuration hierarchy. Table 8–3 Oracle BI Presentation Services Log Configuration File Elements Element Attribute Description Writers None Contains writers configuration. This configuration is loaded on startup. Writer None Configures a writer. Writer disableCentralContro l Optional Determines that this entry is not updated by Fusion Middleware Control. Default value is true. Diagnosing and Resolving Issues in Oracle Business Intelligence 8-17 Writer implementation The following implementations are defined: ■ FileLogWriter. Writes to a disk file. ■ CoutWriter. Writes to standard output. ■ EventLogWriter. Writes to a Windows event log or UNIX syslog. ■ CrashWriter. A Windows only facility that writes to a crash dump file when Presentation Services attempts to log from a specific source file and line number. Used in a production environment for information of some loggable but irrecoverable error for example, failed NQTEST. Note: Use this implementation with care as it might leave the server in an unstable state. Use this implementation in very rare diagnostic-only scenarios on a test system. On Windows, CrashWriter requires the appropriate version of dbghelp.dll at least 6.0.17.0. The correct dbghelp.dll can be found in supportwindowssystem32. Put this DLL in the WINNTsystem32 or in the mainbin directory. No registration is required. Writer name Unique name for the writer. Writer writerClassId Specifies an integer number in the range 1 through 10. This number is used by filters to allow or prohibit logging. Each distinct writer must have a unique value, which is used later for filter configuration. Different writers might have the same class ID, but if they do, those writers cannot be distinguished by filters. Writer fmtName Optional Specifies the format of logged messages. Valid values are: ■ default - 10g style . Formats messages with identifying headings. ■ ODL-TEXT . Formats messages in Oracle Diagnostic Text format. ■ ODL-XML . Formats messages in Oracle Diagnostic XML format. If you do not set this attribute, then logged messages are displayed in the default format which for file log writers is 10g style and for console is ODL-TEXT. See Section 8.5.3, Examples of the Formats of Logged Messages for examples. Writer FileLogWriter specific attribute dir Specifies the directory where log files are created. Table 8–3 Cont. Oracle BI Presentation Services Log Configuration File Elements Element Attribute Description