| Error Handling in clustered Procedures in a PKG [message #41201] |
Mon, 09 December 2002 23:40  |
Chandra Gowda
Messages: 1
Registered: December 2002
|
Junior Member |
|
|
Hi,
I need to handle Neat Error (example System Parameter missing) and display through D2K forms to the end user. So that it does not stop any transaction for different customer.
Assuming there are 4 procedures A,B,C and D in a package. Each procedure is independent and are being called randomly inside one another.
Scenario 1 A calls C, C calls D, D calls B
Scenario 2 B calls C, C calls A, A calls D
And so on…..
Bottom Line is that any error that is trapped inside any procedure, should display to the outermost calling procedure. Also any procedure (A,B,C,D)can be outermost procedure in different instances and also tey could be the innermost procedure.
Can anyone suggest a way out.
PS: I tried using the DBMS_UTILITY.Error_stack and DBMS_UTILITY.Call_STACK. This serves the purpose only when you can definitely say that procedure A is always the OUTERMOST procedure. If other procedures (B,C,D etc) become outermost procedures this can't handle.
Also it displays oracle error and procedure name not Neat Error.
Thanks
Chandra
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
