Re: dbms_alert.signal triggers a memory dump? why?

Daniel Morgan <damorgan_at_x.washington.edu> wrote in message news:<1064551628.809053_at_yasure>...
> Ryan wrote:
>
> >one of my co-workers was testing the following
> >
> >procedure is
> >
> >begin
> >
> >raise exception
> >
> >exception
> >when others then
> >dbms_alert.signal(unRegistered_alert);
> >end;
> >
> >now this locked up because he didnt commit. So he killed the session. He had
> >of these running at the same time. Killed both sessions. Nothing else needed
> >to be rolled back. The status went to 'killed' and the memory dumped to
> >udump? We had to do a shutdown abort to bounce the instance.
> >
> >any idea why this might happen? I thought memory dumps went to cdump?
> >According to him there was nothing else running in these sessions and he
> >just created them to do this. This is on 8.1.7 on Solaris. No mention on
> >metalink.
> >
> >what causes memory dumps to trace files?
> >
> >
> >
> Memory dumps go where you tell them to go. This was a user dump so it
> went to udump. Check your initSID.ora
> to see where you've pointed the various pieces of the pie.

what causes a memory dump? Received on Fri Sep 26 2003 - 05:56:06 CDT