Configuration Considerations for All DB2 Configurations

1. DB2 instance names should contain alphanumeric characters only.

2. DB2 clients should be configured to connect to the database via a LifeKeeper protected IP address. Users can define:

DB2SYSTEM=<Floating IP>” in $instancehome/sqllib/profile.env

and catalog the floating IP address on the clients.

3. The /etc/services file for each server in your configuration protecting a DB2 resource hierarchy must have identical service entries for the protected instance. Additionally, the User ID, Group ID and instance home directory for the protected DB2 instance must be the same on all servers where the resource will be protected.

DB2 adds the following entries as default in /etc/services:

DB2_db2inst1 60000/tcp

DB2_db2inst1_1 60001/tcp

DB2_db2inst1_2 60002/tcp

DB2_db2inst1_END 60003/tcp

db2c_db2inst1 50001/tcp

4. A recovery is what takes place after DB2 is terminated abruptly, as with a system crash. Following are tips that will significantly reduce the amount of time it takes for DB2 to recover from a failure.

• Limit the log records that DB2 will process. You can accomplish this by properly configuring the SOFTMAX and LOGFILSIZ configuration parameters. You should use log files with a size of 4MB (1000 4KB pages) and keep the amount of active log space at 25% of the size of one log file (1MB):

db2 UPDATE DB CFG FOR <dbname> USING SOFTMAX 25

db2 UPDATE DB CFG FOR <dbname> USING LOGFILSIZ 1000

• Ensure that there is a sufficient number of page cleaners to accommodate your work load:

db2 UPDATE DB CFG FOR <dbname> USING NUM_IOCLEANERS <num>

5. DB2 Fault Monitor should be disabled in all servers.

6. DB2 should be installed in all servers.