Ok in fact what I have saw is this First, db2 start with 256m share memory ... So it's ok, they are be able to do it on both system Second, they try to change by following the memory of the system On redhat, it's ok On debian, they don't do it properly Perhaps it set a too high value I have try the express version, so no support for that I think I could try to ask I'm waiting for a new version of db2 I will see if the problem persist Thanks for support Chris Bannister a écrit : > On Wed, Mar 26, 2008 at 09:46:19AM +0100, cypherstrong wrote: > >> I have already try to change it manually but DB2 auto rewrite the shmmax >> value >> > > Even in redhat? But it works in redhat? > > >> I have try to start db2 and after set the shmmax, but they still crash >> with same error. >> > > Annoying. > > >> Perhaps it's a bug of the db2 v9.5 fixpack 0 of ibm soft because older >> version work fine without anything to do. >> > > Presuming you paid for this software, what does support have to say? > > >> They is a way to tell to db2 to don't change this value himself ? >> > > I don't know about db2. I use postgreSQL and it works out of the box. > >
Attachment:
signature.asc
Description: OpenPGP digital signature