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.
greetings all,
we are on 9.40 FC3 on hp-UX 11i - sometimes segments are being added
and cannot flush with onmode -F . is there a way to view what is
holding on to them? i thought the address from onstat -u might match
to the address in onstat - g seg but this is not the case..thanks for
any help
tom
↪ replying to tomL
Madison Pruet — — source: Usenet: comp.databases.informix
onstat -g mem displays the pool names (first column)
onstat -g afr <poolname> displays the allocated fragments by address.
If you run onstat -g seg, you get the logical address of the shared memory
segments.
Somthing like...
for f in `onstat -g mem | cut -d ' ' -f 1 `
do
onstat -g afr $f | nawk -v POOL=$f '{ printf("%s %s %s\\n", $1, POOL,
$3)}'done | sort
should make it easier to figure out what is in the segment
M.P.
"tomL" <tomcaml@yahoo.com> wrote in message
news:3158a6a2.0408111244.8695da0@posting.google.com...
> greetings all,
> we are on 9.40 FC3 on hp-UX 11i - sometimes segments are being added
> and cannot flush with onmode -F . is there a way to view what is
> holding on to them? i thought the address from onstat -u might match
> to the address in onstat - g seg but this is not the case..thanks for
> any help
>
>
> tom
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.