Re: IBM DB2 V9.5 32 bits failed to allocate share memory
Debian and redhat sets on kernel config are slightly different. But with the same config (just config from redhat) on a debian custom kernel, nothing change. so ... It's definitivly not a debian issue. Thanks for support Chris Bannister a écrit : On Thu, Apr 03, 2008 at 11:54:53AM +0200, cypherstrong wrote: Ok After well testing on both system ... I have found that DB2 V9.5 FixPack 0 doesn't work on 32 bits system properly Redhat sets automatically some sysctl value after installation: kernel.shmmax So that's why db2 don't crash I have do the same tuning on debian, and now installation work but ... performance is awfull !!! Even system doesn't say that they is some issues in memory, it seems db2 has a problem on 32bits system... So I have try v8.2 version, and speed is wonderfull with same tuneage of memory I do this : kernel.sem = 256 256000 100 1024 kernel.shmmax=256M (in octet so) kernel.shmall=3.7G So speed is excellent with older version of db2 but not this version, even in redhat or debian I have post on db2 my issue, but it seems that nobody use this version yet on net ... I can't download v9.1fixpack4 anymore on db2 (link is really well hide on they site) So I'm stuck for this system We will need to move to a 64 bits system to solve the problem a fixpack 1 should be good now thanks for support No problem. Seems like its not a Debian problem then. But I would check the kernel configs for differences. signature.asc Description: OpenPGP digital signature
Re: IBM DB2 V9.5 32 bits failed to allocate share memory
On Thu, Apr 03, 2008 at 11:54:53AM +0200, cypherstrong wrote: Ok After well testing on both system ... I have found that DB2 V9.5 FixPack 0 doesn't work on 32 bits system properly Redhat sets automatically some sysctl value after installation: kernel.shmmax So that's why db2 don't crash I have do the same tuning on debian, and now installation work but ... performance is awfull !!! Even system doesn't say that they is some issues in memory, it seems db2 has a problem on 32bits system... So I have try v8.2 version, and speed is wonderfull with same tuneage of memory I do this : kernel.sem = 256 256000 100 1024 kernel.shmmax=256M (in octet so) kernel.shmall=3.7G So speed is excellent with older version of db2 but not this version, even in redhat or debian I have post on db2 my issue, but it seems that nobody use this version yet on net ... I can't download v9.1fixpack4 anymore on db2 (link is really well hide on they site) So I'm stuck for this system We will need to move to a 64 bits system to solve the problem a fixpack 1 should be good now thanks for support No problem. Seems like its not a Debian problem then. But I would check the kernel configs for differences. -- Chris. == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: IBM DB2 V9.5 32 bits failed to allocate share memory
Ok After well testing on both system ... I have found that DB2 V9.5 FixPack 0 doesn't work on 32 bits system properly Redhat sets automatically some sysctl value after installation: kernel.shmmax So that's why db2 don't crash I have do the same tuning on debian, and now installation work but ... performance is awfull !!! Even system doesn't say that they is some issues in memory, it seems db2 has a problem on 32bits system... So I have try v8.2 version, and speed is wonderfull with same tuneage of memory I do this : kernel.sem = 256 256000 100 1024 kernel.shmmax=256M (in octet so) kernel.shmall=3.7G So speed is excellent with older version of db2 but not this version, even in redhat or debian I have post on db2 my issue, but it seems that nobody use this version yet on net ... I can't download v9.1fixpack4 anymore on db2 (link is really well hide on they site) So I'm stuck for this system We will need to move to a 64 bits system to solve the problem a fixpack 1 should be good now thanks for support Chris Bannister a écrit : On Mon, Mar 31, 2008 at 05:22:13PM +0200, cypherstrong wrote: 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 Sounds like Redhat + the db2 guys are hand in glove. Does a search on google with, e.g, db2 Debian, as the search terms bring up any thing interesting, or even db2 linux Or probably even better: db2 linux shmmax :-) 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 No problem, hopefully you at least can sleep a little better. :-) signature.asc Description: OpenPGP digital signature
Re: IBM DB2 V9.5 32 bits failed to allocate share memory
On Mon, Mar 31, 2008 at 05:22:13PM +0200, cypherstrong wrote: 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 Sounds like Redhat + the db2 guys are hand in glove. Does a search on google with, e.g, db2 Debian, as the search terms bring up any thing interesting, or even db2 linux Or probably even better: db2 linux shmmax :-) 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 No problem, hopefully you at least can sleep a little better. :-) -- Chris. == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: IBM DB2 V9.5 32 bits failed to allocate share memory
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. signature.asc Description: OpenPGP digital signature
Re: IBM DB2 V9.5 32 bits failed to allocate share memory
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. -- Chris. == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: IBM DB2 V9.5 32 bits failed to allocate share memory
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 0x. 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 10 /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
Re: IBM DB2 V9.5 32 bits failed to allocate share memory
Hi, Thanks for answer So here all collection I can do to find the problem : The redhat is a Redhat Enterprise 5 with 2.6.18-53.el5 kernel version Here the firmware part : # # Firmware Drivers # CONFIG_EDD=m CONFIG_EFI_VARS=y CONFIG_DELL_RBU=m CONFIG_DCDBAS=m # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_PAGE_OFFSET=0xC000 CONFIG_HIGHMEM=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPLIT_PTLOCK_CPUS=4096 CONFIG_RESOURCES_64BIT=y CONFIG_HIGHPTE=y # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y CONFIG_EFI=y # CONFIG_IRQBALANCE is not set CONFIG_BOOT_IOREMAP=y CONFIG_REGPARM=y # CONFIG_SECCOMP is not set # CONFIG_VGA_NOPROBE is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set CONFIG_HZ_1000=y CONFIG_HZ=1000 CONFIG_KEXEC=y CONFIG_CRASH_DUMP=y CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x40 CONFIG_HOTPLUG_CPU=y # CONFIG_COMPAT_VDSO is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y The 64 bits resources appear, but I don't think it's the problem So now the debian: It's a debian etch with 2.6.18-6-686 kernel Here the firmware part : # # Firmware Drivers # CONFIG_EDD=m CONFIG_EFI_VARS=m CONFIG_DELL_RBU=m CONFIG_DCDBAS=m # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_PAGE_OFFSET=0xC000 CONFIG_HIGHMEM=y CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_SPARSEMEM_STATIC=y CONFIG_SPLIT_PTLOCK_CPUS=4 # CONFIG_RESOURCES_64BIT is not set # CONFIG_HIGHPTE is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y CONFIG_EFI=y CONFIG_IRQBALANCE=y CONFIG_BOOT_IOREMAP=y CONFIG_REGPARM=y # CONFIG_SECCOMP is not set # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_1000 is not set CONFIG_HZ=250 CONFIG_KEXEC=y # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x10 CONFIG_HOTPLUG_CPU=y CONFIG_COMPAT_VDSO=y CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y 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 So here the DB2 log 2008-03-21-15.56.01.630547+060 E9166G1188 LEVEL: Event PID : 32282TID : 2986575552 PROC : db2star2 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911 MESSAGE : ADM7513W Database manager has started. START : DB2 DBM DATA #1 : Build Level, 128 bytes Instance db2inst1 uses 32 bits and DB2 code release SQL09050 with level identifier 03010107. Informational tokens are DB2 v9.5.0.0, s071001, LINUXIA3295, Fix Pack 0. DATA #2 : System Info, 436 bytes System: Linux test 6 2 i686 CPU: total:2 online:2 Cores per socket:1 Threading degree per core:2 Physical Memory(MB): total:2029 free:702 Virtual Memory(MB): total:6125 free:4798 Swap Memory(MB): total:4096 free:4096 Kernel Params: msgMaxMessageSize:65535 msgMsgMap:65536 msgMaxQueueIDs:1024 msgNumberOfHeaders:65536 msgMaxQueueSize:65536 msgMaxSegmentSize:16 shmMax:268435456 shmMin:1 shmIDs:4096 shmSegments:4096 semMap:32000 semIDs:1024 semNum:32000 semUndo:32000 semNumPerID:250 semOps:32 semUndoSize:20 semMaxVal:32767 semAdjustOnExit:32767 2008-03-21-15.56.03.475024+060 I10355G477 LEVEL: Event PID : 32295TID : 2977950624 PROC : db2sysc INSTANCE: db2inst1 NODE : 000 APPHDL : 0-7 APPID: *LOCAL.db2inst1.080321145603 AUTHID : DB2INST1 EDUID : 18 EDUNAME: db2agent (instance) FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20 CHANGE : CFG DB TOOLSDB : Database_memory From: 20 automatic To: 20416 automatic 2008-03-21-15.56.47.131581+060 E10833G462 LEVEL: Event PID : 32295TID : 2967464864 PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : TOOLSDB APPHDL : 0-10 APPID: *LOCAL.DB2.080321145647 AUTHID : DB2INST1 EDUID : 41 EDUNAME: db2stmm (TOOLSDB) FUNCTION: DB2 UDB, Self tuning memory manager, stmmLog, probe:1008 DATA #1 : preformatted Starting STMM log from file number 0 2008-03-21-15.56.47.132190+060 E11296G528 LEVEL: Event PID : 32295TID : 2967464864 PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : TOOLSDB APPHDL : 0-10 APPID: *LOCAL.DB2.080321145647 AUTHID : DB2INST1 EDUID : 41 EDUNAME: db2stmm (TOOLSDB) FUNCTION: DB2 UDB, Self tuning memory manager, stmmLogGetFileStats, probe:565 DATA #1 : preformatted New STMM
Re: IBM DB2 V9.5 32 bits failed to allocate share memory
Ok with the same kernel option set in a debian kernel like this : apt-get source linux-image-`uname -r` cp -r linux-`uname -r` linux-`echo $REDHAT_VERSION` ln -s linux-`echo $REDHAT_VERSION` linux cd linux cp ~/config-`echo $REDHAT_VERSION` .config echo | make oldconfig make -kpkg --initrd kernel_image So nothing change I have disabled completly selinux (it was in alert mode only), nothing change See anything else ? Strong Cypher a écrit : Hi, Thanks for answer So here all collection I can do to find the problem : The redhat is a Redhat Enterprise 5 with 2.6.18-53.el5 kernel version Here the firmware part : # # Firmware Drivers # CONFIG_EDD=m CONFIG_EFI_VARS=y CONFIG_DELL_RBU=m CONFIG_DCDBAS=m # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_PAGE_OFFSET=0xC000 CONFIG_HIGHMEM=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPLIT_PTLOCK_CPUS=4096 CONFIG_RESOURCES_64BIT=y CONFIG_HIGHPTE=y # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y CONFIG_EFI=y # CONFIG_IRQBALANCE is not set CONFIG_BOOT_IOREMAP=y CONFIG_REGPARM=y # CONFIG_SECCOMP is not set # CONFIG_VGA_NOPROBE is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set CONFIG_HZ_1000=y CONFIG_HZ=1000 CONFIG_KEXEC=y CONFIG_CRASH_DUMP=y CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x40 CONFIG_HOTPLUG_CPU=y # CONFIG_COMPAT_VDSO is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y The 64 bits resources appear, but I don't think it's the problem So now the debian: It's a debian etch with 2.6.18-6-686 kernel Here the firmware part : # # Firmware Drivers # CONFIG_EDD=m CONFIG_EFI_VARS=m CONFIG_DELL_RBU=m CONFIG_DCDBAS=m # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_PAGE_OFFSET=0xC000 CONFIG_HIGHMEM=y CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_SPARSEMEM_STATIC=y CONFIG_SPLIT_PTLOCK_CPUS=4 # CONFIG_RESOURCES_64BIT is not set # CONFIG_HIGHPTE is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y CONFIG_EFI=y CONFIG_IRQBALANCE=y CONFIG_BOOT_IOREMAP=y CONFIG_REGPARM=y # CONFIG_SECCOMP is not set # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_1000 is not set CONFIG_HZ=250 CONFIG_KEXEC=y # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x10 CONFIG_HOTPLUG_CPU=y CONFIG_COMPAT_VDSO=y CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y 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 So here the DB2 log 2008-03-21-15.56.01.630547+060 E9166G1188 LEVEL: Event PID : 32282TID : 2986575552 PROC : db2star2 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911 MESSAGE : ADM7513W Database manager has started. START : DB2 DBM DATA #1 : Build Level, 128 bytes Instance db2inst1 uses 32 bits and DB2 code release SQL09050 with level identifier 03010107. Informational tokens are DB2 v9.5.0.0, s071001, LINUXIA3295, Fix Pack 0. DATA #2 : System Info, 436 bytes System: Linux test 6 2 i686 CPU: total:2 online:2 Cores per socket:1 Threading degree per core:2 Physical Memory(MB): total:2029 free:702 Virtual Memory(MB): total:6125 free:4798 Swap Memory(MB): total:4096 free:4096 Kernel Params: msgMaxMessageSize:65535 msgMsgMap:65536 msgMaxQueueIDs:1024 msgNumberOfHeaders:65536 msgMaxQueueSize:65536 msgMaxSegmentSize:16 shmMax:268435456 shmMin:1 shmIDs:4096 shmSegments:4096 semMap:32000 semIDs:1024 semNum:32000 semUndo:32000 semNumPerID:250 semOps:32 semUndoSize:20 semMaxVal:32767 semAdjustOnExit:32767 2008-03-21-15.56.03.475024+060 I10355G477 LEVEL: Event PID : 32295TID : 2977950624 PROC : db2sysc INSTANCE: db2inst1 NODE : 000 APPHDL : 0-7 APPID: *LOCAL.db2inst1.080321145603 AUTHID : DB2INST1 EDUID : 18 EDUNAME: db2agent (instance) FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20 CHANGE : CFG DB TOOLSDB : Database_memory From: 20 automatic To: 20416 automatic 2008-03-21-15.56.47.131581+060 E10833G462 LEVEL: Event PID : 32295TID : 2967464864 PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : TOOLSDB APPHDL : 0-10 APPID: *LOCAL.DB2.080321145647 AUTHID : DB2INST1 EDUID : 41 EDUNAME:
Re: IBM DB2 V9.5 32 bits failed to allocate share memory
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 0x. 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 10 /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. -- Chris. == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: IBM DB2 V9.5 32 bits failed to allocate share memory
On Fri, Mar 21, 2008 at 10:16:52AM +0100, Vincent Bachelier wrote: Hi, I have a issue with IBM DB2 V9.5 (the express version) in 32 bits. I have install it on a 64 bits arch without any problem, on debian But in 32 bits, on a Bi-Xeon with 4g of ram, during installation they say Allocation memory failed : Cannot allocate share memory Is that the *exact* error message? It's a fresh debian etch 32 bits install, and a fresh ibm db2 v9.5 express install ! What is the output of: uname -a The damn is that it's for a test server in an enterprise condition. The only way I have found is to install the db2 server on a redhat enterprise, and they work ! I don't understand why ??? I would really prefer to keep everything on debian, but I think they is a setting that could make db2 crash ... I don't understand I have look in redhat config for kernel, all main think like HIMEM4G and 64BITS RESOURCE, is sets ... Any idea about this ? Take careful note of any error messages -- which, hopefully, will lead you to the right config files to compare between the working redhat and the non working Debian setup. Can you explain: all main think like HIMEM4G and 64BITS RESOURCE, is sets ... Whats this 64BITS RESOURCE? Is uname -a for redhat == uname -a for Debian? -- Chris. == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: IBM DB2 V9.5 32 bits failed to allocate share memory
On Mon, Mar 24, 2008 at 12:30:28AM +1300, Chris Bannister wrote: On Fri, Mar 21, 2008 at 10:16:52AM +0100, Vincent Bachelier wrote: Can you explain: all main think like HIMEM4G and 64BITS RESOURCE, is sets ... Whats this 64BITS RESOURCE? Is uname -a for redhat == uname -a for Debian? Or uname -a for AIX? Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
