Hi Alpesh,
um,... aaaah,... yes, I see, 1.5TB is quiet big. I wouldn't like to have to move that, too.
So, I guess you're working with DB2 on z/OS? I'm not familiar with that one (yet). But with my DB2 on Linux I'd try another approach, consisting of
* playing with commit count,
* increasing the bufferpool,
* increasing size and number of logs,
* spread the logs over different disks.
Don't know the structure of the data within the table, but primary keys and/or indexes and a select based on such a column should help significantely. (Once had a mass-insert based on a bigger, joined select; interupted it after 24 hours. Added an index and it was done in 15 minutes !!)
Regards,
Bernd
|