Applies to:
Business Intelligence Server Enterprise Edition - Version 11.1.1.3.0 [1905] to 11.1.1.6.0 [Release 11g]Business IntelligenceSuite Enterprise Edition - Version 11.1.1.3.0 [1905] to 11.1.1.6.0 [Release 11g]
Information in this document applies to any platform.
Goal
How to review the information in the log files for Oracle Business Intelligence (OBIEE) 11g version.
Fix
You can check the different log files in OBIEE using the Enterprise Manager (EM) Console page but you can also review directly the files in the hard disk.
a) EM Console. Log in to the URL
http://server.domain:7001/em
and navigate to:
Fam_bifoundation_domain-Business Intelligence-coreapplications-Diagnostics-Log Messages
These are all the available files:
a) EM Console. Log in to the URL
http://server.domain:7001/em
and navigate to:
Fam_bifoundation_domain-Business Intelligence-coreapplications-Diagnostics-Log Messages
These are all the available files:
Presentation Services Log
Server Log
Scheduler Log
JavaHost Log
Cluster Controller Log
Action Services Log
Security Services Log
Administrator Services Log
Server Log
Scheduler Log
JavaHost Log
Cluster Controller Log
Action Services Log
Security Services Log
Administrator Services Log
************************************************************
To check the files directly, you can use the following:
0) The log files for OBIEE components are under
To check the files directly, you can use the following:
0) The log files for OBIEE components are under
<Middleware Home>/instances/instance1/diagnostics/logs
Example:
C:\OBIEE_11g\instances\instance3\diagnostics\logs
Example:
C:\OBIEE_11g\instances\instance3\diagnostics\logs
These are the different type of log files:
1) Installation logs.
1.1) OBIEE Installation and Configuration ($ORACLE_HOME/bin/config.sh):
<Middleware Home>/cfgtoollogs\oui
Examples:
C:\OBIEE_11g\Oracle_BI1\cfgtoollogs\oui
2011-12-23_02-58-20PM.log
install2011-12-23_02-58-20PM.log
install2011-12-23_02-58-20PM.out
installActions2011-12-23_02-58-20PM.log
installProfile2011-12-23_02-58-20PM.log
oraInstall2011-12-23_02-58-20PM.err
oraInstall2011-12-23_02-58-20PM.out
Examples:
C:\OBIEE_11g\Oracle_BI1\cfgtoollogs\oui
2011-12-23_02-58-20PM.log
install2011-12-23_02-58-20PM.log
install2011-12-23_02-58-20PM.out
installActions2011-12-23_02-58-20PM.log
installProfile2011-12-23_02-58-20PM.log
oraInstall2011-12-23_02-58-20PM.err
oraInstall2011-12-23_02-58-20PM.out
or
<Middleware Home>/oracle_common/cfgtoollogs/oui
Examples:
C:\OBIEE_11g\oracle_common\cfgtoollogs\oui
install2011-12-23_02-58-20PM.log
installActions2011-12-23_02-58-20PM.log
installProfile2011-12-23_02-58-20PM.log
Examples:
C:\OBIEE_11g\oracle_common\cfgtoollogs\oui
install2011-12-23_02-58-20PM.log
installActions2011-12-23_02-58-20PM.log
installProfile2011-12-23_02-58-20PM.log
1.2) OraInventory files.
Examples:
installActions2011-12-15_03-21-41PM.log
oraInstall2011-12-05_02-55-22PM.err
oraInstall2011-12-05_02-55-22PM.out
installActions2011-12-15_03-21-41PM.log
oraInstall2011-12-05_02-55-22PM.err
oraInstall2011-12-05_02-55-22PM.out
Location:
- Windows:
C:\Program Files\Oracle\Inventory\logs
- Linux, AIX : Directory mentioned in /etc/oraInst.loc
- Solaris: Directory mentioned in /var/opt/oracle / oraInst.loc
- HP OpenVMS: Directory under sys$login
- Windows:
C:\Program Files\Oracle\Inventory\logs
- Linux, AIX : Directory mentioned in /etc/oraInst.loc
- Solaris: Directory mentioned in /var/opt/oracle / oraInst.loc
- HP OpenVMS: Directory under sys$login
1.3) Make.log
$ORACLE_HOME/install/make.log
file to check for install/relinking.
2) Repository Creation Utility (RCU)
If the RCU software is uncompressed in this directory:
D:\Trabajo\Docu\OBIEE\Software\11.1.1.6.0\Windows64
Check the following files, mainly the 'rcu.log':
D:\Trabajo\Docu\OBIEE\Software\11.1.1.6.0\Windows64\rcuHome\rcu\log\logdir.2012-02-23_10-17
biplatform.log
mds.log
rcu.log
biplatform.log
mds.log
rcu.log
3) BI Server log files
<Middleware Home>/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1
Example:
C:\OBIEE_11g\instances\instance3\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1
The files to review are:
3.1) Queries run by BI:
nqquery.log
3.2) BI log file
nqserver.log
3.3) Administration Tool
servername_NQSAdminTool.log (example, jjuan4_NQSAdminTool.log)
3.4) nQUDMLExec
servername_nQUDMLExec.log (examle, jjuan4_nQUDMLExec.log)
3.5) Migration Utility:
servername_obieerpdmigrateutil.log (example, jjuan4_obieerpdmigrateutil.log)
3.6) Repository log
<ORACLE_INSTANCE>\OracleBIServerComponent\coreapplication_obis1\repository
3.7) System logging level (for BISystem user).
http://docs.oracle.com/cd/E23943_01/bi.1111/e10540/planning.htm#BIEMG398
Using Administration Tool, in Tools->Options->Repository->System Logging Level to set the log level.
This option determines the default query logging level for the internal BISystem user. The BISystem user owns the Oracle BI Server
system processes and is not exposed in any user interface.
A query logging level of 0 (the default) means no logging. Set this logging
level to 2 to enable query logging for internal system processes like event
polling and initialization blocks.
See this link to see all the Query Logging Levels
http://docs.oracle.com/cd/E23943_01/bi.1111/e10541/logging.htm#BIESG181
http://docs.oracle.com/cd/E23943_01/bi.1111/e10540/planning.htm#BIEMG398
Using Administration Tool, in Tools->Options->Repository->System Logging Level to set the log level.
This option determines the default query logging level for the internal BISystem user. The BISystem user owns the Oracle BI Server
system processes and is not exposed in any user interface.
A query logging level of 0 (the default) means no logging. Set this logging
level to 2 to enable query logging for internal system processes like event
polling and initialization blocks.
See this link to see all the Query Logging Levels
http://docs.oracle.com/cd/E23943_01/bi.1111/e10541/logging.htm#BIESG181
4) Presentation Server log files
<Middleware Home>/instances/instance1/diagnostics/logs/OracleBIPresentationServicesComponent/coreapplication_obips1
Example:
C:\OBIEE_11g\instances\instance3\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1
File to check:
sawlog0.log
File to check:
sawlog0.log
4.1) Java Host
<Middleware Home>/instances/instance1/diagnostics/logs/OracleBIJavaHostComponent\coreapplication_obijh1
Example:
C:\OBIEE_11g\instances\instance3\diagnostics\logs\OracleBIJavaHostComponent\coreapplication_obijh1
Files to check:
jh.log
jh-1.log
jh-2.log
Example:
C:\OBIEE_11g\instances\instance3\diagnostics\logs\OracleBIJavaHostComponent\coreapplication_obijh1
Files to check:
jh.log
jh-1.log
jh-2.log
4.2) Web Catalog Upgrade
<Middleware Home>/instances/instance1/diagnostics/logs/OracleBIPresentationServicesComponent/coreapplication_obips1
Example:
C:\OBIEE_11g\instances\instance3\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1
File to check:
webcatupgrade0.log
File to check:
webcatupgrade0.log
5) Scheduler log
<Middleware Home>/instances/instance1/diagnostics/logsOracleBISchedulerComponent/coreapplication_obisch1
Example:
C:\OBIEE_11g\instances\instance1\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1
File to check:
nqscheduler.log
Example:
C:\OBIEE_11g\instances\instance1\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1
File to check:
nqscheduler.log
5.1) iBot log files.
- You can review the log files using the Windows client tool Job Manager
- You can also review the following log files:
Agent-1-1.err
Agent-1-1.log
Agent-1-1.log
Review the instanceconfig.xml file under
<Middleware Home>\instances\instance1\config\OracleBISchedulerComponent\coreapplication_obisch1
Example:
C:\OBIEE_11g\instances\instance1\config\OracleBISchedulerComponent\coreapplication_obisch1
to see the path where the iBot log files are created:
<iBots>
<Log_Dir>C:\OBIEE_11g\instances\instance1\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1</Log_Dir>
<!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><Web_Server>jjuan2-es.es.oracle.com:9710</Web_Server>
</iBots>
<Log_Dir>C:\OBIEE_11g\instances\instance1\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1</Log_Dir>
<!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><Web_Server>jjuan2-es.es.oracle.com:9710</Web_Server>
</iBots>
By default, it is the same path as the Scheduler log but you can modify.
The path is:
<Middleware Home>\instances\instance1\config\OracleBISchedulerComponent\coreapplication_obisch1
Example:
C:\OBIEE_11g\instances\instance1\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1
Example:
C:\OBIEE_11g\instances\instance1\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1
6) Cluster Controller
<Middleware Home>/instances/instance1/diagnostics/logs/OracleBIClusterControllerComponent\coreapplication_obiccs1
Example:
C:\OBIEE_11g\instances\instance3\diagnostics\logs\OracleBIClusterControllerComponent\coreapplication_obiccs1
File to check:
nqcluster.log
Example:
C:\OBIEE_11g\instances\instance3\diagnostics\logs\OracleBIClusterControllerComponent\coreapplication_obiccs1
File to check:
nqcluster.log
7) ODBC
<Middleware Home>/instances/instance1/diagnostics/logs/OracleBIODBCComponent/coreapplication_obips1
Example:
C:\OBIEE_11g\instances\instance3\diagnostics\logs\OracleBIODBCComponent\coreapplication_obips1
Example:
C:\OBIEE_11g\instances\instance3\diagnostics\logs\OracleBIODBCComponent\coreapplication_obips1
8) Weblogic Server (WLS) Managed Server/Security Providers.
In a Simple installation type, there is NO Managed Server, so these log files does not exist in a Simple installation.
<Middleware Home>/user_projects/domains/bifoundation_domain/servers/bi_server1/logs
or
<BI Domain Home>/servers/bi_server1/logs/
Example:
C:\OBIEE_11g\user_projects\domains\bifoundation_domain\servers\bi_server1\logs\
access.log
bi_server1.log
bi_server1.out
bi_server1.out00001
bi_server1-diagnostic.log
or
<BI Domain Home>/servers/bi_server1/logs/
Example:
C:\OBIEE_11g\user_projects\domains\bifoundation_domain\servers\bi_server1\logs\
access.log
bi_server1.log
bi_server1.out
bi_server1.out00001
bi_server1-diagnostic.log
9) Weblogic Server (WLS) Admin Server.
If there is no Managed Server (for instance, you did Simple Install), you should review these log files:
<Middleware Home>\user_projects\domains\bifoundation_domain\servers\AdminServer\logs
Example:
C:\OBIEE_11G\user_projects\domains\bifoundation_domain\servers\AdminServer\logs
access.log
AdminServer.log
AdminServer-diagnostic.log
Example:
C:\OBIEE_11G\user_projects\domains\bifoundation_domain\servers\AdminServer\logs
access.log
AdminServer.log
AdminServer-diagnostic.log
Domain log file
bifoundation_domain.log
10) Oracle Process Management (OPM)
<Middleware Home>/instances/instance1/diagnostics/logs/OPMN/opmn
Example:
C:\OBIEE_11g\instances\instance3\diagnostics\logs\OPMN\opmn
Files to check:
debug.log
logquery~1.log
opmn.log
opmn.out
service.log
Example:
C:\OBIEE_11g\instances\instance3\diagnostics\logs\OPMN\opmn
Files to check:
debug.log
logquery~1.log
opmn.log
opmn.out
service.log
11) Upgrade Assistant (ua).
<OBIEE_HOME>/upgrade/logs
Example
C:\OBIEE_11g\Oracle_BI1\upgrade\logs
Files to check:
ua2010-10-20-14-30-21PM.log
Example
C:\OBIEE_11g\Oracle_BI1\upgrade\logs
Files to check:
ua2010-10-20-14-30-21PM.log
12) OBIEE Patches applied with Opatch
The path for the log files for OBIEE patches applied with OPatch tool is:
<Middleware Home>/Oracle_BI1/cfgtoollogs/opatch
<Middleware Home>/Oracle_BI1/cfgtoollogs/opatch
Example:
Log file location : C:\OBIEE_11G\Oracle_BI1\cfgtoollogs\opatch\opatch2010-09-24_16-52-41PM.log
Patch history file: C:\OBIEE_11G\Oracle_BI1\cfgtoollogs\opatch\opatch_history.txt
Log file location : C:\OBIEE_11G\Oracle_BI1\cfgtoollogs\opatch\opatch2010-09-24_16-52-41PM.log
Patch history file: C:\OBIEE_11G\Oracle_BI1\cfgtoollogs\opatch\opatch_history.txt
Other file to check:
C:\Program Files\Oracle\Inventory\logs
C:\Program Files\Oracle\Inventory\logs
----------------------------------
Please, review also the following note. It contains information about the Web Logic Server (WLS) log files and how to increase the log level for OBIEE logs.
Note 1275087.1: What are all the logs and configuration files for OBIEE 11G and where to find them?
If you are trying to debug a specific problem and need assistance from Oracle Support, please run the Remote Diagnostic Agent (RDA) as described in Remote Diagnostic Agent (RDA) - OBIEE 11g - Note 1367015.1. Please upload the RDA files to any new SR that you create to enable quicker resolution of your issue.
Niciun comentariu:
Trimiteți un comentariu