Modifies individual entries in the database manager configuration file for the instance that contains the currently connected database.
SYSADM
Database
>>-UPDATE--+-DATABASE MANAGER-+--+-CONFIGURATION-+--------------> +-DB MANAGER-------+ +-CONFIG--------+ '-DBM--------------' '-CFG-----------' .--------------------------------------. V | >--USING----config-keyword--+-value------------+-+--------------> +-value--AUTOMATIC-+ +-AUTOMATIC--------+ '-MANUAL-----------' .-DEFERRED-. >--+----------+------------------------------------------------><
This is a default clause when operating in the CLPPlus interface. DEFERRED need not be called when using CLPPlus processor.
CALL SYSPROC.ADMIN_CMD('db2 update dbm cfg using DIAGLEVEL 1')
To view or print a list of the database manager configuration parameters, use the SYSIBMADM.DBMCFG administrative view. To reset the database manager configuration parameters to the recommended database manager defaults, use the RESET DATABASE MANAGER CONFIGURATION command through the ADMIN_CMD procedure. For more information about database manager configuration parameters and the values of these parameters appropriate for each type of database node configured (server, client, or server with remote clients), see individual configuration parameter descriptions.
Not all parameters can be updated.
Some changes to the database manager configuration file become effective only after they are loaded into memory. For more information on which parameters are configurable online and which ones are not, see the configuration parameter summary. Server configuration parameters that are not reset immediately are reset during execution of db2start. For a client configuration parameter, parameters are reset the next time you restart the application. If the client is the command line processor, it is necessary to invoke TERMINATE.
If an error occurs, the database manager configuration file does not change.
The database manager configuration file cannot be updated if the checksum is invalid. This can occur if you edit database manager configuration file and do not use the appropriate command. If the checksum is invalid, you must reinstall the database manager to reset the database manager configuration file.
When you update the SVCENAME, or TPNAME database manager configuration parameters for the current instance, if LDAP support is enabled and there is an LDAP server registered for this instance, the LDAP server is updated with the new value or values.
Command execution status is returned in the SQLCA resulting from the CALL statement.
Updates can only be made to the database instance that contains the connected database.
If a parameter supports dynamic update, an attempt is made to update it dynamically, even if the IMMEDIATE keyword is not specified. The authorization used is the current SYSTEM_USER id.