Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
satriguy@aol.com — — source: Informix-list mailing list archive (1991-1998)
You need to avoid dynamic shared memory segments on HP at all costs. If
your
SHMVERTSIZE is 60000, I would suspect that would be enough. However, if
your application is leaving a lot of open statements (i.e. not issueing a
FREE on a prepared statement or CURSOR) then each user thread might need a
lot of memory in the shared memory segment. You might want to monitor your
system
with some "onstat -g ses" commands to see if it appears that your threads
continue to allocate memory, or if they seem to 'level out' at some point.
If it appears that the memory usage per session continues to grow, then
you should open a case with tech support.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.