Re: Oracle Error handling capabilities ...

Maybe you already have an anwser since this was posted 12 days ago, but my idea would be to create a trigger on insert or update on that specific table, then do the error handling in the trigger it self, put your conditions in this code and raise them yourself. As you know you can set trigger to fire upon each row, so be carefull if your data is big this could take alote of more resources so try to keep your query's tight and fast if you can use the rowid. I guess like anything else you need to fine the right balance.

Hope this hint help
regards

narenn_at_my-dejanews.com wrote:
>
> Imagine there is an Oracle application which has very poor Error handling
> capabilities and needs to be enhanced. There is one macro which does
> very trivial error handling but this macro is shared by the entire application
> whenever and oracle error is encountered.
>
> How best can we enhance the error handling ? We need to build in error
> handling capacity for the following ...
>
> 1> Report update/insert on columns which have values greater than the
> allowed precision 2> Report Oracle NULL values being inserted where the
> columns are NOT NULL 3> Report Unique Constraints being violated etc etc
>
> All these errors are reported right now , but we want to isolate certain
> errors as not fatal and proceed. But in the process log the column name,
> table name or index name which needs to be investigated. The errors reported
> right now by oracle are very generic sometimes. For example there is no way i
> know of to find which column has a overflow occuring when we update/insert a
> table ?
>
> What are , if any new error handling routines in oracle 8 which you have used.
>
> Plese share your experiences either replying here or sending mail to
> Narendra.Nathmal_at_fmr.com
>
> Thanks
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

Received on Mon Jan 25 1999 - 18:44:15 CST