Resets the configuration of a specific database to the system defaults.
This command updates all members by default, except when MEMBER is specified to reset only one member.
Instance. An explicit attachment is not required. If the database is listed as remote, an instance attachment to the remote node is established for the duration of the command.
>>-RESET--+-DATABASE-+--+-CONFIGURATION-+-----------------------> '-DB-------' +-CONFIG--------+ '-CFG-----------' >--FOR--database-alias--+-----------------------+-------------->< '-MEMBER--member-number-'
Reset the database configuration on a multi-partition instance
10 gilera 0
20 gilera 1
30 motobi 0
40 motobi 1
The user has created the SAMPLE database on the instance. The catalog partition for SAMPLE is on database partition number 10. Let's assume the user is logged on to system motobi.
db2 reset db cfg for sample
db2 reset db cfg for sample dbpartitionnum 30
export DB2NODE=30
db2 reset db cfg for sample
To view or print a list of the database configuration parameters, use the GET DATABASE CONFIGURATION command.
To change the value of a configurable parameter, use the UPDATE DATABASE CONFIGURATION command.
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.
If an error occurs, the database configuration file does not change.
The database configuration file cannot be reset 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.
The RESET DATABASE CONFIGURATION command will reset the database configuration parameters to the documented default configuration values, where auto_runstats will be ON. Self_tuning_mem will be reset to ON on non-partitioned database environments and to OFF on partitioned database environments.
The RESET DATABASE CONFIGURATION command does not change the database configuration parameters ENCRLIB and ENCROPTS. The RESET DATABASE CONFIGURATION command is not done through a database connection, so DB2 is not able to determine whether a user holds SECADM authority.