Oracle® Business Intelligence Enterprise Edition Deployment Guide > Clustering, Load Balancing, and Failover in Oracle Business Intelligence >
Troubleshooting an Oracle BI Clustered Environment
Log files for Oracle BI components help you trouble shoot issues that may occur in your BI deployment after enabling the clustering, load balancing and failover capabilities of Oracle BI. To effectively diagnose issues, understand the lines of communication that occur as described in the topic Communication Between Oracle BI Components in a Clustered Environment in this chapter. Review the log files for the BI components for every instance in the cluster. The table below shows the log file and its location for each BI component. Log files will record any client-side failures that may have occurred due to misconfiguration. While some Failover events are not logged, the Cluster Controller log file will record crashes of any BI Scheduler or BI Server instances. Review the Event Viewer log on Windows and syslog on Linux or UNIX systems. Review the log files after initial start up. If an BI Server or BI Scheduler instance has not been configured correctly and as expected by the Cluster Controller, then the instance, though it may not shut down, will not be added to the cluster. The log files will record such failures. The following table lists the log files for BI Components.
|
|
|
BI Server |
NQServer.log |
- Windows OracleBI_HOME\server\Log§
- Linux or UNIX
OracleBI_HOME/server/Log
|
BI Cluster Controller |
NQCluster.log |
- Windows
OracleBI_HOME\server\Log§
- Linux or UNIX
OracleBI_HOME/server/Log
|
BI Scheduler |
NQScheduler.log |
- Windows
OracleBI_HOME\server\Log§
- Linux or UNIX
OracleBI_HOME/server/Log
|
BI Presentation Services |
sawlog*.log (For example, sawlog0.log) |
- Windows
OracleBIData_HOME\web\log§
- Linux or UNIX
OracleBIData_HOME/web/log
|
BI JavaHost |
host*.log.* (For example, jhost0.log.0) |
- Windows
OracleBIData_HOME\web\log\javahost
- Linux or UNIX
OracleBIData_HOME/web/log/javahost
|
|