Using Fusion Middleware Control to View Log Information, Error Messages, and Alerts

8-6 System Administrators Guide for Oracle Business Intelligence Enterprise Edition ■ Oracle BI Scheduler – nqscheduler-n.log — The Oracle BI Scheduler log file, which is searchable in the Fusion Middleware Control Log Viewer. n = date and timestamp, for example nqscheduler-20100909-2135.log ■ Cluster Controller – nqcluster-yyyyMMdd-hhmm.log — The Oracle BI Cluster Controller diagnostic file, which is searchable in the Fusion Middleware Control Log Viewer. n = date and timestamp, for example nqcluster-20100909-2135.log ■ BI JEE log Action Services and Security Services, both of the following log files are searchable in the Fusion Middleware Control Log Viewer: – AdminServer-diagnostic.log – bi_server1-diagnostic.log ■ Upgrade Log files for the upgrade of Oracle Business Intelligence are created in the following location: ORACLE_HOME\upgrade\logs For information about upgrade log files, see Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence. These files are not searchable in the Fusion Middleware Control Log Viewer. 8.3.2 What Are Diagnostic Log Configuration Files and Where Are They Located? Diagnostic log configuration files control output to diagnostic log files for Oracle Business Intelligence. Log configuration files for Oracle Business Intelligence are stored in the following locations: ORACLE_INSTANCE\config\component_type\bi_component_name For example: ■ \OPMN\opmn\opmn.xml ■ \OracleBIClusterControllerComponent\coreapplication_obiccs1\ccslogconfig.xml ■ \OracleBIJavaHostComponent\coreapplication_obijh1\logging_config.xml ■ \OracleBIPresentationServicesComponent\coreapplication_ obips1\instanceconfig.xml ■ \OracleBISchedulerComponent\coreapplication_obisch1\instanceconfig.xml ■ \OracleBIServerComponent\coreapplication_obis1\logconfig.xml Note: Editing a diagnostic log configuration file for a single component is not advised, because changes might subsequently be overwritten. For information, see Section 3.4, Using a Text Editor to Update Configuration Settings. Diagnosing and Resolving Issues in Oracle Business Intelligence 8-7 About Formats in Diagnostic Log Configuration Files Diagnostic log configuration files conform to the Oracle Diagnostic Log ODL standard, although they can differ slightly in appearance. Example 8–1 and Example 8–2 illustrate two of the log configuration files for Oracle Business Intelligence. Example 8–1 BI Server Diagnostic Log Configuration File Format server ServerInstance Log MaximumFileSizeKb10000MaximumFileSizeKb MaximumLogAgeDay60MaximumLogAgeDay FormatODL-TEXTFormat Level IncidentError1IncidentError Error1Error Warning16Warning Notification1Notification Trace16Trace Level Log UserLog MaximumFileSizeKb10000MaximumFileSizeKb MaximumLogAgeDay10MaximumLogAgeDay FormatODL-TEXTFormat UserLog ServerInstance server Example 8–2 JavaHost Server Diagnostic Log Configuration File Format ?xml version = 1.0 encoding = utf-8? logging_configuration log_handlers log_handler name=odl-handler class=oracle.core.ojdl.logging.ODLHandlerFactory property name=path value=C:\oracle_bi_ee_ BIFNDNPTPSNT0911060426S-Release\jhlogs\javahost.log property name=maxFileSize value=1000000 property name=maxLogSize value=5000000 log_handler log_handlers loggers logger name=saw level=NOTIFICATION:1 useParentHandlers=false handler name=odl-handler logger loggers logging_configuration Oracle Business Intelligence components control their diagnostic log files by using server-specific settings in their log configuration files, for example: ■ Oracle BI Presentation Services log configuration file: - writerClassId settings configure messages that the system writes to the sawlog.log file. ■ Oracle BI Server log configuration file: