From: steveee_ca@my-deja.com
Newsgroups: comp.databases.oracle.server
Subject: Re: Stack Trace
Date: Tue, 12 Dec 2000 13:43:00 GMT
Organization: Deja.com - Before you buy.
Lines: 38
Message-ID: <915a13$b0o$1@nnrp1.deja.com>
References: <913idd$157$1@nnrp1.deja.com>
NNTP-Posting-Host: 209.226.121.110
X-Article-Creation-Date: Tue Dec 12 13:43:00 2000 GMT
X-Http-User-Agent: Mozilla/4.73 [en]C-SYMPA (Win98; U)
X-Http-Proxy: 1.0 x70.deja.com:80 (Squid/1.1.22) for client 209.226.121.110
X-MyDeja-Info: XMYDJUIDsteveee_ca


Hi Bill,

A couple of ways..one, if you have Procedure Builder, you can step
through your code and then open up the Error Stack..
I've got a generic script I sometimes use that inserts errors into some
'error table' that I create for that purpose..it uses calls to
DBMS_UTILITY. There are functions in that package like

DBMS_UTILITY.FORMAT_ERROR_STACK and DBMS_UTILITY.FORMAT_CALL_STACK that
you can read into variables and insert into your 'error table'.

Hopefully this gets at what you're looking for.

Steve






In article <913idd$157$1@nnrp1.deja.com>,
  wdr1@pobox.com wrote:
> Hi,
>
> I was wondering if it's possible in PL/SQL to get a stack trace when
 an
> exception happens?  It would be might useful in tracking down bugs.
>
> Thanks,
> -Bill
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>


Sent via Deja.com http://www.deja.com/
Before you buy.