SE 7 & error 208
Greetings,
The finderr for -208 shows (in part):
The database server needed to allocate data-space memory in order to
process the query, but none was available. This error may reflect a
hardware limit, an operating-system configuration limit, or a temporary
shortage of space.
In versions later than 5.01, only this error message informs you that
the database server is unable to allocate memory.
Some general info:
Server = HP 9000/800, 2 CPU's & 4 Gig RAM
O/S = HPUX B11.11 (with all patches)
Informix = SE 7.25.HC1
We grabbed the database and ran this same program on another
server (AIX 4.3.3; IDS 7.31) with no problems. We also run
this same program on over 1,000 other client machines. This
is the only site with this issue.
I ran a few utilities while the program ran & failed:
sar -w:
HP-UX aims2 B.11.11 U 9000/800 11/04/04
09:28:21 swpin/s bswin/s swpot/s bswot/s pswch/s
09:28:26 0.00 0.0 0.00 0.0 480
09:28:31 0.00 0.0 0.00 0.0 261
... All the ones in between look the same
11:49:51 0.00 0.0 0.00 0.0 1312
11:49:56 0.00 0.0 0.00 0.0 411
11:50:01 0.00 0.0 0.00 0.0 870
Average 0.00 0.0 0.00 0.0 4977
ipcs -mob:
IPC status from /dev/kmem as of Thu Nov 4 09:28:21 2004
T ID KEY MODE OWNER GROUP NATTCH SEGSZ
Shared Memory:
m 0 0x411c07ba --rw-rw-rw- root root 0 348
m 1 0x4e0c0002 --rw-rw-rw- root root 2 61760
m 2 0x412009ea --rw-rw-rw- root root 2 8192
m 1603 0x0c6629c9 --rw-r----- root root 2 19057872
m 4 0x06347849 --rw-rw-rw- root root 1 77384
m 805 0xffffffff --rw-r--rw- root root 0 22908
m 6 0x33143ffb --rw------- root root 3 1129624
m 7 0x6d143ce6 --rw-rw-rw- root root 2 47120
... All the ones in between look the same
Thu Nov 4 11:49:07 EST 2004
IPC status from /dev/kmem as of Thu Nov 4 11:49:37 2004
T ID KEY MODE OWNER GROUP NATTCH SEGSZ
Shared Memory:
m 0 0x411c07ba --rw-rw-rw- root root 0 348
m 1 0x4e0c0002 --rw-rw-rw- root root 2 61760
m 2 0x412009ea --rw-rw-rw- root root 2 8192
m 1603 0x0c6629c9 --rw-r----- root root 2 19057872
m 4 0x06347849 --rw-rw-rw- root root 1 77384
m 805 0xffffffff --rw-r--rw- root root 0 22908
m 6 0x33143ffb --rw------- root root 3 1129624
m 7 0x6d143ce6 --rw-rw-rw- root root 2 47120
vmstat -nS:
Thu Nov 4 09:28:21 EST 2004
VM
memory page faults
avm free si so pi po fr de sr in sy cs
46235 189486 0 0 0 0 0 0 0 531 3784 294
CPU
cpu procs
us sy id r b w
4 2 94 1 0 0
4 4 91
... All the ones in between look the same
VM
memory page faults
avm free si so pi po fr de sr in sy cs
36154 195922 0 0 0 0 0 0 0 611 1688 165
CPU
cpu procs
us sy id r b w
1 1 98 1 0 0
2 4 94
swapinfo -t
Thu Nov 4 09:28:21 EST 2004
Kb Kb Kb PCT START/ Kb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 8388608 0 8388608 0% 0 - 1 /dev/vg00/lvol2
reserve - 724416 -724416
memory 3338384 2617420 720964 78%
total 11726992 3341836 8385156 28% - 0 -
... All the ones in between look the same
Thu Nov 4 11:49:13 EST 2004
Kb Kb Kb PCT START/ Kb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 8388608 0 8388608 0% 0 - 1 /dev/vg00/lvol2
reserve - 828136 -828136
memory 3338384 2617476 720908 78%
total 11726992 3445612 8281380 29% - 0 -
All of these makes me wonder how the SE can determine a lack of
memory. No where do I see the system ruuning low on memory or
even swapping to disk. Other users on the machine do not see
any performance hit while this runs and fails.
Any ideas before I open a trouble call with support?
Thanks,
Tom