When you stop applications that use extender services, the server remains active until you explicitly stop it, or until the server machine recycles. You can stop all the extender servers by entering the DMBSTOP command from the server machine on the command line for the operating system.
To stop and restart extender services from the client, run the STOP SERVER and START SERVER commands from the db2ext command line. These commands stop and start extender services for the current database.
EEE Only: In a partitioned database environment, DMBSTART can be used to start either all database partition servers defined for the instance, or a single database partition server only. DMBSTART without any parameters will start all database partition servers. If you want to start one database partition server only, you do so by specifying in the command the node you want to start, as shown below:
dmbstart nodenum 2
Once you have started the server at a particular node, you must reconnect that server to the database. Use the extender command RECONNECT SERVER, as shown below:
reconnect server at nodenum 2
EEE Only: If you are using DB2 extenders in a partitioned database environment, DMBSTOP without any parameters will stop all database partition servers that are defined for the instance. If you want to stop one database partition server only, you must first disconnect that server from the database. Use the extenders command DISCONNECT SERVER, as shown below:
disconnect server at nodenum 2
You can then run DMBSTOP, specifying in the command the node you want to stop. The example below shows what you would enter from the command line of the server to stop extender services at node number 2.
dmbstop nodenum 2
EEE Only: Do not run DMBSTOP at a specific node unless your database is running in maintenance mode. In addition, you need to make sure that no extender activities will be triggered on this node while it is turned off. Otherwise, you may encounter unexpected behavior.