Include the element and its ancestor elements as appropriate, as shown in the

8-8 System Administrators Guide for Oracle Business Intelligence Enterprise Edition - Log settings configure messages that the system writes to the nqserver.log file. For more information, see Section 8.3.5, What Messages Are Included in the System Log? - UserLog settings configure messages that the system writes to the nqquery.log file. For more information, see Section 8.4, Managing the Query Log. ■ Oracle BI Scheduler log configuration file: - Log settings configure messages that the system writes to the nqscheduler.log file. ■ JavaHost Server log configuration file: - log_handlers elements and subelements enable configuration of the log file rotation policy and the specification of the log file name and its location. - loggers elements and subelements enable appropriate handling of Java component JavaHost Server log levels, by mapping the JavaHost Server log levels to the standard Oracle Diagnostic Log ODL log levels. 8.3.3 What Are Log File Message Categories and Levels? Categories and levels for log file messages define the detail and level of importance with which the system writes messages to a log file. Fusion Middleware Control enables you to control these settings in the logconfig.xml file. Each message category in a log file for Oracle Business Intelligence is set to a specific default value between 1 and 32, and only messages with a level less than or equal to the log level is logged. Log file message categories are described in Table 8–1 . Table 8–1 Log File Message Category Levels Category:Level Description IncidentError:1 A serious problem caused by unknown reasons has occurred. You can fix the problem only by contacting Oracle Support Services. No performance impact. Error:1 A problem that requires attention from the system administrator has occurred. No performance impact. Warning:1 An action occurred or a condition was discovered that should be reviewed and might require action before an error occurs. No performance impact. Notification:1 A report of a normal action or event has occurred. This could be a user operation, such as login completed or an automatic operation such as a log file rotation. No performance impact. Notification:16 A configuration-related message or problem has occurred. Low performance impact. It should be possible to enable this level broadly in a production environment without having a significant performance impact in the software. Diagnosing and Resolving Issues in Oracle Business Intelligence 8-9 In the following log configuration file example, in the Notification message category, only level 1 messages are logged. If the log level is set to 0, then nothing is logged for that message category. Level IncidentError1IncidentError Error1Error Warning1Warning Notification1Notification Trace1Trace Level Avoid manually changing the default settings in the log file. Use Fusion Middleware Control to make changes. For more information, see Section 8.2.2.1, Using Fusion Middleware Control to Configure Log File Rotation Policy and Specify Log Levels. 8.3.4 What is Log File Rotation? Log file rotation is the creation of new log files, when the file exceeds a specified threshold or date. Take the MaximumFileSizeKb setting for the component log configuration file for the Oracle BI Scheduler as an example. Whenever a log file exceeds the size that is specified by this setting, then the existing Scheduler log file is renamed, and a new log file is created. Additionally, a log file date that is older than the MaximumLogAgeDay setting is deleted. The file naming convention for the Scheduler is as follows: ■ nqscheduler.log — The latest log file. ■ nqscheduler-n.log — The renamed previous log file. where n = date and timestamp, for example nqscheduler-20100909-2135.log Trace:1 A trace or debug message that is used for debugging or performance monitoring has been written. Typically this message contains detailed event data that is clear enough to be understood by someone who does not know internal implementation details. Small performance impact. This level might be enabled broadly occasionally on a production environment to debug issues with the software. Enabling logging at this level might have a small performance impact, but not to the point of making the software unusable. Trace:16 A fairly detailed trace or debug message has been written. The message is clear enough to be understood by Oracle Support Services engineers who have a deep knowledge of the product but might not know full details of the internal implementation. High performance impact. This level should not be enabled on a production environment, except on special situations to debug issues with the software. Trace:32 A highly detailed trace or debug message has been written. The message is intended for an Oracle developer working on the software who knows enough details about the implementation of the subsystem that generates the message. Very high performance impact. This level is not expected to be enabled in a production environment and developers use it only to debug the software on a test or development environment. Table 8–1 Cont. Log File Message Category Levels Category:Level Description