In article <689i3e$4lk$1@sparky.wolfe.net>, SteveS
<ssilva@prestongates.com> writes
>Has anyone had any experience using the dump file created with an assertion
>failure? I would like to understand what happens during such a failure and
>how I can pinpoint what is causing the failure.
>
>I believe you can use onstat -g ses with the dump file (something like
>shmem.1db----- onstat -g ses sesid). Unfortunately, if you don't know what
>the session id was, how can you look. Is there a utility or anything else
>that can help?
>
>Any help is appreciated. Thanks.
>
>
You mean the shmem.* file? Try
onstat shmem.<whatever> -g ses
This will list all sessions.
If you check your online.log you should find a message which shows the
session which brought the engine down. Also you may find a
/tmp/af.xxxx file mentioned which can be useful.
--
David Williams
Maintainer of the Informix FAQ
Primary site (Beta Version) http://www.smooth1.demon.co.uk
Official site http://www.iiug.org/techinfo/faq/faq_top.html
I see you standin', Standin' on your own, It's such a lonely place for you, For
you to be If you need a shoulder, Or if you need a friend, I'll be here
standing, Until the bitter end...
So don't chastise me Or think I, I mean you harm...
All I ever wanted Was for you To know that I care