Command Reference

START DATABASE MANAGER

Starts the current database manager instance background processes on a single node or on all the nodes defined in a multi-node environment.

This command is not valid on a client.

Scope

In a multi-node environment, this command affects all nodes that are listed in the $HOME/sqllib/db2nodes.cfg file, unless the nodenum parameter is used.

Authorization

One of the following:

sysadm
sysctrl
sysmaint

Note: On OS/2, no authorization is required if the ss_logon database manager configuration parameter is set to NO.

Required Connection

None

Command Syntax

>>-+-START--+-DATABASE MANAGER-+-+---+-------------------+------>
   |        +-DB MANAGER-------+ |   '-PROFILE--profile--'
   |        '-DBM--------------' |
   '-db2start--------------------'
 
>-----+--------------------------------------+-----------------><
      '-NODENUM--nodenum--| start options |--'
 
start options
 
|---+------------------------------+----------------------------|
    +-ADDNODE--| addnode options |-+
    +-STANDALONE-------------------+
    '-RESTART--| restart options |-'
 
addnode options
 
|---HOSTNAME--hostname---PORT--logical-port--------------------->
 
>-----+--------------------------+---+-----------------+-------->
      '-COMPUTER--computer-name--'   '-USER--username--'
 
>-----+---------------------+---+-------------------+----------->
      '-PASSWORD--password--'   '-NETNAME--netname--'
 
>-----+-------------------------+-------------------------------|
      +-LIKE NODE--node-number--+
      '-WITHOUT TABLESPACES-----'
 
restart options
 
|---+---------------------+---+---------------------+----------->
    '-HOSTNAME--hostname--'   '-PORT--logical-port--'
 
>-----+-------------------+-------------------------------------|
      '-NETNAME--netname--'

Command Parameters
Note: All of the following parameters are valid in an MPP environment only.

PROFILE profile

Specifies the name of the profile file to be executed at each node to define the DB2 environment. This file is executed before the nodes are started. The profile file must reside in the sqllib directory of the instance owner.

Note:

The environment variables in the profile file are not necessarily all defined in the user session.

NODENUM nodenum

Specifies the node to be started. If no other options are specified, a normal startup is done at this node.

Valid values are from 0 to 999 inclusive. If ADDNODE is not specified, the value must already exist in the db2nodes.cfg file of the instance owner. If no node number is specified, all nodes defined in the node configuration file are started.

ADDNODE

Specifies that the new node is added to the db2nodes.cfg file of the instance owner with the hostname and logical-port values.

Ensure that the combination of hostname and logical-port is unique.

The add node utility is executed internally to create all existing databases on the node being added. After a node is added, the db2nodes.cfg file is not updated with the new node until a db2stop is issued. The node is not part of the MPP system until the next db2start following the db2stop.
Note: When the database partitions are created on the new node, their configuration parameters are set to the default.

HOSTNAME hostname: With ADDNODE, specifies the host name to be added to the db2nodes.cfg file.
PORT logical-port: With ADDNODE, specifies the logical port to be added to the db2nodes.cfg file. Valid values are from 0 to 999.
COMPUTER computer-name: The computer name for the machine on which the new node is created. This parameter is mandatory on Windows NT, but is ignored on other operating systems.
USER username: The user name for the account on the new node. This parameter is mandatory on Windows NT, but is ignored on other operating systems.
PASSWORD password: The password for the account on the new node. This parameter is mandatory on Windows NT, but is ignored on other operating systems.
NETNAME netname: Specifies the netname to be added to the db2nodes.cfg file. If not specified, this parameter defaults to the value specified for hostname.
LIKE NODE node-number: Specifies that the containers for the temporary table spaces will be the same as the containers on the specified node-number for each database in the instance. The node specified must be a node that is already in the db2nodes.cfg file.
WITHOUT TABLESPACES: Specifies that containers for the temporary table spaces are not created for any of the databases. The ALTER TABLESPACE statement must be used to add temporary table space containers to each database before the database can be used.

STANDALONE

Specifies that the node is to be started in stand-alone mode. FCM does not attempt to establish a connection to any other node. This option is used when adding a node.

RESTART

Starts the database manager after a failure. Other nodes are still operating, and this node attempts to connect to the others. If neither the hostname nor the logical-port parameter is specified, the database manager is restarted using the hostname and logical-port values specified in db2nodes.cfg. If either parameter is specified, the new values are sent to the other nodes when a connection is established. The db2nodes.cfg file is updated with this information.

HOSTNAME hostname: With RESTART, specifies the host name to be used to override that in the node configuration file.
PORT logical-port: With RESTART, specifies the logical port number to be used to override that in the node configuration file. If not specified, this parameter defaults to the logical-port value that corresponds to the nodenum value in the db2nodes.cfg file. Valid values are from 0 to 999.
NETNAME netname: Specifies the netname to override that specified in the db2nodes.cfg file. If not specified, this parameter defaults to the netname value that corresponds to the nodenum value in the db2nodes.cfg file.

Examples

The following is sample output from db2start issued on a three node system with nodes 10, 20, and 30:

04-07-1997 10:33:05    10   0   SQL1063N  DB2START processing was successful.
04-07-1997 10:33:07    20   0   SQL1063N  DB2START processing was successful.
04-07-1997 10:33:07    30   0   SQL1063N  DB2START processing was successful.
SQL1063N  DB2START processing was successful.

Usage Notes

It is not necessary to issue this command on a client node. It is provided for compatibility with older clients, but it has no effect on the database manager.

Once started, the database manager instance runs until the user stops it, even if all application programs that were using it have ended.

If the database manager starts successfully, a successful completion message is sent to the standard output device. If an error occurs, processing stops, and an error message is sent to the standard output device. In a multi-node environment, messages are returned on the node that issued the START DATABASE MANAGER command.

If no parameters are specified in a multi-node database environment, the database manager is started on all parallel nodes using the parameters specified in the node configuration file.

If a START DATABASE MANAGER command is in progress, ensure that the applicable nodes have started before issuing a request to the database.

The db2cshrc file is not supported and cannot be used to define the environment.

On UNIX platforms, the START DATABASE MANAGER command supports the SIGINT and SIGALRM signals. The SIGINT signal is issued if CTRL+C is pressed. The SIGALRM signal is issued if the value specified for the start_stop_time database manager configuration parameter is reached. If either signal occurs, all in-progress startups are interrupted and a message (SQL1044N for SIGINT and SQL6037N for SIGALRM) is returned from each interrupted node to the $HOME/sqllib/log/db2start. timestamp.log error log file. Nodes that are already started are not affected. If CTRL+C is pressed on a node that is starting, db2stop must be issued on that node before an attempt is made to start it again.

On the Windows NT operating system, neither the db2start command nor the NET START command returns warnings if any communication subsystem failed to start. The database manager in a Windows NT environment is implemented as an NT service, and does not return an error if the service is started successfully. Be sure to examine the NT Event Log or the DB2DIAG.LOG file for any errors that may have occurred during the running of db2start.

See Also

ADD NODE

STOP DATABASE MANAGER.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]