Sie sind auf Seite 1von 15

OBIEE 11g Domain Start & Stop in Linux

Starting & stopping the OBIEE 11g Domain on a Windows platform is very simple thanks to the
shortcuts created during the installation. However, on a Linux platform this becomes a bit more
tedious as there are no scripts for that.
In this article you will find the scripts needed to start & stop the OBIEE 11g Domain.
Note 1: In the scripts listed below, make sure you replace $OBIEE11g_MW_HOME with the
Middleware Home folder specified during installation (e.g. /OBIEE11g).
Note 2: Also replace <OBIEE_11g_server> with the IP of the server where OBIEE 11g has
been installed.
Components
The OBIEE 11g Domain has four main components (apart from the Supporting Database
Schemas created by RCU) that need to be started to have the system started. This four main
components are:
1. WebLogic Domain
2. Node Manager
3. Managed Server
4. Oracle BI System Components (started using OPMN)
Starting the OBIEE 11g Domain Components
1.a. WebLogic Domain
Open a new Terminal window and execute the following command line:
$OBIEE11g_MW_HOME/user_projects/domains/bifoundation_domain/bin/startWebLogic.sh
WebLogic requires the WebLogic administrator username and password to be started (e.g.
weblogic/Admin123). Type it in when prompted in the Terminal window.
This Terminal window execution will be kept on without returning to the shell. Make sure it is
not closed.
1.b. Node Manager
Open a new Terminal window and execute the following command line:
$OBIEE11g_MW_HOME/wlserver_10.3/server/bin/startNodeManager.sh
This Terminal window execution will be kept on without returning to the shell. Make sure it is
not closed.
WebLogic and NodeManager can run in parallel, so there is no need to wait for the first one
to stop having activity to start the second one.
Check that these two processes have been started by opening a web browser and typing in the
following address into the address bar:
http://<OBIEE_11g_server>:7001/console
The above URL should retrieve the following web page:

Image 1: Oracle Weblogic Server 11g
When the above screenshot is retrieved you will know that both WebLogic Domain and
NodeManager have been started.
2. Managed Server
Open a new Terminal window and execute the following command line:
$OBIEE11g_MW_HOME/user_projects/domains/bifoundation_domain/bin/startManagedWebL
ogic.sh bi_server1
Insert the credentials for the WebLogic administrator (weblogic/Admin123) when prompted.
This Terminal window execution will be kept on without returning to the shell. Make sure it is
not closed.
Check that it has been started by opening a web browser and typing in the following address into
the address bar:
http://<OBIEE_11g_server>:7001/em
Insert the credentials for the WebLogic administrator (weblogic/Admin123). This will log you
into the Enterprise Manager application.

Image 2: Enterprise Manager application
Verify that the WebLogic server bi_server1 is started as shown in the above screenshot.
3. Oracle BI System Components (started using OPMN)
Open a new Terminal window and execute the following command line:
$OBIEE11g_MW_HOME/instances/instance1/bin/opmnctl startall
This Terminal window execution will complete. You may close it then if you wish to do so.
Stopping the OBIEE 11g Domain Components
1. Oracle BI System Components (started using OPMN)
Open a new Terminal window and execute the following command line:
$OBIEE11g_MW_HOME/instances/instance1/bin/opmnctl stopall
2. Managed Server
In the same Terminal window execute the following command line:
$OBIEE11g_MW_HOME/user_projects/domains/bifoundation_domain/bin/stopManagedWebL
ogic.sh bi_server1
Insert the credentials for the WebLogic administrator (weblogic/Admin123) when prompted.
This will complete the execution of Managed Server that was open in a Terminal window
since the process was started. You may close this Terminal window now.
3. Node Manager
In the same Terminal window execute the following command line:
ps -ef |grep Node|grep nodemanager |cut -c10-15
This will show the Node Manager process. Write down its PID. Then execute:
kill <NodeManager_PID>
Note that <NodeManager_PID> should be replaced by the PID found in the previous step.
This will complete the execution of Node Manager that was open in a Terminal window
since the process was started. You may close this Terminal window now.
4. WebLogic Domain
In the same Terminal window execute the following command line:
$OBIEE11g_MW_HOME/user_projects/domains/bifoundation_domain/bin/stopWebLogic.sh
This will complete the execution of WebLogic Domain that was open in a Terminal window
since the process was started. You may close this Terminal window now.
- See more at: http://www.clearpeaks.com/blog/oracle-bi-ee-11g/obiee-11g-domain-start-stop-in-
linux#sthash.vW8FnRMe.dpuf
Stop and Start OBIEE 11g Linux
The following commands will help you stop and start an OBIEE 11g domain in a
Linux envirnonment.
STOP OBIEE 11G

