Starting and Stopping OBIEE

OBIEE 11g init.d Script

Right away I suggest you take a look at RittmanMead’s init.d script located here on github. This script is really well written and handles the startup and shutdown of Node Manager, Admin Server, bi_server, and OPMN. Enable it with chkconfig and and it will nicely handle server reboots. I also like to call this script via Ansible playbooks after deploying RPDs or doing a security migration to make changes take affect.

OBIEE 11g Manually

I would highly recommend setting up your files for both AdminServer and bi_servers. This way you will not be prompted to enter a username/password during the service startups.

Create files in these locations:


Put your weblogic username and password in these files like this:


On the next server startup the contents of these files will be encrypted and used to startup the server without login prompts.




$ $ORACLE_HOME/wlserver_10.3/server/bin/


$ ps aux |grep NodeManager
$ kill PID



startNodeManager(verbose='true', NodeManagerHome='$ORACLE_HOME/wlserver_10.3/common/nodemanager/', ListenAddress='');

Shutdown In this example I am using keyfile to login without username/password

 port=9556, domainName='bifoundation_domain',

Admin Server

Startup Script

$ $ORACLE_HOME/user_projects/domains/bifoundation_domain/bin/ 

Shutdown Script

$ $ORACLE_HOME/user_projects/domains/bifoundation_domain/bin/ 


In these examples I am using bi_server1, but might be another server number if this is a cluster.

Startup Script

$ $ORACLE_HOME/user_projects/domains/bifoundation_domain/bin/ bi_server1

Shutdown Script

$ $ORACLE_HOME/user_projects/domains/bifoundation_domain/bin/ bi_server1


In these examples I am using instance1, but might be another instance number if this is a cluster.

Start All

$ $ORACLE_HOME/instance1/bin/opmnctl startall

Stop All

$ $ORACLE_HOME/instance1/bin/opmnctl stopall

Start/stop single OPMN processes

  • First get a status to see what is needing attention. This will also display the ias-component name ```bash $ ORACLE_HOME/instance1/bin/opmnctl status

Processes in Instance: instance1 ———————————+——————–+———+——— ias-component | process-type | pid | status ———————————+——————–+———+——— essbasestudio1 | EssbaseStudio | 27439 | Alive essbaseserver1 | Essbase | 27440 | Alive coreapplication_obiccs1 | OracleBIClusterCo~ | 27438 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 27437 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 27436 | Alive coreapplication_obips1 | OracleBIPresentat~ | N/A | Down coreapplication_obis1 | OracleBIServerCom~ | 27435 | Alive

In this case obips1 is down.  

* Lets start it up using startproc with the ias-component name
$ ORACLE_HOME/instance1/bin/opmnctl startproc ias-component=coreapplication_obips1
opmnctl startproc: starting opmn managed processes...
  • Check the status again and verify it is running coreapplication_obips1 | OracleBIPresentat~ | N/A | Alive


There are a couple of nice surprises when it comes to 12c. First, there are no more OPMN components to worry about. Second, Oracle was kind enough to provide startup/shutdown scripts out of the box! These scripts will control the Node Manager, Admin Server, and the BI server/components.

The scripts


$ $ORACLE_HOME/user_projects/domains/bi/bitools/bin/


$ $ORACLE_HOME/user_projects/domains/bi/bitools/bin/


$ $ORACLE_HOME/user_projects/domains/bi/bitools/bin/

Start/Stop single process

In this example I am starting obips1

$ $ORACLE_HOME/user_projects/domains/bi/bitools/bin/ -i obips1


Another nice feature about 12c is controlling nodes in a cluster. On any additional nodes the only thing you need to start is the Node Manager, and then the primary server will handle the rest.

Additional Nodes

$ nohup $ORACLE_HOME/user_projects/domains/bi/bin/ &
Andrew Martin
Lead BI Infrastructure Architect


comments powered by Disqus