Starting and stopping OBIEE in 10g and 11g

Starting/Stopping Oracle OBIEE 11G

OBIEE 11g is hosted on Weblogic and hence the scripts to start/stop services is totally different from that in 10G.

The start sequnces is:

• Node Manager (wls console and EM, scripts located in  WLS_HOME/bin)
• AdminServer (scripts located under domain/bi_foundation/bin)
• BI Managed Server  (scripts located under domain/bi_foundation/bin)
• Process Manager (Start all bi Services, scripts located at INSTANCE_HOME/bin, uses opmnctl -startall/status)

The Scripts are:

• Node Manager: startNodeManager (cmd or sh)
• AdminServer: startWeblogic (cmd or sh)
• BI Managed Server: startManagedServer (cmd or sh)
• Process Manager: opmnctl  startall

 

Stop Sequence:

The reverse order needs to be followed to stop Services.

• opmnctl stopall
• stopManagedServer (cmd or sh)
• stopWeblogic (cmd or sh)
• Node Manager: To stop nodemanager on unix directly kill the process. On windows if registered as a service stop node manager service.

 

Starting/Stopping Oracle OBIEE 10G

Oracle BI start/stop scripts are located in the directory OracleBI_HOME/setup. The main  scripts are:

• oc4j (start OC4J)
• run-sa.sh (calls user.sh and starts the Oracle BI Server)
• run-saw.sh (calls saw.sh and starts the Oracle BI Presentation Services.)
• run-sch.sh (for BI Scheduler)
• run-ccs.sh (for the Cluster Controller)
• sa-cli.sh (Sets up the environment for running the Oracle BI Client)

The order in which the differnt services in OBIEE are stopped/restarted is important. Below is the start sequence for OBI Component:

• OC4J
• Oracle Business Intelligence Server service.
• Oracle Business Intelligence Presentation Services service.
• Oracle Business Intelligence Scheduler Server service.

Scripts to start:

oc4j -start

run-sa.sh start
run-saw.sh start
run-ccs.sh start  --> Oracle BI Cluster Controller (Only required if OBIEE Cluster is setup)

 

Scripts to Stop:

 

run-ccs.sh stop
run-saw.sh stop
run-sa.sh stop
oc4j -shutdown -port 23791 -password oc4jadmin

OBIEE 11G and 10G Logs

The log files for OBIEE Individual components are under INSTANCE_HOME/instances/instance1/diagnostics/logs. 

11G has neatly compartmentalised logs for each individual components of OBIEE, Below are the location for each of thos components.

Installation log    -->  OBIEE_HOME/logs

nqquery log   -->     OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1

nqserver log   -->     OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1

servername_NQSAdminTool log   -->  OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1

servername_NQSUDMLExec log  -->  OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1

servername_obieerpdmigrateutil log (Migration log)  -->   OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1

sawlog0 log (presentation)      -->     OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIPresentationServicesComponent/coreapplication_obips1

jh log (Java Host)     -->     OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIJavaHostComponent\coreapplication_obijh

webcatupgrade log (Web Catalog Upgrade)     -->    OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIPresentationServicesComponent/coreapplication_obips1

nqscheduler log (Agents)        --> OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBISchedulerComponent/coreapplication_obisch1

nqcluster log    -->   OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIClusterControllerComponent\coreapplication_obiccs1

ODBC log      -->     OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIODBCComponent/coreapplication_obips1

opmn log      -->      OBIEE_HOME/instances/instance1/diagnostics/logs/OPMN/opmn

Also Logs can be accessed via the EM Console http://server.domain:7001/em

navigate to: Farm_bifoundation_domain-> Business Intelligence-> coreapplications-> Dagnostics-> Log Messages

It is also possible to set individual component level logging from the EM console or rather manage logging for the whole system:

Farm_bifoundation --> application deployment. Select the component and right click to get the options, select logs --> log configuration or view log

OBIEE 10G:

The main logs in OBIEE 10G are as below.

1. BI Presentation Server log can be located from BI_HOME\OracleBIData\web\log\sawlog0.log

This log is useful for Presentation Server login issues and answers/dashboard related issues.

To increase the logging on this server to get a detailed logging to troubleshoot the SSO and integration issues by modifying the logconfig.xml file present in C:\OracleBIData\web\config folder

2. BI Server logs are NQServer.log and NQQuery.log present in BI_HOME\OracleBI\server\Log folder

 NQServer.log consists of BI Server Start up issues and Subject areas loaded and the datasources connected from within the RPD. If the NQSConfig.ini has errors or if RPD has version issues or if proper RPD is not loaded, the BI Server fails to start and this will be recorded in the NQServer.log

NQQuery.log consits of BI Server query operations. We can also check if the result is coming from cache or straight from database. We can get the actual time to execute the query. We can get the physical and logical query from this log.

3. BI Cluster Controller log can located from BI_HOME\OracleBI\server\Log folder. When the cluster is setup with OBIEE server nodes, the NQCluster.log file would provide the cluster nodes connectivity and status information. Along with the NQServer.log , NQCluster.log would be very useful for cluster related issues.

4. BI Javahost can be located from BI_HOME\OracleBIData\web\log\javahost\jhost0.log. This is used for identifying the issues with the charts and graphs generated by Java from Answers/Dashboard reports.

5. BI Scheduler can be located from BI_HOME\OracleBI\server\Log\NQScheduler.log. This is used for identifying the issues related to delivers/scheduler. To increase the logging on scheduler, set the debug flag to true in the scheduler job manager configuration window.