How Are Issues Resolved?

Diagnosing and Resolving Issues in Oracle Business Intelligence 8-5 For an example of a JavaHost Server diagnostic log configuration file, see Example 8–2 . 4. Save your changes and close the file. 5. Restart Oracle Business Intelligence.

8.3 Understanding Diagnostic Log and Log Configuration Files

This section discusses diagnostic log files and diagnostic log configuration files, and contains the following topics: ■ Section 8.3.1, What Are Diagnostic Log Files and Where Are They Located? ■ Section 8.3.2, What Are Diagnostic Log Configuration Files and Where Are They Located? ■ Section 8.3.3, What Are Log File Message Categories and Levels? ■ Section 8.3.4, What is Log File Rotation? 8.3.1 What Are Diagnostic Log Files and Where Are They Located? Diagnostic log files are files used to store message information that is generated by Oracle Business Intelligence servers. These log files are stored in the following location: ORACLE_INSTANCE\diagnostics\logs\component_type\coreapplication The following diagnostic log files are used in Oracle Business Intelligence: ■ Presentation Services – \CatalogCrawler\sawcatalogcrawlerlogsysn.log — The catalog crawler log file, which is not searchable in the Fusion Middleware Control Log Viewer. – sawlogn.log — The Presentation Services log file that represents the latest part of diagnostic log output and is searchable in the Fusion Middleware Control Log Viewer. For more information specifically about Presentation Services logging, see Section 8.5, Logging in Oracle BI Presentation Services. ■ Oracle BI Server – nqqueryn.log — The Oracle BI Server query log, which is not searchable in the Fusion Middleware Control Log Viewer. n = date and timestamp, for example nqquery-20101209-2135.log – nqservern.log — The Oracle BI Server main diagnostic log, which is searchable in the Fusion Middleware Control Log Viewer. n = date and timestamp, for example nqserver-20101209-2135.log – nqsadmintool.log — The log for the Oracle BI Administration Tool. – Oracle BI Server utilities — For example, biserverxmlexec and equalizerpds, also generate their own logs when they are run. ■ JavaHost – jh-n.log — The JavaHost Server main diagnostic log, which is searchable in the Fusion Middleware Control Log Viewer. n = date and timestamp, for example jh-20100909-2135.log 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.