Environment : DB2 LUW V.9.7.5 Red Hat Linux 5.7
Disk allocation for the containers for DB2 redirect restore is very slow in my LINUX Dev box.Is there any Linux kernal parameter that improves the speed of disk allocation for DB2 redirect restore?.
DB Size is about 60GB.
Backup takes about 40mins but redirect restores takes close to 4 hours time. Writing to containers only starts alomst after 3hours ,after first RESTORE Command
Note that,UTIL_HEAP_SZ is sized properly .Also DB has 15+ tablespaces to distribute the storage equally to speed up the backups and restores.
Restore Script:
CONNECT TO DBNAME1 ;
QUIESCE DATABASE immediate force connections;
UNQUIESCE DATABASE;
connect reset;
deactivate db DBNAME1;
list applications for DB DBNAME1;
RESTORE DATABASE PRODDB FROM /databases2/01_restore ON /path1/DBNAME1 ,/path2/DBNAME1,/path3/DBNAME1 DBPATH on /path1/DBNAME1 INTO DBNAME1 REPLACE EXISTING REDIRECT without rolling forward WITHOUT PROMPTING;
RESTORE DATABASE PRODDB CONTINUE;
UPDATE DB CFG FOR DBNAME1 USING logarchmeth1 OFF logarchmeth2 OFF logprimary 3 logsecond 29 logfilsiz 8192 softmax 300 immediate;
activate db DBNAME1;
connect to DBNAME1;
connect reset;
Disk allocation for the containers for DB2 redirect restore is very slow in my LINUX Dev box.Is there any Linux kernal parameter that improves the speed of disk allocation for DB2 redirect restore?.
DB Size is about 60GB.
Backup takes about 40mins but redirect restores takes close to 4 hours time. Writing to containers only starts alomst after 3hours ,after first RESTORE Command
Note that,UTIL_HEAP_SZ is sized properly .Also DB has 15+ tablespaces to distribute the storage equally to speed up the backups and restores.
Restore Script:
CONNECT TO DBNAME1 ;
QUIESCE DATABASE immediate force connections;
UNQUIESCE DATABASE;
connect reset;
deactivate db DBNAME1;
list applications for DB DBNAME1;
RESTORE DATABASE PRODDB FROM /databases2/01_restore ON /path1/DBNAME1 ,/path2/DBNAME1,/path3/DBNAME1 DBPATH on /path1/DBNAME1 INTO DBNAME1 REPLACE EXISTING REDIRECT without rolling forward WITHOUT PROMPTING;
RESTORE DATABASE PRODDB CONTINUE;
UPDATE DB CFG FOR DBNAME1 USING logarchmeth1 OFF logarchmeth2 OFF logprimary 3 logsecond 29 logfilsiz 8192 softmax 300 immediate;
activate db DBNAME1;
connect to DBNAME1;
connect reset;