Handling Memory Limits
- From: "red_valsen@xxxxxxxxx" <red_valsen@xxxxxxxxx>
- Date: Mon, 22 Feb 2010 11:30:59 -0800 (PST)
Occasionally we run into a situation on development hosts in which the
informixserver is running several memory-intensive processes and
attempts to procure more memory than the O/S permits. Since we don't
set SHMTOTAL (and RESIDENT=0), the informixserver at first fills its
tmp dbspaces, then its root dbspace, then just aborts, leaving behind
unhelpful assert failure files. If we set SHMTOTAL, however, in the
same circumstance the message log is flooded with notices redundantly
describing the lack of memory; the informixserver is rendered
unusable, not responding even to attempts to kill the offending
sessions, and we have to shutdown and restart the instance anyway.
Have others experienced this kind of error? Is there any way for the
informixserver itself to avoid these extremes in behavior -- seppuku
or schizophrenia -- somehow, and ensure that it can handle more
adroitly a lack of memory resources?
Running IDS 11.50.FC4 on HP-UX 11.23.
.
- Follow-Ups:
- Re: Handling Memory Limits
- From: brenddie
- Re: Handling Memory Limits
- Prev by Date: Re: IBM's Academic Initiative
- Next by Date: Building Fast Data Warehouse Schema's, Deploying a Star Schema - a New Webcast at Tue 2/22/10 at 2:00pm EST
- Previous by thread: Re: IBM's Academic Initiative
- Next by thread: Re: Handling Memory Limits
- Index(es):
Relevant Pages
|
