Starting and Stopping Fusion Middleware Control Starting and Stopping Oracle Management Agent

Starting and Stopping Oracle Fusion Middleware 4-7 1. Start any database-based repository: a. Set the ORACLE_HOME environment variable to the Oracle home for the database. b. Set the ORACLE_SID environment variable to the SID for the database default is orcl. c. Start the Net Listener: ORACLE_HOMEbinlsnrctl start d. Start the database instance: ORACLE_HOMEbinsqlplus nolog SQL connect SYS as SYSDBA SQL startup SQL quit 2. Start the Oracle WebLogic Server Administration Server as described in Section 4.2.1 . 3. If you have not already done so, configure Node Manager, as described in Section 4.2.4 . 4. Ensure Node Manager is running. If Node Manager is not running, start it by executing the following command: MW_HOMEuser_projectsdomainsDOMAIN_NAMEbinstartNodeManager.sh 5. Start Oracle Identity Management system components: a. Set the ORACLE_HOME environment variable to the Oracle home and ORACLE_INSTANCE environment variables for the Identity Management components. b. Start OPMN and all system components: opmnctl startall 6. Start the Oracle WebLogic Server Managed Servers as described in Section 4.2.2.2 . Any applications deployed to the server are also started. 7. Start OPMN and all other system components, such as Oracle HTTP Server. a. Set the ORACLE_HOME and ORACLE_INSTANCE environment variables to the Oracle home and Oracle instance for the system components. b. Start OPMN and all system components in that Oracle instance: opmnctl startall 8. If your environment includes components that are targets monitored by Oracle Management Agent, start Oracle Management Agent, as described in Section 4.5 .

4.7.2 Stopping an Oracle Fusion Middleware Environment

To stop an Oracle Fusion Middleware environment: 1. Stop system components, such as Oracle HTTP Server. You can stop them in any order. a. Set the ORACLE_HOME and ORACLE_INSTANCE environment variables to the Oracle home and Oracle instance for the system components. 4-8 Oracle Fusion Middleware Administrators Guide b. Stop OPMN and all system components in that Oracle instance: opmnctl stopall 2. If your environment includes components that are targets monitored by Oracle Management Agent, stop Oracle Management Agent, as described in Section 4.5 . 3. Stop the Oracle WebLogic Server Managed Servers, as described in Section 4.2 . Any applications deployed to the server are also stopped. 4. Stop Oracle Identity Management components: a. Set the ORACLE_HOME environment variable to the Oracle home for the Identity Management components. b. Stop OPMN and all system components: opmnctl stopall 5. Stop the Administration Server as described in Section 4.2.1 . 6. If you want to stop Node Manager, you can use the kill command: kill -9 PID 7. Stop any database-based repository: a. Set the ORACLE_HOME environment variable to the Oracle home for the database. b. Set the ORACLE_SID environment variable to the SID for the database default is orcl. c. Stop the database instance: ORACLE_HOMEbinsqlplus nolog SQL connect SYS as SYSDBA SQL shutdown SQL quit d. Stop the Net Listener: ORACLE_HOMEbinlsnrctl stop

4.8 Starting and Stopping: Special Topics

This section contains the following special topics about starting and stopping Oracle Fusion Middleware: ■ Starting and Stopping in High Availability Environments ■ Forcing a Shutdown of Oracle Database

4.8.1 Starting and Stopping in High Availability Environments

There are special considerations and procedures for starting and stopping High Availability environments, such as: ■ Oracle Fusion Middleware Cold Failover Cluster ■ Oracle Application Server Disaster Recovery