Step 1 of 4: Shutdown OPMN Components

Oracle Process Manager should be used to shutdown all system components.
Linux Command Line
$ cd /opt/app/obiee/fmw_home1/instances/instance1/bin
$ ./opmnctl stopall
$

Step 2 of 4: Shutdown Managed Server

By default there should be one managed server, bi_server1 that we will shut
down. At the point you should shut down any other Managed Servers in this
WebLogic domain.
Linux Command Line
$ cd
/opt/app/obiee/fmw_home1/user_projects/domains/bifoundation_domain/bin
$ stopManagedWebLogic.sh bi_server1 t3://machine:7001 weblogic weblogic1
$

Verify that the Managed Server has shutdown completely with ps -ef | grep
bi_server1.

Step 3 of 4: Shutdown Node Manager

There should be a single Node Manager for the machine. Shut it down with the
command below.
Linux Command Line
$ ps -ef | grep Node | grep nodemanager | grep -v grep | cut -c10-15
Linux Command Line
$ kill -9 ####
$

Step 4 of 4: Shutdown Admin Server

There should be a single Node Manager for the machine. Shut it down with the
command below.
Linux Command Line
$ cd
/opt/app/obiee/fmw_home1/user_projects/domains/bifoundation_domain/bin
$ ./stopWebLogic.sh weblogic weblogic1 t3://machine:7001
$

Verify that the Managed Server has shutdown completely with ps -ef | grep
AdminServer.
START OBIEE 11G

Step 1 of 4: Start Admin Server

Remember to run standard variable scripts first.
Linux Command Line
$ cd
/opt/app/obiee/fmw_home1/user_projects/domains/bifoundation_domain/bin
$ nohup ./startWebLogic.sh -Dweblogic.management.username=weblogic -
Dweblogic.management.password=weblogic1 &
$ tail -f nohup.out
$

After issueing the start command we tail the log until we see the message below,
indicating that the server has started successfully.
<WebLogicServer> <BEA-000360> <Server started in RUNNING mode>


Step 2 of 4: StartNode Manager

There should be a single Node Manager for the machine. Start it up with the
command below.
Linux Command Line
$ cd /opt/app/obiee/fmw_home1/wlserver_10.3/server/bin
$ nohup ./startNodeManager.sh > NOD.out &
$ tail -f NOD.out

After issueing the start command we tail the log until we see the message below,
indicating that the server has started successfully.
<Info> <Secure socket listener started on port ####>

Step 3 of 4: Start Managed Server

By default there should be one managed server, bi_server1 that we will start
up. At this point you should start any other Managed Servers in this WebLogic
domain.
Linux Command Line
$ cd /opt/app/obiee/fmw_home1/wlserver_10.3/common/bin
$ ./commEnv.sh
$ cd
/opt/app/obiee/fmw_home1/user_projects/domains/bifoundation_domain/bin
$ ./setDomainEnv.sh
$ nohup ./startManagedWebLogic.sh bi_server1 t3://machine:7001 >
bis1_startup.log &
$ tail nohup.out

After issueing the start command we tail the log until we see the message below,
indicating that the server has started successfully.
Server started in RUNNING mode

Step 4 of 4: Startup OPMN Components

Oracle Process Manager should be used to shutdown all system components.
Linux Command Line
Linux Command Line
$ cd /opt/app/obiee/fmw_home1/instances/instance1/bin
$ ./opmnctl startall
$ ./opmnctl status
$

The opmnctl command stopall should shutdown all running components including
opmnctl. You can verify this by running the status command which should return
an error. You should see ouput such as below.
Linux Command Line
Processes in Instance: instance1
---------------------------------+--------------------+---------+----------+---------
---+----------+-----------+------
ias-component | process-type | pid | status | uid | memused | uptime | ports
---------------------------------+--------------------+---------+----------+---------
---+----------+-----------+------
coreapplication_obiccs1 | OracleBIClusterCo~ | 11741 | Alive | 70916792 |
55188 | 0:01:01 | N/A
coreapplication_obisch1 | OracleBIScheduler~ | 11740 | Alive | 70916789 |
122388 | 0:01:01 | N/A
coreapplication_obijh1 | OracleBIJavaHostC~ | 11739 | Alive | 70916790 |
1186088 | 0:01:01 | javahost:9810
coreapplication_obips1 | OracleBIPresentat~ | 11742 | Alive | 70916791 |
261576 | 0:01:01 | N/A
coreapplication_obis1 | OracleBIServerCom~ | 11738 | Alive | 70916788 |
150904 | 0:01:01 | N/A









