Prev: OSERR : 5 "Access is denied."
Next: Reorgchk, Reorg, Runstats not having any effect after completion. Why is this?
From: Mark A on 22 Apr 2008 19:00 <dcruncher4(a)aim.com> wrote in message news:fukoc902976(a)drn.newsguy.com... > I recreated the database with all default settings and changed only > the DB2_USE_ALTERNATE_PAGE_CLEANING=ON . > > I inserted 2 million rows in 2 threads parallely. Only 4 times it > spewed out the error and only those 4 rows failed to insert. > > Thanks Mark and Serge. Ian mentioned in this thread that the bufferpool you created is too large for the available real memory on your database server, and that is the source of your problem. The bufferpool BP1 did not get allocated because of memory limitations and the DB2 hidden (very small) 8K bufferpool was used instead. This is the real source of your problem (although the other recommendations will help speed things up). If you do the following, it will probably fix your problem permanently: db2 alter bufferpool bp1 size 30000; Then (just to be safe): db2stop db2start
From: ajstorm on 23 Apr 2008 09:12
On Apr 22, 7:00 pm, "Mark A" <nob...(a)nowhere.com> wrote: > <dcrunch...(a)aim.com> wrote in messagenews:fukoc902976(a)drn.newsguy.com... > > I recreated the database with all default settings and changed only > > the DB2_USE_ALTERNATE_PAGE_CLEANING=ON . > > > I inserted 2 million rows in 2 threads parallely. Only 4 times it > > spewed out the error and only those 4 rows failed to insert. > > > Thanks Mark and Serge. > > Ian mentioned in this thread that the bufferpool you created is too large > for the available real memory on your database server, and that is the > source of your problem. The bufferpool BP1 did not get allocated because of > memory limitations and the DB2 hidden (very small) 8K bufferpool was used > instead. This is the real source of your problem (although the other > recommendations will help speed things up). > > If you do the following, it will probably fix your problem permanently: > > db2 alter bufferpool bp1 size 30000; > > Then (just to be safe): > > db2stop > db2start Another option, of course, would be to enable self tuning memory for your system. Not sure if this is something that you've considered. To do that, issue the following: db2 connect to test db2 update db cfg using SELF_TUNING_MEM ON DATABASE_MEMORY AUTOMATIC db2 alter bufferpool bp1 size AUTOMATIC Once this is done, you should no longer see any use of the hidden buffer pools. Thanks, Adam |