Starting an Oracle Fusion Middleware Environment

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 Starting and Stopping Oracle Fusion Middleware 4-9

4.8.2 Forcing a Shutdown of Oracle Database

If you find that the Oracle Database instance is taking a long time to shut down, you can use the following commands to force an immediate shutdown: ORACLE_HOMEbinsqlplus nolog SQL connect SYS as SYSDBA SQL SHUTDOWN IMMEDIATE; An immediate database shutdown proceeds with the following conditions: ■ No new connections are allowed, nor are new transactions allowed to be started, after the statement is issued. ■ Any uncommitted transactions are rolled back. If long uncommitted transactions exist, this method of shutdown might not complete quickly, despite its name. ■ Oracle does not wait for users currently connected to the database to disconnect. Oracle implicitly rolls back active transactions and disconnects all connected users. The next startup of the database will not require any instance recovery procedures. See: Oracle Fusion Middleware High Availability Guide for information about starting and stopping in high-availability environments See Also: Oracle Database Administrators Guide in the Oracle Database 11g documentation library