db2start - Start DB2 command

db2start can be executed as a system command or a CLP command.

Start DB2 at the server before connecting to a database, precompiling an application, or binding a package to a database.

The db2start command launches the DB2 database product installation as a Windows service. The DB2 database product installation on Windows can still be run as a process by specifying the /D switch when invoking db2start. The DB2 database product installation can also be started as a service using the Control Panel or the NET START command.

Since db2start launches a Windows service, you must meet Windows 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.

If a db2start operation in a multi-partition database is not completed within the value specified by the start_stop_time database manager configuration parameter, the database partitions that have timed out will not have the database manager instance background processes started (all resources associated with the database partition will be removed). Environments with many database partitions with a low value for start_stop_timeout might experience this behavior. To resolve this behavior, increase the value of start_stop_time database manager configuration parameter.

For root-install DB2 copies on Linux and UNIX operating systems, the db2start command sets the ulimit value required by the database manager without changing the permanent setting of ulimit for the instance owner ID.

For non-root install, you should set the ulimit for 'data' to 'unlimited' and 'nofiles' to 'unlimited' or the maximum value allowed on the system.