DB2 - Problem description
Problem IC68082 | Status: Closed |
SLOW RESTORE INTO A NEW DATABASE ON AIX DUE TO HAVING ONLY 3 PREFETCHERS STARTED. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
When a restore is done on AIX into a new database, by default only 3 prefetcher processes are started, causing slow restore. This does not happen when the restore is on existing database, when NUM_IOSERVERS parameter is set to a higher value. And when restoring into a new database, there are no means to set NUM_IOSERVERS database configuration parameter. This does not happen on Linux where by default 255 prefetcher processes are started. The workaround to this issue is to create a dummy database, update NUM_IOSERVERS to a higher value (ex: 20), then do a restore. This will cause equal number of prefetcher processes start as it is defined by NUM_IOSERVERS parameter. | |
Problem Summary: | |
SLOW RESTORE INTO A NEW DATABASE ON AIX DUE TO HAVING ONLY 3 PREFETCHERS STARTED. | |
Local Fix: | |
1. Create a dummy database 2. Update NUM_IOSERVERS to a higher values (20 is a good starting point): db2 connect to <db_name> db2 update db cfg using NUM_IOSERVERS 20 3. Start a restore. | |
available fix packs: | |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
LOCAL FIX: 1. Create a dummy database 2. Update NUM_IOSERVERS to a higher values (20 is a good starting point): db2 connect to <db_name> db2 update db cfg using NUM_IOSERVERS 20 3. Start a restore. Fixed in DB2 V98FP3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.04.2010 23.12.2010 23.12.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.8.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.8.0.3 |