Few more notes :-


How To Start / Stop An OBIEE 11g (11.1.1.x)
Unix / Linux Environment Via Command-line
How To Start / Stop An OBIEE 11g (11.1.1.x) Unix / Linux Environment Via Command-line
Starting the environment via command-line:
The high-level manual steps are:
Set your environment
Start WLS Admin Server in the background
Start WLS NodeManager
Start WLS Managed Server
Start Oracle Instance
Note: init.d boot time startup scripts are not covered here. These examples are from Oracle Enterprise
Linux 5


1. Set your environment (manually or via script).
Note: You may use the standard environment scripts (commEnv.sh, setDomainEnv.sh, etc) ; however,
these are the minimal variables necessary for these examples



MW_HOME=/[path]/[obiee11g_middleware_home]; export MW_HOME
DOMAIN_HOME=/$MW_HOME/user_projects/domains/bifoundation_domain; export DOMAIN_HOME
WL_HOME=$MW_HOME/wlserver_10.3; export WL_HOME
ORACLE_HOME=$MW_HOME/Oracle_BI1; export ORACLE_HOME
ORACLE_INSTANCE=$MW_HOME/instances/instance1; export ORACLE_INSTANCE
#
# You may also want to set your PATH environment to avoid having to use
# paths in the commands
#
PATH=$WL_HOME/server/bin:$DOMAIN_HOME/bin:$ORACLE_INSTANCE/bin:$ORACLE_HOME/OPatch:$PA
TH; export PATH

2. Start the WebLogic (WLS) Administration Server in the background
Note: For username and password, you can:
o pass username/pwd in the command line,
o use the boot.properties file for an encrypted username/password
o set as environment variables - WLS_USER / WLS_PW,
o or pass WLS_USER /WLS_PW in the start scripts.

Please see the Oracle WebLogic documentation to determine what meets your need.

In these examples, you can name the logs whatever you desire.


Execute:
nohup sh $DOMAIN_HOME/bin/startWebLogic.sh -Dweblogic.management.username=weblogic -
Dweblogic.management.password=[_your_password_] > wls_start.log &

Next, tail the log to determine if the server started completely.

execute:
tail -f [log name]

wait until you see:
<WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

there should be no further lines after this. If successful, proceed to step 3. If errors, correct them and
restart.
Note: This takes some time. The terms "takes some time", "starts fast", "starts slow", "takes xx amount of
time" are all relative terms depending upon resources in your environment.

3. Start Node Manager


Note: In this example, the username and password are embedded in script via WLS_USER
and WLS_PW. If you need another method or a more secure method, like a boot.properties file, then
please see:
Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server 11g
Release 1 (10.3.1)



Execute:
nohup sh $WL_HOME/server/bin/startNodeManager.sh > startNodeManager.log &

Next, tail the log to determine if the server started completely.
tail -f [log name]


Look for <INFO> <Secure socket listener started on port 9556>
Note: starts fast



4. Start the OBI Managed Server (bi_server1 -- default - java bits)
Note: This can be started via Fusion Middleware Control or WebLogic Administration Console as well.
For this example, modify WLS_USER and WLS_PW in the startManagedWebLogic.sh script to the values
chosen during installation. You can set ADMIN_URL in the environment, in the script or pass on the
command-line. In this example, it is passed on the command-line.



Execute:
nohup sh $DOMAIN_HOME/bin/startManagedWebLogic.sh bi_server1 http://server.domain:7001
> start_bi_server1.log &

Next, tail the log to determine if the server started completely.
tail -f [log name]


look for "Server started in RUNNING mode:
<Mon D, YYYY H:MM:SS PM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started
WebLogic Managed Server "wls_ods1" for domain "IDMDomain" running in
Production Mode>
<Mon D, YYYY H:MM:SS PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server
state changed to RUNNING>
<Mon D, YYYY H:MM:SS PM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server
started in RUNNING mode

Note: takes about 30 seconds depending upon your environment. At this point, you could start any other
servers that you have configured in the same manner. For example, WLS_DISCO, WLS_PORTAL.



