Using the DB2 autoconfigure command to configure database parameters

Using DB2® autoconfigure is an easy and quick way to find the initial settings for database parameters.

It calculates values for the buffer pool size, database configuration and database manager configuration parameters, with the option of suggesting or applying these recommended values.

Database administrators can use the recommended values as a basis for fine tuning the parameters.

Sample command: DB2 autoconfigure

Note: The command is split up in multiple lines for better readability. When issuing it at the command prompt, it needs to specified in one line.
db2 autoconfigure using   
   mem_percent 80   
   workload_type simple  
   num_stmts 60   
   tpm 10000   
   is_populated yes  
   num_local_apps 0     
   num_remote_apps 100  
   isolation rs  
   bp_resizeable yes  
apply db and dbm 

where:

mem_percent 80
The TradeDatabase is the only database for this DB2 instance. Set the maximum usable instance memory to 80%.
workload_type simple
Simple workloads tend to be I/O intensive and mostly transactions.
num_stmts 60
Estimated number of statements per unit of work.
tpm 10000
Expected transactions per minute.
is_populated yes
Database populated with data
num_local_apps 0
No local applications
num_remote_apps 100
Estimated number of connected remote applications
bp_resizeable yes
Buffer pools are resizeable
Note: The database server is installed on a single DASD Model 27 (approximately 20 GB capacity). A more static and smaller log file setup is chosen, than that suggested by the DB2 autoconfigure command.

Limit the database log files to 6 GB and configure no secondary log files for the benchmark application (LOGFILSIZ value is 4 KB pages):

Sample commands: DB2 command sequence for changing the database log file setup.

db2 -v “update db cfg for tradedb using LOGPRIMARY 6” 
db2 -v “update db cfg for tradedb using LOGSECOND 0” 
db2 -v “update db cfg for tradedb using LOGFILSIZ 262144”