Starts the current database manager instance background processes on a single database partition or on all the database partitions defined in a multi-partitioned database environment.
This command is not valid on a client.
In a multi-partitioned database environment, this command affects all database partitions that are listed in the $HOME/sqllib/db2nodes.cfg file, unless the DBPARTITIONNUM parameter is used.
The ADD DBPARTITIONNUM start option requires either sysadm or sysctrl authority.
You must meet Windows operating system requirements for starting a service. If Extended Security is disabled, you must be a member of the Administrators, Server Operators or Power Users group. If Extended Security is enabled, you must be a member of either the Administrators group or the DB2ADMNS group to start the database.
None
>>-+-START--+-DATABASE MANAGER-+-+------------------------------> | +-DB MANAGER-------+ | | '-DBM--------------' | '-db2start--+----+------------' '-/D-' >--+--------------------------------------------------------+---> '-REMOTE--+----------+--instancename--| remote options |-' '-INSTANCE-' >--+---------------------------------------------------------+--> '-ADMIN MODE--+------------------+--+-------------------+-' +-USER--username---+ '-RESTRICTED ACCESS-' '-GROUP--groupname-' >--+------------------+-----------------------------------------> '-PROFILE--profile-' >--+--------------------------------------------------------+-->< '-DBPARTITIONNUM--db-partition-number--| start options |-' remote options |--+-ADMINNODE--nodename-+--USER--username--USING--password-----| '-HOSTNAME--hostname--' start options |--+----------------------------------------------------+-------| +-ADD DBPARTITIONNUM--| add dbpartitionnum options |-+ +-STANDALONE-----------------------------------------+ '-RESTART--| restart options |-----------------------' add dbpartitionnum options |--HOSTNAME--hostname--PORT--logical-port-----------------------> >--+-------------------------+--+----------------+--------------> '-COMPUTER--computer-name-' '-USER--username-' >--+--------------------+--+------------------+-----------------> '-PASSWORD--password-' '-NETNAME--netname-' >--+------------------------------------------+-----------------| +-LIKE DBPARTITIONNUM--db-partition-number-+ '-WITHOUT TABLESPACES----------------------' restart options |--+--------------------+--+--------------------+---------------> '-HOSTNAME--hostname-' '-PORT--logical-port-' >--+------------------------+--+----------------+---------------> '-COMPUTER--computername-' '-USER--username-' >--+--------------------+--+------------------+-----------------| '-PASSWORD--password-' '-NETNAME--netname-'
If the ADMIN MODE option is specified alone, the databases within the quiesced instance will be activated to do authorization checking for all connect attempts to the database. This is necessary to determine if the connecting user ID has dbadm authority; this authority is stored in the database catalog and the database must be activated to determine if the user ID has it. To prevent this authorization checking from happening, specify the RESTRICTED ACCESS option.
All of the following parameters are valid in an Enterprise Server Edition (ESE) environment only.
Valid values are from 0 to 999 inclusive. If ADD DBPARTITIONNUM is not specified, the value must already exist in the db2nodes.cfg file of the instance owner. If no database partition number is specified, all database partitions defined in the configuration file are started.
Ensure that the combination of hostname and logical-port is unique.
The add database partition server utility is executed internally to create all existing databases on the database server partition being added. The new database partition server is automatically added to the db2nodes.cfg file.
If the ADD request is made in an environment that has two or more active database partition servers, the new database partition server is visible to the environment when the ADD processing completes.
If the ADD request is made in an environment that has one database partition server and it is active, after ADD processing completes, the new database partition server is inactive. The instance must be restarted by using db2stop and db2start before the new database partition server can participate in the partitioned database environment. If the ADD request is made in an environment that has one database partition server and it is inactive, after ADD processing completes, the new database partition server (or servers, if more than one is added) is active. Only the original database partition server needs to be started.
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.
On Microsoft Windows Vista or later versions, when using an id that has local or domain administrator authority, you must execute this command from a DB2 command window running with full administrator privileges.
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 partitioned database environment, messages are returned on the database partition that issued the START DATABASE MANAGER command.
If no parameters are specified in a partitioned database environment, the database manager is started on all parallel nodes using the parameters specified in the database partition configuration file.
If a START DATABASE MANAGER command is in progress, ensure that the applicable database partitions have started before issuing a request to the database.
The db2cshrc file is not supported and cannot be used to define the environment.
You can start an instance in a quiesced state. You can do this by using one of the following choices:
db2start admin mode
or
db2start admin mode user username
or
db2start admin mode group groupname
The RESTRICTED ACCESS option will prevent the databases within the quiesced instance from being activated to do authorization checking. Any user ID trying to connect to a database, which has dbadm authority or quiesce_connect privilege on the database, will not be allowed to connect. Only user IDs which have sysadm, sysctrl, or sysmaint authority and the user or group specified with the command will be allowed to connect to the database.
The RESTRICTED ACCESS option should be used when there is a need to have exclusive connections to a database within the quiesced instance. Such cases can include making an offline backup or performing other maintenance activities.
When adding a new database partition server, START DATABASE MANAGER 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 then the storage path definitions are retrieved as part of that communication. Likewise, if system temporary table spaces are to be created with the database partitions, START DATABASE MANAGER might have to communicate with another database partition server to retrieve the table space definitions for the database partitions that reside on that server. The start_stop_time database manager configuration parameter is used to specify the time, in minutes, by which the other database partition server must respond with the automatic storage and table space definitions. If this time is exceeded, the command fails. If this situation occurs, increase the value of start_stop_time, and reissue the command.
On UNIX platforms, the START DATABASE MANAGER command supports the SIGINT signal. It is issued if CTRL+C is pressed. If this signal occurs, all in-progress startups are interrupted and a message (SQL1044N) is returned from each interrupted database partition to the $HOME/sqllib/log/db2start. timestamp.log error log file. Database partitions that are already started are not affected. If CTRL+C is pressed on a database partition that is starting, db2stop must be issued on that database partition before an attempt is made to start it again.
On Windows operating systems, neither the db2start command nor the NET START command returns warnings if any communication subsystem failed to start. The database manager in a Windows environment is implemented as a service, and does not return an error if the service is started successfully. Be sure to examine the Event Log or the db2diag log file for any errors that might have occurred during the running of db2start.