Modifies individual entries in a specific database configuration file. A database configuration file resides on every database partition on which the database has been created.
Database. The database connection must be local to the instance containing the connected database.
>>-UPDATE--+-DATABASE-+--+-CONFIGURATION-+----------------------> '-DB-------' +-CONFIG--------+ '-CFG-----------' >--+---------------------+--+-----------------------+-----------> '-FOR--database-alias-' '-MEMBER--member-number-' .--------------------------------------. V | >--USING----config-keyword--+-value------------+-+--------------> +-value--AUTOMATIC-+ +-AUTOMATIC--------+ '-MANUAL-----------' .-IMMEDIATE-. >--+-----------+----------------------------------------------->< '-DEFERRED--'
This is a default clause when operating in the CLPPlus interface as well. IMMEDIATE need not be called when using CLPPlus processor.
CALL SYSPROC.ADMIN_CMD ('UPDATE DB CFG USING sortheap 1000')
Command execution status is returned in the SQLCA resulting from the CALL statement.
The database-alias must be an alias name that is defined on the server.
The command affects all database partitions unless MEMBER is specified.
To view or print a list of the database configuration parameters, use the SYSIBMADM.DBCFG administration view.
To reset all the database configuration parameters to the recommended defaults, use the RESET DATABASE CONFIGURATION command using the ADMIN_CMD procedure.
To change a database configuration parameter, use the UPDATE DATABASE CONFIGURATION command through the ADMIN_CMD procedure. For example, to change the logging mode to "archival logging" on a single-partition database environment containing a database called ZELLMART, use:
CALL SYSPROC.ADMIN_CMD ('update db cfg for zellmart using logarchmeth1 logretain')
To check that the logarchmeth1 configuration parameter has changed, use:
SELECT * FROM SYSIBMADM.DBCFG WHERE NAME='logarchmeth1'
CALL SYSPROC.ADMIN_CMD ('update db cfg for zellmart member 30 using
logarchmeth1 logretain')
For more information about DB2 database configuration parameters and the values available for each type of database node, see the individual configuration parameter descriptions. The values of these parameters differ for each type of database node configured (server, client, or server with remote clients).
Not all parameters can be updated.
Some changes to the database configuration file become effective only after they are loaded into memory. All applications must disconnect from the database before this can occur. For more information aboutwhich parameters are configurable online and which ones are not, see summary list of configuration parameters.
If an error occurs, the database configuration file does not change. The database configuration file cannot be updated if the checksum is invalid. This might occur if the database configuration file is changed without using the appropriate command. If this happens, the database must be restored to reset the database configuration file.