Database configuration file

A database configuration file is created for each database. This file is called SQLDBCON prior to Version 8.2, and SQLDBCONF in Version 8.2 and later. The creation of this file is done for you.

This file contains values for various configuration parameters that affect the use of the database, such as:
  • Parameters specified or used when creating the database (for example, database code page, collating sequence, Db2® database release level)
  • Parameters indicating the current state of the database (for example, backup pending flag, database consistency flag, rollforward pending flag)
  • Parameters defining the amount of system resources that the operation of the database might use (for example, buffer pool size, database logging, sort memory size).
Note: If you edit the db2system, SQLDBCON (prior to Version 8.2), or SQLDBCONF (Version 8.2 and later) file using a method other than those provided by the Db2 database manager, you might make the database unusable. Therefore, do not change these files using methods other than those documented and supported by the database manager.

Performance Tip: Many of the configuration parameters come with default values, but might need to be updated to achieve optimal performance for your database. By default, the Configuration Advisor is invoked as part of the CREATE DATABASE command so that the initial values for some parameters are already configured for your environment.

For multi-partition databases: When you have a database that is distributed across more than one database partition, the configuration file should be the same on all database partitions. Consistency is required since the query compiler compiles distributed SQL statements based on information in the local node configuration file and creates an access plan to satisfy the needs of the SQL statement. Maintaining different configuration files on database partitions could lead to different access plans, depending on which database partition the statement is prepared.