Starting and Stopping the Oracle Stack

A.15 Starting and Stopping the Oracle Stack

This appendix describes how to start and stop the components of the Oracle stack in a specific order. It includes the following sections:

A.15.1 Starting the Stack

This section describes the procedure to start the stack.

Start the stack components in the following order.

Start the Oracle Database.
1. In the Database ORACLE_HOME, set the ORACLE_SID, ORACLE_HOME and PATH environment variables to the appropriate values.
2. Start the listener.
```
ORACLE_HOME/bin/lsnrctl start 
```
3. Start the database.
```
ORACLE_HOME/bin/sqlplus "/as sysdba"
startup
```
Start the Oracle WebLogic Administration Server.

Note:

If you start the Oracle WebLogic Administration Server from the command line as shown, it runs in the foreground and prints output to the screen. You can, however, run the server in the background by using nohup at the beginning of the command line. This sends all output to the file nohup.out and prevents the script from prompting you for USER_NAME and PASSWORD. To pass parameters to StartWebLogic.sh when using nohup, you can use a boot identity file, as described in the Starting and Stopping Servers chapter of Administering Server Startup and Shutdown for Oracle WebLogic Server.
```
$DOMAIN_HOME/bin/startWebLogic.sh
```
When executing these scripts:
- The default value for DOMAIN_NAME is base_domain
- You will be prompted for values for USER_NAME and PASSWORD if you do not provide them as options when you execute the script.
Ensure that the Node Manager is running. If, for some reason, the Node Manager is not running, start it.
```
$DOMAIN_HOME/bin/startNodeManager.sh
```
Start WebLogic system components, such as Oracle Internet Directory.
```
$DOMAIN_HOME/bin/startComponent.sh <instance-name>
```
You can verify that the system components have started in a WLST shell by executing:
```
oid_instanceStatus(instanceName = 'instance-name')
```
Start WebLogic Managed Servers, such as Oracle Directory Integration Platform.
```
$DOMAIN_HOME/bin/startManagedWebLogic.sh \
{SERVER_NAME} {ADMIN_URL} {USER_NAME} {PASSWORD}
```
To start managed components in the background, you can use the Oracle WebLogic Administration Console. See Overview of Administration Consoles in Understanding Oracle WebLogic Server for more information.

You can view the status of WebLogic managed components with Oracle Enterprise Manager Fusion Middleware Control. See Overview of Using Fusion Middleware Control to Manage Oracle Internet Directory.

A.15.2 Stopping the Stack

You can stop the Administration Server and all the managed servers by using Oracle WebLogic Administration Console.

See Overview of Administration Consoles in Understanding Oracle WebLogic Server for more information.

To stop the stack components from the command line, issue the commands in the following order.

Stop WebLogic Managed Servers such as WLS_ODS1. The Oracle Directory Integration Platform (DIP) typically runs from the WLS_ODS1 Managed Server.
```
$DOMAIN_HOME/bin/stopManagedWebLogic.sh \
{SERVER_NAME} {ADMIN_URL} {USER_NAME} {PASSWORD}
```
Stop WebLogic system components, such as Oracle Internet Directory.
```
$DOMAIN_HOME/bin/stopComponent.sh <instance-name> 
```
Stop the WebLogic Administration Server.
```
$DOMAIN_HOME/bin/stopWebLogic.sh
```
If you want to stop the Node Manager:
```
$DOMAIN_HOME/bin/stopNodeManager.sh
```
Stop the Oracle Database.
1. In the Database ORACLE_HOME, set the ORACLE_SID, ORACLE_HOME, and PATH environment variables to the appropriate values.
2. Stop the database.
```
ORACLE_HOME/bin/sqlplus "/as sysdba"
shutdown immediate 
```
3. Stop the listener.
```
ORACLE_HOME/bin/lsnrctl stop
```