Re: Contiguous shared memory segment allocation failed at 0xd0000000
Posted in 2006
Topics: Server Administration, Platform-Specific Issues, Internationalization & Character Sets
You're on Version 10 ? You may be able to save resources and time on the delete part by using Truncate table. It can delete a whole table in one fell swoop.
========================
-<<Floyd Wellershaus>>-
Database Administrator
Unix Administrator
email: fwellers@yahoo.com
Home: 703-430-0805
Cell: 703-477-6045
========================
http://www.one.org/
----- Original Message ----
From: Murray Wood (IList) (Murray Wood (IList)) <ifxmaillist@quanta.co.nz>
To: informix-list@iiug.org
Sent: Sunday, August 13, 2006 5:17:44 PM
Subject: RE: Contiguous shared memory segment allocation failed at 0xd0000000
SHMBASE is different in your config from standard - why?
How much shared memory is allocated to this instance (onstat -g seg) ?
How many locks do you need for this process (16:10:23 dynamically allocated
100000 locks) ? OR you could lock the table.
You need to configure LOCKS to what you require. When it adds locks it may
require more shared memory! (I have forgotten whether there is a limit on
the number of shared memory segments on AIX 5.2).
MW
-----Original Message-----
From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org]
On Behalf Of Yunyao (Frank) Qu
Sent: Saturday, 12 August 2006 3:56 a.m.
To: informix-list@iiug.org
Subject: Contiguous shared memory segment allocation failed at 0xd0000000
I was doing a mass update, delete ( big transaction) and found the info
in online log,
16:10:21 Maximum server connections 21
16:10:23 Requested shared memory segment size rounded from 8604KB to8608KB
16:10:23 Contiguous shared memory segment allocation failed at 0xd0000000.Allocation successful at 0x30000000.
Check SHMBASE is consistent with the value in
$INFORMIXDIR/etc/onconfig.std.
If you are using the correct SHMBASE value in your ONCONFIG file, then
consider this message informational only.
16:10:23 Dynamically allocated new virtual shared memory segment (size
8608KB)
16:10:23 dynamically allocated 100000 locks
16:10:25 Requested shared memory segment size rounded from 8604KB to8608KB
16:10:25 Contiguous shared memory segment allocation failed at 0xd0000000.Allocation successful at 0xe0000000.
Check SHMBASE is consistent with the value in
$INFORMIXDIR/etc/onconfig.std.
If you are using the correct SHMBASE value in your ONCONFIG file, then
consider this message informational only.
(1) why "Contiguous shared memory segment allocation failed at 0xd0000000.
Allocation successful at 0x30000000." ?
(2) whay "Check SHMBASE is consistent with the value in
$INFORMIXDIR/etc/onconfig.std"? Since I used a different onconfig file:
onconfig.dev1
INFO in my onconfig:
informix@dolly $ more onconfig.dev1 | grep SHM
SHMBASE 0x40000000 # Shared memory base address
SHMVIRTSIZE 32768 # initial virtual shared memory segmentsize
SHMADD 8192 # Size of new shared memory segments
(Kbytes)
EXTSHMADD 8192 # Size of new extension shared memory
segments (Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited# For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.
DUMPSHMEM 1 # Dump a copy of shared memory
informix@dolly $ more onconfig.std | grep SHM
SHMBASE 0x30000000L # Shared memory base address
SHMVIRTSIZE 8192 # initial virtual shared memory segmentsize
SHMADD 8192 # Size of new shared memory segments
(Kbytes)
EXTSHMADD 8192 # Size of new extension shared memory
segments (Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited# For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.
DUMPSHMEM 1 # Dump a copy of shared memory
informix@dolly $ onstat -version
Program Name: onstat
Build Version: 10.00.UC4
Build Number: N204
Build Host: ibm6c1b
Build OS: AIX 5.2
Build Date: Fri Nov 18 23:37:26 CST 2005
GLS Version: glslib-4.00.UC7
Thank you for your time!
Frank
--
Yunyao "Frank" Qu
Computer Sciences Corporation(CSC)
NOAA/CLASS, (301)817-4696
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
Does it exist yet?
--
Neil Truby t:01932 724027
Director m:07798 811708
Ardenta Limited e:neil.truby@ardenta.com
"Floyd Wellershaus" <fwellers@yahoo.com> wrote in message
news:mailman.256.1155506071.20706.informix-list@iiug.org...
You're on Version 10 ? You may be able to save resources and time on the
delete part by using Truncate table. It can delete a whole table in one fell
swoop.
========================
-<<Floyd Wellershaus>>-
Database Administrator
Unix Administrator
email: fwellers@yahoo.com
Home: 703-430-0805
Cell: 703-477-6045
========================
http://www.one.org/
----- Original Message ----
From: Murray Wood (IList) (Murray Wood (IList)) <ifxmaillist@quanta.co.nz>
To: informix-list@iiug.org
Sent: Sunday, August 13, 2006 5:17:44 PM
Subject: RE: Contiguous shared memory segment allocation failed at
0xd0000000
SHMBASE is different in your config from standard - why?
How much shared memory is allocated to this instance (onstat -g seg) ?
How many locks do you need for this process (16:10:23 dynamically allocated
100000 locks) ? OR you could lock the table.
You need to configure LOCKS to what you require. When it adds locks it may
require more shared memory! (I have forgotten whether there is a limit on
the number of shared memory segments on AIX 5.2).
MW
-----Original Message-----
From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org]
On Behalf Of Yunyao (Frank) Qu
Sent: Saturday, 12 August 2006 3:56 a.m.
To: informix-list@iiug.org
Subject: Contiguous shared memory segment allocation failed at 0xd0000000
I was doing a mass update, delete ( big transaction) and found the info
in online log,
16:10:21 Maximum server connections 21
16:10:23 Requested shared memory segment size rounded from 8604KB to8608KB
16:10:23 Contiguous shared memory segment allocation failed at 0xd0000000.Allocation successful at 0x30000000.
Check SHMBASE is consistent with the value in
$INFORMIXDIR/etc/onconfig.std.
If you are using the correct SHMBASE value in your ONCONFIG file, then
consider this message informational only.
16:10:23 Dynamically allocated new virtual shared memory segment (size
8608KB)
16:10:23 dynamically allocated 100000 locks
16:10:25 Requested shared memory segment size rounded from 8604KB to8608KB
16:10:25 Contiguous shared memory segment allocation failed at 0xd0000000.Allocation successful at 0xe0000000.
Check SHMBASE is consistent with the value in
$INFORMIXDIR/etc/onconfig.std.
If you are using the correct SHMBASE value in your ONCONFIG file, then
consider this message informational only.
(1) why "Contiguous shared memory segment allocation failed at 0xd0000000.
Allocation successful at 0x30000000." ?
(2) whay "Check SHMBASE is consistent with the value in
$INFORMIXDIR/etc/onconfig.std"? Since I used a different onconfig file:
onconfig.dev1
INFO in my onconfig:
informix@dolly $ more onconfig.dev1 | grep SHM
SHMBASE 0x40000000 # Shared memory base address
SHMVIRTSIZE 32768 # initial virtual shared memory segmentsize
SHMADD 8192 # Size of new shared memory segments
(Kbytes)
EXTSHMADD 8192 # Size of new extension shared memory
segments (Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited# For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.
DUMPSHMEM 1 # Dump a copy of shared memory
informix@dolly $ more onconfig.std | grep SHM
SHMBASE 0x30000000L # Shared memory base address
SHMVIRTSIZE 8192 # initial virtual shared memory segmentsize
SHMADD 8192 # Size of new shared memory segments
(Kbytes)
EXTSHMADD 8192 # Size of new extension shared memory
segments (Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited# For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.
DUMPSHMEM 1 # Dump a copy of shared memory
informix@dolly $ onstat -version
Program Name: onstat
Build Version: 10.00.UC4
Build Number: N204
Build Host: ibm6c1b
Build OS: AIX 5.2
Build Date: Fri Nov 18 23:37:26 CST 2005
GLS Version: glslib-4.00.UC7
Thank you for your time!
Frank
--
Yunyao "Frank" Qu
Computer Sciences Corporation(CSC)
NOAA/CLASS, (301)817-4696
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
Please note that one more reason for not top-posting is that the top-posted signature converts the rest of the message into a signature block, so the conscientious poster has to work much harder than should be necessary to provide salient context! (And there were three top posted answers in a row - all the people tagged below are guilty of top-posting!) Murray Wood wrote (in response to a question detailing memory allocation problems with shmbase values and non-contiguous segments): > SHMBASE is different in your config from standard - why? Floyd Wellershaus wrote: > You're on Version 10? You may be able to save resources and time on > the delete part by using Truncate table. It can delete a whole table > in one fell swoop. Neil Truby wrote: > Does it exist yet? Does what exist yet? IDS 10.00 exists. And TRUNCATE TABLE was added in 10.00.UC4. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/
Related threads
- Posting from the Informix-list
- Migrating from IDS 9.40.UC6 to 11.50.UC3
- Ip for a network session
- questions onstat -g