|
|
|
|
|
|
|
|
|
|
Re: ORA errors reflected in Apps not registering in the database alert log [message #642993 is a reply to message #642964] |
Thu, 24 September 2015 06:56   |
 |
EdStevens
Messages: 1375 Registered: September 2013
|
Senior Member |
|
|
bpeasland wrote on Wed, 23 September 2015 09:13Where I work, we trap the ORA error in our app code. We give the user a more user-friendly error message but we log the actual ORA- error into a log table in the database. This way, we can go back and research application errors after the fact.
Cheers,
Brian
Brian,
I know you and I have discussed this before and are in agreement, but for the sake of the OP, allow me to point out that a key to your system is that you actually trap and record the original ORA- message. The bane of DBAs is the application the simply replaces the original error message (and its code) with a "user friendly" (read: "meaningless") message. The actual, meaningful error is lost forever, and yet the DBA is somehow expected to know that "Error. Please contact your IT department" actually means (in this one particular instance only) "ORA-01476".
|
|
|
|