start_stop_time - Start and stop timeout configuration parameter
This parameter specifies the time, in minutes, within which all database partition servers must respond to a START DBM or a STOP DBM command in a Db2 pureScale environment. It is also used as the timeout value during ADD DBPARTITIONNUM and DROP DBPARTITIONNUM operations.
- Configuration type
- Database manager
- Applies to
- Database server with local and remote clients
- Parameter type
- Configurable Online
- Propagation class
- Immediate
- Default [range]
- 10 [1 - 1 440]
- Unit of measure
- Minutes
Member or nodes that do not respond to db2start or db2stop commands within the specified time will be killed and cleaned up automatically by db2start or db2stop in a multi member/node instance. The diagnostic messages are logged into the diagpath defined in the database manager configuration or at its default value (for example, sqllib/db2dump/ $m on UNIX operating systems).
If a db2start or db2stop operation is not completed within the value specified by the start_stop_time database manager configuration parameter, the database members and partitions being stopped will be killed and cleaned up automatically. Environments with a low value for start_stop_time may experience this behavior. To resolve this behavior, increase the value of start_stop_time.
When adding a new database partition using one of the db2start, START DATABASE MANAGER, or ADD DBPARTITIONNUM commands, the add database partition operation must determine whether or not each database in the instance is enabled for automatic storage. This is done by communicating with the catalog partition for each database. If automatic storage is enabled, the storage path definitions are retrieved as part of that communication. Likewise, if system temporary table spaces are to be created with the database partition(s), the operation might have to communicate with another database partition server to retrieve the table space definitions for the database partition(s) that reside on that server. These factors should be considered when determining the value of the start_stop_time parameter.
To allow the force application operation more time to succeed, for example to rollback a large batch transaction, increase start_stop_time. If the timeout is configured to be too low or if the member/partition(s) is in a state that cannot be successfully forced, the member/partition(s) will be killed and possibly in need of crash recovery. db2start needs to be run before the crash recovery can occur and release any retained locks, then db2stop to stop the member/partition(s) cleanly.
rsh or ssh.