5. Start the OBIEE System Components ( BI Servers -- c++ bits)
$ORACLE_INSTANCE/bin/opmnctl startall

Next, execute: opmnctl status or opmnctl status -l (lower case L) to ensure the
processes are started properly/completely.


The output will look similar to this:


$ORACLE_INSTANCE/bin/opmnctl status -l

Processes in Instance: instance1
---------------------------------+--------------------+---------+----------+----------
--+----------+-----------+------
ias-component | process-type | pid | status | uid | memused | uptime | ports
---------------------------------+--------------------+---------+----------+----------
--+----------+-----------+------
coreapplication_obiccs1 | OracleBIClusterCo~ | 11741 | Alive | 70916792 | 55188 |
0:01:01 | N/A
coreapplication_obisch1 | OracleBIScheduler~ | 11740 | Alive | 70916789 | 122388 |
0:01:01 | N/A
coreapplication_obijh1 | OracleBIJavaHostC~ | 11739 | Alive | 70916790 | 1186088 |
0:01:01 | javahost:9810
coreapplication_obips1 | OracleBIPresentat~ | 11742 | Alive | 70916791 | 261576 |
0:01:01 | N/A
coreapplication_obis1 | OracleBIServerCom~ | 11738 | Alive | 70916788 | 150904 |
0:01:01 | N/A


Stopping the enviroment cleanly via the command-line:
Reverse the steps above with the following commands:
Note: You can look inside the respective scripts or the documentation for alternative or more secure
methods. You can also kill the processes, but you may risk corruption.
1. Stop the Oracle Instance
$ORACLE_INSTANCE/bin/opmnctl stopall
2. Stop the OBIEE Managed Server (bi_server1)
$DOMAIN_HOME/bin/stopManagedWebLogic.sh bi_server1
t3://host.domain:7001 username password

If running other managed servers, then stop them in the same manner.
3. Stop the the WebLogic (WLS) Administration Server
$DOMAIN_HOME/bin/stopWebLogic.sh username password
t3://host.domain:7001
4. At this point, since the node manager was started in another shell in the background, then you
will need to kill the JVM process that the node manager is running under. There should be no risk
of corruption at this point since everything is already shutdown. If you had started the node
manager in a shell (and not in the background), then you could just close the shell.

You can use the command ps -ef | grep [os user] to check for running processes under
the specified user and then kill the JVM process with kill -9 [PID] (where PID is the process
id of the running JVM)

How to clear the BI Server cache using command line script or via the
Issue SQL page
This post will explain how to clear the BI Server cache using either (1) a script, or (2) the user
interface.
You may need to clear your cache to allow the data in the cache to get refreshed.
(1) Clearing the cache using Command Line script
This example is for Linux/Unix, but can be easily adjusted for Windows.
Create a file called purgecache.txt and place it at
[FMW_HOME]/instances/instance1/bifoundation/OracleBIApplication/coreapplication/set
up
In the file, enter the code call SAPurgeAllCache() (without the quotes) which is a special
BI Server command for clearing the entire cache.
Then create a shell script called purgecache.sh, located in a directory where you store your
custom scripts which includes the following 2 commands
(Note: there is a space after the dot in the below command)
.
/[FMW_HOME]/instances/instance1/bifoundation/OracleBIApplication/coreapplication/set
up/bi-init.sh
(Note: the below is ONE long command; not 2 commands)
[FMW_HOME]/Oracle_BI1/bifoundation/server/bin/nqcmd -d AnalyticsWeb -u
administrator -p pswd s
[FMW_HOME]/instances/instance1/bifoundation/OracleBIApplication/coreapplication/set
up/purgecache.txt
Then you may execute the shell script just as you would any other script (for
example ./purgecache.sh ) -or- you may add this new script to your crontab if desired for
example, to run each night before your cache seeding reports run.
(2) Clearing the cache using the Issue SQL page
Log into OBIEE Analytics using an ID that has the Administration link privilege.
http://server:9704/analytics
Click on the Administration link located at the top right of the page.

Click on the Issue SQL link at the bottom left of the page.

In the Issue SQL window, enter the command: call SAPurgeAllCache() (without the
quotes)
Click the Issue SQL button to execute the command.

You should see a message indicating that the command was executed successfully (assuming
you have caching turned on).
Your cache directory located at
[FMW_HOME]/instances/instance1/bifoundation/OracleBIServerComponent/
coreapplication_obis1/cache
should now be empty.