I have already try to change it manually but DB2 auto rewrite the shmmax value I have try to start db2 and after set the shmmax, but they still crash with same error.
Perhaps it's a bug of the db2 v9.5 fixpack 0 of ibm soft because older version work fine without anything to do. They is a way to tell to db2 to don't change this value himself ? Chris Bannister a écrit : > On Tue, Mar 25, 2008 at 09:51:23AM +0100, Strong Cypher wrote: > >> Hi, >> >> Thanks for answer >> >> So here all collection I can do to find the problem : >> >> Yeah there is some difference ... perhaps I could try to copy the kernel >> config of redhat on a debian with the same version of kernel and see ... I >> will try that >> > > Maybe, but see below. > > >> So here the DB2 log >> > [..] > >> MESSAGE : ZRC=0x850F0005=-2062614523=SQLO_NOSEG >> "No Storage Available for allocation" >> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >> DIA8305C Memory allocation failure occurred. >> DATA #1 : <preformatted> >> Unable to attach 3 segments totalling 566165504 bytes starting at address >> 0x00000000. One possible cause may be an improper setting for the >> shmmax Linux kernel tuneable. >> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Here is your clue, right there. > > >> ... So the problem appear during the installation process ... I have never >> see that on the redhat system >> > > compare: > > cat /proc/sys/kernel/shmmax > > on the Debian system with the redhat system. > > To alter the setting, e.g.: > > echo 1000000000 > /proc/sys/kernel/shmmax > > will allow a segment up to one billion bytes. > > The error (from above): > > Unable to attach 3 segments totalling 566165504 bytes > > will help determine the value. > > If you reboot your computer, you will lose that setting so you will have > to put it in a local init script. > >
signature.asc
Description: OpenPGP digital signature
