You can stop and start the deployed instance from the workload
console. You can also stop and start individual virtual machines in
the pattern.
To stop a running deployed instance:
- Select and select the instance from the Virtual
System Instances list.
- Click the Stop icon in the instance title
bar.
To start a stopped deployed instance:
- Select and select the instance from the Virtual
System Instances list.
- Click the Start icon in the instance title
bar.
Note: A known defect in DB2® 10.1.0.2 results in the DB2
processes not always restarting when the instance stops and restarts. In this case, you must start
DB2 process manually, by logging into the DB2 node as db2inst1 and running
db2start. You might also need to restart the WSRR processes on the WSRR
nodes.
To stop individual virtual machines.
- Expand the Virtual Machines section of
the instance view.
- Select the Manage link for the machine
that you want to stop.
- Click the stop icon in the manage bar.
To start individual virtual machines.
- Expand the Virtual Machines section of
the instance view.
- Select the Manage link for the machine that you want to start.
- Click the start icon in the manage bar.
You can also stop and start WSRR and DB2 from
the command line. Click the Login link to connect
by using the SSH console.
You stop and start WSRR by stopping and starting the WebSphere® Application Server profile. See Managing profiles using commands in the WebSphere Application Server Information Center.
In the Advanced Pattern, after the DMGR and Custom Nodes are restarted, the WSRR cluster needs
starting. To do this, open the WebSphere Application Server administrative console and select . Select WSRRCluster_1, then click
Start.
You can stop and start DB2 by
using system commands. See System Commands in the DB2 Information Center.