Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: dbms_alert.signal triggers a memory dump? why?

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

From: Daniel Morgan <damorgan_at_x.washington.edu>
Date: Thu, 25 Sep 2003 21:47:15 -0700
Message-ID: <1064551628.809053@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.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)
Received on Thu Sep 25 2003 - 23:47:15 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US