This is an attempt to share one of the important information from Oracle Documentation regarding the various log files for OBIEE 11g. It is more than copy and paste type of the blog, which I think is useful for debugging activities.
WLS Admin Server
The log level can be maintained via WLS Console>biFoundation_doman>servers>
AdminServer, by default all messages are published.
Log Files Name
§ AdminServer.log
§ bifoundation_domain.log
§ AdminServer-diagnostic.log (BI JEE log, Action Services and Security Services)
§ access.log
§ \logs\bipublisher\bipublisher.log
Log Location
§ <Middleware_HOME>user_projects\domains\bifoundation_domain\servers\AdminServer
\logs
Example
· D:\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs
WLS Managed Server
The log level can be maintained via WLS Console>biFoundation_doman>servers>
bi_server1, by default all messages are published.
Log Files Name
§ bi_server1.log
§ bi_server1.out
§ bi_server1.out00001 etc
§ bi_server1-diagnostic.log (BI JEE log (Action Services and Security Services), - review in FMC)
§ access.log
§ \logs\bipublisher\bipublisher.log
Log Location
§ <Middleware_HOME>user_projects\domains\bifoundation_domain\servers\bi_server1\logs
Example
· D:\Middleware\user_projects\domains\bifoundation_domain\serversr\bi_server1\logs
BI System Components (BI instance)
Oracle BI ServerComponent
The log level can be set to higher level by using Fusion Middleware Diagnostics tab > Log Configuration. The permitted log levels are as follows incident error option, error option, warning option, notification option and trace option such as set Trace to ‘FINEST’ ( performance impact) .
For nqquery.log set level 0 trough 5 in BI Admin Tool / can be set by using LOGLEVEL system session variable.
Log Files Name
§ nqserver.log
§ Nqquery.log
§ Administrator_NQSAdminTool.log
§ Administrator_nQUDMLExec.log
Log Location
§ <ORACLE_INSTANCE>\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1\
Example
· D:\Middleware\instances\instance\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1\
Oracle BI Presentation Services Components
The log level can be set to higher level by using Fusion Middleware Diagnostics tab > Log Configuration. The permitted log levels are as follows incident error option, error option, warning option, notification option and trace option such as set Trace to ‘FINEST’ ( performance impact) .
Log Files Name
§ sawlog0.log
§ webcatupgrade0.log
§ \catalogcrawler\sawcatalogcrawlerlogsys0.log
Log Location
§ <ORACLE_INSTANCE>\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1\
Example
· D:\Middleware\instances\instance\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1\
Oracle BI Scheduler Services Components
The log level can be set to higher level by using Fusion Middleware Diagnostics tab > Log Configuration. The permitted log levels are as follows incident error option, error option, warning option, notification option and trace option such as set Trace to ‘FINEST’ ( performance impact)
Log Files Name
§ nqscheduler-<n>.log
Log Location
§ <ORACLE_INSTANCE>\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1\
Example
· D:\Middleware\instances\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1\
Oracle BI Java Host Components
The log level can be set to higher level by using Fusion Middleware Diagnostics tab > Log Configuration. The permitted log levels are as follows incident error option, error option, warning option, notification option and trace option such as set Trace to ‘FINEST’ ( performance impact)
The log level can be set to higher level by using Fusion Middleware Diagnostics tab > Log Configuration. The permitted log levels are as follows incident error option, error option, warning option, notification option and trace option such as set Trace to ‘FINEST’ ( performance impact)
Log Files Name
§ Jh.log
§ Jh-n.log
Log Location
§ <ORACLE_INSTANCE>\diagnostics\logs\OracleBIJavaHostComponent\coreapplication_obijh1
Example
· D:\Middleware\instances\instance\diagnostics\logs\OracleBIJavaHostComponent\coreapplication_obijh1
Oracle BI Cluster Controller Components
The log level can be set to higher level by using Fusion Middleware Diagnostics tab > Log Configuration. The permitted log levels are as follows incident error option, error option, warning option, notification option and trace option such as set Trace to ‘FINEST’ ( performance impact)
The log level can be set to higher level by using Fusion Middleware Diagnostics tab > Log Configuration. The permitted log levels are as follows incident error option, error option, warning option, notification option and trace option such as set Trace to ‘FINEST’ ( performance impact)
Log Files Name
§ Nqcluster-<n>.log
Log Location
· <ORACLE_INSTANCE>\diagnostics\logs\OracleBIClusterControllerComponent\coreapplication_obiccs1
Example
· D:\Middleware\instances\instance\diagnostics\logs\OracleBIClusterControllerComponent\coreapplication_obiccs1
OPMN
The log level can be set to higher level by using Fusion Middleware Diagnostics tab > Log Configuration. The permitted log levels are as follows incident error option, error option, warning option, notification option and trace option such as set Trace to ‘FINEST’ ( performance impact)
Log Files Name
§ Debug.log
§ Opmn.log
§ Service.log etc
Log Location
· <ORACLE_INSTANCE>\diagnostics\logs\OPMN\opmn
Example
· D:\Middleware\instances\instance1\diagnostics\logs\OPMN\opmn
Java Components
Embedded LDAP
Log Files Name
§ EmbeddedLDAP.log
§ EmbeddedLDAPAccess.log
Log Location
· DOMAIN_HOME/servers/server_name/data/ldap/log/EmbeddedLDAP.log
Example
· D:\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\data\ldap\log
Miscellaneous
Repository Log
Log Files Name
§ <Repository Name> .rpd.log
Log Location
· <ORACLE_INSTANCE>\OracleBIServerComponent\coreapplication_obis1\repository\
Example
· D:\Middleware\instances\instance\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository
Update Log
Log Files Name
§ ua<timestamp>.log
Log Location
· BI_ORACLE_HOME\upgrade\logs
Example
· D:\Middleware\Oracle_BI1\upgrade\logs\us2012-02-15-12-06-10PM.log
Usage Tracking Log (if redirected to logs rather than tables)
Update Log
Log Files Name
§ NQAcct.yyyymmdd.hhmmss.log
Log Location
STORAGE_DIRECTORY parameter in the Usage Tracking section of the NQSConfig.INI file determines the location of usage tracking log files
BI Agent Log
Log Files Name
§ Agent-JobID-InstanceID.xxx
Log Location
The default location for log files is the Log directory in the Oracle Business Intelligence installation directory on the computer where the Oracle BI Scheduler is installed.
Example
· D:\Middleware\Oracle_BI1\upgrade\logs\us2012-02-15-12-06-10PM.log
Install/De-install/Patch
Log Files Name
§ deinstall2010-08-15_09-01-33PM.out
§ deinstall2010-08-15_09-01-33PM.log
§ installProfile2010-08-15_09-01-33PM.log
§ oraInstall2010-08-15_09-01-33PM.out
§ oraInstall2010-08-19_01-21-49AM.err
§ OPatch2010-08-19_02-15-05-AM.log
§ 2010-08-19_01-21-49AM.log
§ installProfile2010-08-19_01-21-49AM.log
Log Location
· Linux and UNIX: USER_HOME/oraInventory/logs/
· Windows: C:\Program Files\Oracle\Inventory\logs\
Example
· C:\Program Files\Oracle\Inventory\logs\
