Re: ORA-6510 wrapped PL/SQL no easy access to source
- From: Jack van Zanen <jack@xxxxxxxxxxxx>
- To: Hemant K Chitale <hkchital@xxxxxxxxxxxxxx>
- Date: Wed, 25 Aug 2010 10:57:10 +1000
Hi All,
The mystery is solved, sort of.
I dug through the trace files and could not find any error message (ORA-,
ERR#, whatever) but did notice that between the failing statement parsing
and the actual closing of that cursor there was a call to delete from
sdo_geor_ddl__table$$
This is from spatial, we do not need to use spatial in this database so I
removed it and it now works fine.
Obviously this app and the way it works does not mix very well with oracle
Spatial.
Jack van Zanen
-------------------------
This e-mail and any attachments may contain confidential material for the
sole use of the intended recipient. If you are not the intended recipient,
please be aware that any disclosure, copying, distribution or use of this
e-mail or any attachment is prohibited. If you have received this e-mail in
error, please contact the sender and delete all copies.
Thank you for your cooperation
On 25 August 2010 00:11, Hemant K Chitale <hkchital@xxxxxxxxxxxxxx> wrote:
>
> The trace file would have an ERR# entry before the "SQL*Net break/reset
> client". The ERR# would be the Error Number.
>
> Hemant K Chitle
>
>
> At 02:10 PM Tuesday, Jack van Zanen wrote:
>
> Error:
>> ORA-06510: PL/SQL: unhandled user-defined exception
>>
>>
>> When we trace the application we can see the statement executed returning
>> no rows and having the "SQL*Net break/reset to client" waits with it. These
>> waits point to an error in the call, but what I really like to see is the
>> actual oracle error generated which is unfortunately hidden by the user
>> defined exception.
>>
>> How can I find out, without going back to the vendor, what the actual
>> error message is.
>>
>>
>> I will try "alter system set events '6510 trace name errorstack level
>> 1';", but will it help?
>>
>>
>> Jack van Zanen
>>
>>
>
> Hemant K Chitale
>
> http://hemantoracledba.blogspot.com
>
>
>
>
>
>
Other related posts:
