Restarting Administration Server Scenarios

Avoiding and Recovering From Server Failure 4-5

4.4 Restarting a Failed Administration Server

The following sections describe how to start an Administration Server after a failure.

4.4.1 Restarting an Administration Server

See Chapter 2, Starting and Stopping Servers.

4.4.1.1 Restarting Administration Server Scenarios

Table 4–1 WebLogic Server Exit Codes Exit Code Value Meaning Restart Recommendation Less than 0 A negative value indicates that the server instance failed during a state transition, and did not terminate in a stable condition. Example: If a Start in Standby command is issued for a server instance whose configuration is invalid, the server instance fails in the transitional STARTING state, and does not achieve the STANDBY state. Do not attempt to restart the server. Diagnose the problem that caused the server process to exit. Indicates that the server process terminated normally, as a result of a shutdown command, either graceful or forced. None. Greater than 0 A positive value indicates that the server instance stopped itself after determining that one or more of its subsystems were unstable. Example: A server instance detects an out of memory condition or stuck threads, and shuts itself down. The server instance can be restarted. Note: You can use Node Manager to automatically restart a failed Administration Server. For more information see Restart Administration and Managed Servers in Node Manager Overview in the Node Manager Administrators Guide for Oracle WebLogic Server. Table 4–2 Administration Server Restart Scenarios Listen Address Definition Same Machine or Different Machine with Same IP Address Different Machine with Different IP Address Not defined 1. If you are starting AS on a different machine with the same IP address: a. Install WebLogic Server. b. Move data. 2. Start the Administration Server. Running MSs will reconnect automatically at the next AdminReconnectIntervalS ecs . 3. To start an MS that was not running when AS failed, no change in command is required. 1. Install WebLogic Server. 2. Move data. 3. Start the Administration Server. MSs that were running when AS went down, will not reconnect because they know only the previous Administration Server URL. See Section 4.4.1.3, Managed Servers and the Re-started Administration Server. Restart MSs supplying the new AS listen address on the command line. 4. To start an MS that was not running when AS failed, supply the new AS listen address on the command line. 4-6 Managing Server Startup and Shutdown for Oracle WebLogic Server

4.4.1.2 Restarting an Administration Server on Another Machine