MC.9 and MCY1 and Exception Handling in (Logistics Inf. Sys)LIS

Hi,
I want the 'Valuated Stock Value" greater then or equal to zero (>=) appear in the MC.9 report. I can create 'Exception' in MCY1 but am unable to do so. Once I am in MCY1; I choose 'Requirements' then Key Figure 'Valuated Stock Value' then 'Type of condition' is 'Threshold Val. Anal.' is set to '> 0'. However, the report still displays zero values in MC.9. I don't want to display 'Valuated Stock Value' zero to be displayed on the report. Please help.
Thanks
Naved

Hey Chris,
I got the point for exception handling in weblogic 9.2. We ae using 9.2. It comes up with the concept of shared page flows which means all my unhandled exceptions are thrown to the shared page flow controller. There based on the type of exception, i can forward the request to appropraite page.
Thanks anywyas,
Saurabh

Similar Messages

Provider Hosted App - Exception Handling and Logging

Hello,
I would like to use file system to log the exceptions (The IIS server in which the APP is configured) for Provider Hosted App - Could anyone share some blogs/links related to that?
Thanks in advance,

Well the first time, I asked the question, I think I
was not so clear. Please let me explain this in
detail. I am not architect, so correct me if I am
wrong.
I want to use log4J but definitely want to avoid using
them directly in our package, idea is to create
wrappers around all the external API, jar we are
using. At logging side I feel little comfortable.
But having little difficulty in thinking and designing
about Exception handling framework.
1. My aim is to create a general framework in 3 broad
categories (For Presentation tier, For Business tier,
for Data Access tier)
2. For each tier if you import those already created
framework classes, all developers should be just able
to use the methods of exception framework and use them
in catch block and throw them.
Example:- I would like to create a class called
MyProjectExceptionDecider, which will decide the type
of exception in Business Tier and then use my
MyProjectExceptionErrorParser, which reads the XML
document and gets a related message number and error
message.
This MyProjectExceptionErrorParser then passes the
right exception to MyProjectExceptionDisplayer which
will display the exception with right message and
message number.
And something more like this. I am not yet getting
complete picture.
3. So, if you have done something similar and if you
have the class diagram and sequence diagram for such
exception handling, I would be grateful if you are
willing to share with me.
Please let me know, if you have different ideas. I
request you all to participate and throw your ideas
and suggestions.
Srikanthgenerally, wheather or not you are using log4j or anything else, when designing exception handling mechnism, you need to decide on where or by whom an exception will be handled, and if the exception needs to be displyed, and how it is displayed.

What is the idea behind Render Response and Exception Handling in TF?

Dear All,
While searching for answer for my question, I find it hard to decipher this line.
task flow exception handling doesn't handle any exception that is in Render Response phase
I found this several times in many post like this.
Re: ADF Exception handling (including RENDER RESPNSE PHASE)
and this
Re: Exception Handling in TaskFlow
What's the idea behind exception handling in task flow that is related to JSF/ADF life cycle?
I can't find a resource on why I should know what phase an exception has been thrown?
Sorry if my question might be vague/ignorant to others, but I just would like to know the idea from experts around here. :)
Thanks.
JDEV 11G PS4

Hi,
Render Response is the last lifecycle phase processed during JSF request. The ADF controller has no chance of handling exceptions that occur during this time (example, exception thrown in managed bean) and therefore in its default exception handling implementation ignores this lifecycle phase. As an application developer you don't need to know when an exception is raised. However, if you find that an exception occurs during Render Response and it is not handled by the ADFc declarative exception handler, then you know. You can try and override the framework exception handler as explained here:
https://blogs.oracle.com/jdevotnharvest/entry/extending_the_adf_controller_exception_handler
However, better practice is to use try/catch blocks surrounding e.g. calls in a managed bean that could cause exceptions
Frank

Exception Handling in bounded taskflows - expected behaviour

Hi,
I'm currently reviewing exception handling in bounded task flows and some things does not seems to be very clear for me.
(q1) Does it make sense that a bounded task flow calls a method (via a method activity) defined on the page definition of another page (outside of the BTF) by using a #{data.xxxmyPageDef.myMethodName.execute} EL expression?
(q2) Is is correct to expect the application to execute the method marked as ExceptionHandler in the taskflow, whenever an exception occurs?
(q3) I created 5 different scenarios where I call a service method which throws an exception, from within a page fragment of the BTF.
(q3 – sc1) Call a service method through the binding layer of the current page (by using #{bindings.xxx.execute})
Result: A dialog containing the exception message appears.
This is what I expected. Althought, the exception handler method does not seems to be invoked.(q3 – sc2) Call a service method through a task flow method activity using #{bindings.xxx.execute}
Result: A dialog containing the exception message appears.
This is what I expected. Althought, the exception handler method does not seems to be invoked.(q3 – sc3) Call a service method through a task flow method activity using #{data.myPageFragementPagedef.xxx.execute} (accessing the pageDef of the page fragment)
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage.(q3 – sc4) Call a service method through a task flow method activity using #{data.myPageContainingThePageFragmentPageDef.xxx.execute} (accessing the page containing the BTF region)
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage. (q3 – sc5) Call a service method through a task flow method activity using #{data.aPageOutsideTheBTFPageDef.xxx.execute} (accessing a page outside the BTW)
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage. (q4) How can it be possible that – without an exception handler – exceptions occur when calling method activities, without the exceptions being translated to FacesMessages?
Thanks in advance,
Koen Verhulst
JDeveloper 11.1.1.4

Koen,
+(q1) Does it make sense that a bounded task flow calls a method (via a method activity) defined on the page definition of another page (outside of the BTF) by using a #{data.xxxmyPageDef.myMethodName.execute} EL expression?+
No. Exceptions should be handled locally.
+(q2) Is is correct to expect the application to execute the method marked as ExceptionHandler in the taskflow, whenever an exception occurs?+
Only for exceptions that are before Render Response. The Render Response Phase is not handled in ADFc. So exceptions that occur in managed beans may fall through
+(q3) I created 5 different scenarios where I call a service method which throws an exception, from within a page fragment of the BTF.+
+(q3 – sc1) Call a service method through the binding layer of the current page (by using #{bindings.xxx.execute}) Result: A dialog containing the exception message appears.+
This is what I expected. Althought, the exception handler method does not seems to be invoked.
The binding layer has an error handler you can override in the DataBinings.cpx file
+(q3 – sc2) Call a service method through a task flow method activity using #{bindings.xxx.execute}+
Result: A dialog containing the exception message appears.
This is what I expected. Althought, the exception handler method does not seems to be invoked.
Again, you use the binding layer to invoke the service
+(q3 – sc3) Call a service method through a task flow method activity using #{data.myPageFragementPagedef.xxx.execute} (accessing the pageDef of the page fragment)+
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage.
Never use such a call. Its bad practice as there is no guarantee the container you reference is active. Always have the method call activity have its own binding defined when accessing a method call activity. I know there are lots of example floating aroundthat you #{data ...} and many are from 10.1.3. This should be avoided alltogether though
+(q3 – sc4) Call a service method through a task flow method activity using #{data.myPageContainingThePageFragmentPageDef.xxx.execute} (accessing the page containing the BTF region)+
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does not seems to be invoked, I expect the ADF Error Handler to create a FacesMessage.
Again, this is not a proper use of the ADF framework.
+(q3 – sc5) Call a service method through a task flow method activity using #{data.aPageOutsideTheBTFPageDef.xxx.execute} (accessing a page outside the BTW)+
Result: Nothing happens. This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage.
accessing a page outside the BTW (!!!) This should ring a worst practices alarm on your laptop (obviously doesn't do it either)
+(q4) How can it be possible that – without an exception handler – exceptions occur when calling method activities, without the exceptions being translated to FacesMessages?+
Exceptions are not handled in a single place but stacked. The business service raises an exception and passes it to the binding layer if not handled. The binding layer handles the exception and if it can't passes it to ADFc. ADFc can handle this exception if it is not during Render Response.
Bottom line: There is no single point of exception handling. So as a recommendation for best practices
- Catch and handle exceptions as close as possible to their origins
- If things can go wrong, thy will - use try/catch blocks in managed beans
- Use an exception handling activity in all bounded task flows. In the case of task flow call activities being used exceptions can bubble up to the caller. However, this would take users out of their current application context
- Exceptions not handled in ADFc can be intercepted by overriding the application task flow exception handler (used by the exception handler activities). This would give you a chance e.g. to handle issues during Render Response
- Never fight the framework, never bend the framework: Don't use out of scope access to page definitions and resources. Exception handling is not a replacement for bad code practices (sorry for saying this, its not meant to be rude) :-)
Though I don't have a qualified numbers of bugs open for exception handling in ADF between 11.1.1.4 and now (and some that are open), but there are issues reported in this area. If there is something that really feels wrong, please go ahead and file a bug and provide a test case for development to have a look. The Render Response issue, for example is something we are aware of and that is in discussion (afaik knows, there is a change in exception handling in JSF 2 that may have an impact to what we can do in ADFc).
thanks
Frank

Exception handling of Transport acknowledgement in asynchronous send in BPM

HI,
A silly question, but your help would be greatly appreciated..
- I have a asynch send step in a BPM for sending data to the target system through RFC
- It has acknoweledgement property of this send step is set to transport acknowledgement
- The exception property of this send step is set to throw a 'RFCException'
- This send step is inside a block
- This block also has an Exception branch which catches this 'RFCException'
- now my RFC channel failed for some known reason, but the flow never went into the Exception branch
IS this behaviour of the 'transport acknowledgement' property of an asynch send step in BPM expected ?
What should I take care so that if my RFC receiver channel throws an exception, the flow of my BPM goes to the exception branch ??

- now my RFC channel failed for some known reason, but the flow never went into the Exception branch
IS this behaviour of the 'transport acknowledgement' property of an asynch send step in BPM expected ?
What should I take care so that if my RFC receiver channel throws an exception, the flow of my BPM goes to the exception
branch ??
When an exception is caught by the Transport Acknowledgement it will trigger the Exception branch (if the send step is defined inside a Block with an Exception Branch)
I think you have not defined (and then assigned) a proper Exception Handler for the Block.
Click on the Block and define an Exception Handler......click on the Exception Branch and then select the Exception Handler from the dropdown......if this is not done then the Exception Branch wont be executed.....perform a check on your BPM in IR (using F7) you may get some warnings.
Regards,
Abhishek.

Exception Handling in Web Center for UI related Errors not working.

Hi Guys,
I have implemented Error Handling in ADF Application with Custom Model Exception Handler ( which is "CustomExceptionHandler extends DCErrorHandlerImpl") to catch all Model Layer Exception and to customize those error messages.
I have implemented Error Handling in ADF Application with Custom View Exception Handler ( which is "CustomViewErrorHandler extends oracle.adf.view.rich.context.ExceptionHandler";) to catch all View Layer Exception and to customize those error messages.
The design for this is , in Model Custom Exception Handler i find the exception message in "public String getDisplayMessage(BindingContext bindingContext,Exception exception) " method and throw RuntimeException to pass this exception to Custom View Layer Exception , so that i can handle all the exception @ View Layer it self .
In the View Layer Exception Handler i am navigating to specific error page using
String contextPath = ((HttpServletRequest)FacesContext.getCurrentInstance().getExternalContext().getRequest()).getContextPath();
ExternalContext ectx = facesContext.getExternalContext();
ectx.redirect.
All these things absolutly working in ADF Application for all the exception ( Model , View ) and i am successfully navigating to error page.
Problem :
When i implement the same thing in Webcenter Application ( Model Custom Exception Handler and View Custom Exception Handler), Model Part is working as expected , but View Custom Exception Handler is not all calling .
i am assuming that ,this View Custom Exception Handler (CustomViewErrorHandler extends oracle.adf.view.rich.context.ExceptionHandler) works only for JSF Life cycle
"Allows frameworks to intercept otherwise unhandled exceptions thrown during the JSF lifecycle. ExceptionHandlers can be registered by adding a service file with a class name at META-INF/services/oracle.adf.view.rich.context.ExceptionHandler." from http://jdevadf.oracle.com/adf-richclient-demo/docs/apidocs/oracle/adf/view/rich/context/ExceptionHandler.html";
As Webcenter Portal uses ADF Life Cycle this Exception Handler is not calling , i am not sure.
if any one has any idea please let me know .
Thanks
Annapareddy Srinivasrao
Edited by: Srinivasrao Annapareddy on May 22, 2013 12:06 PM

i used runtime exception along with the wdwsmodel exception

General Exception Handling

Hello. In my applications I usually have a try catch(Throwable) block surrounding all the top code (the code in main()) to log and report errors and exceptions that is not caught anywhere else, and to have my application exit in a controlled way. But I recently noticed that exceptions thrown in event handling (i.e. java.awt.EventDispatchThread.run) are not caught by the try catch block in main().
Are there any easy way to catch everything so my app can exit in a controlled way?
If this is not possible which exceptions are not propagated to main()? I would guess that it's exceptions thrown in other threads, is this correct? If so, do I have to surround all event handling by try catch(Throwable) to be safe?
I would like more information and guidelines about exception handling. Any book recommendations?
Help appreciated, thanks!

You should never let exceptions propagate outside your event handling methods.
If you don't follow that rule, the java.awt.EventDispatchThread.run() method terminates and the Java Virtual Machine tries to print the stack trace to the terminal window (if there is one) and then exits, but not through your main() method.
So, try /catch all Exceptions inside your event handler methods:
// inside event handler method
try {
    // handle event here
   } catch (Throwable t) {
     // handle errors and recover from errors here
     // and either log error or if important display message to the user.
   }There is no easy-lazy way to do exception handling by only having the try/catch block in main in this case.
Note : If any of the listeners throws an exception none of the following listeners is called. Since there is no guarantee of the order in which listeners are called you cannot be sure which ones are called first.

JSF Exception Handling Example

Here is an example of catching a backend exception and displaying it on the UI. It seems like most of the examples in books and such concern themselves with Validators and Converters. If you are trying to catch a backend exception, and you just want to display a UI message for it, see if this will work for you:
JSF tags:
<h:commandLink id="myActionLink" value="#{msgs.myLinkText}" binding="#{MyFormBean.uiComponentLink}" action="#{MyFormBean.linkProcessingMethod}"></h:commandLink>
<h:messages layout="table" errorClass="Errors" styleClass="AlignLeft"/>
...And now the exception handling and message creation inside of the managed bean:
private HtmlCommandLink uiComponentLink;
* Method that processes the link action
* @return String (action ID)
public String linkProcessingMethod()
     try
          // BEGIN: TEST ONLY
          if(1 == 1)     // Always true
               throw new Exception("TEST ERROR MESSAGE DISPLAY");
          // END: TEST ONLY
     return "dummyPageReference";     // No reference for this in faces-config.xml. Redisplays same page.
     catch (Exception e)
         addFacesMessageForUI("Exception detected. Message: " +e.getMessage());
         return "dummyPageReference";
* Add faces message for display on the UI
* @param String uiMessage
private void addFacesMessageForUI(String uiMessage)
     FacesMessage facesMessage = new FacesMessage(uiMessage);
     FacesContext facesContext = FacesContext.getCurrentInstance();
     // Passing null for the client ID argument to the FacesContext
     // addMessage() method specifies the message as not belonging
     // to any particular UI component. This will cause the message
     // to be displayed as a general message on the UI
     facesContext.addMessage(null,facesMessage);
}

chrisjohn wrote:
Following link would be helpful
[http://technologicalbrainstorm.wordpress.com/2009/09/19/exception-handling-in-jsf/]
Thanks!!Please, don't resurrect old threads, and especially not to post link-spam. Your account will get blocked if you continue with it. I'm locking this thread.
Kaj

Plz help in exception handling

Hello
I am trying to do this exception handling in string to numeric conversion. Everything is working fine except when i enter any number with letters f and d on exception handling doesnt work like for example if i enter 5f or 4 d progam is working fine, but it supposed to show that it is error.
here is the code:
class AlsMark implements ActionListener
        public void actionPerformed(ActionEvent ae)
           try {
            double amount=0;
            amount=Double.parseDouble(tfConvert.getText());
            amount=amount*0.168;
            lbResult.setText(tfConvert.getText()+" mark is "+Double.toString(amount)+" euro");
            validate();
            catch (NumberFormatException nfe)
                System.out.println(tfConvert.getText()+" is not an integer");
               // tfConvert.setText("0");
                JOptionPane.showMessageDialog(null,"Please enter a decimal value","Error",JOptionPane.ERROR_MESSAGE);
    }

The Double.parseDouble() method will accept f (float) and d (double) letters.
Try with:
class AlsMark implements ActionListener
        public void actionPerformed(ActionEvent ae)
           try {
            double amount=0;
            amount=(double)Integer.parseInt(tfConvert.getText());
            amount=amount*0.168;
            lbResult.setText(tfConvert.getText()+" mark is "+Double.toString(amount)+" euro");
            validate();
            catch (NumberFormatException nfe)
                System.out.println(tfConvert.getText()+" is not an integer");
               // tfConvert.setText("0");
                JOptionPane.showMessageDialog(null,"Please enter a decimal value","Error",JOptionPane.ERROR_MESSAGE);

Exception handling in rfcs and bapis

exception handling in rfcs and bapis

Hi Jayakrishna,
In General , there are non execptions in BAPIs, because of the reason, that the exception raised in a SAP envoronment may not mean anything for a non SAP initiator. All the exception situations would only fill the return table(TYpe BAPIRET2 or something like that). If you read that table after the call to the bapi, you can understand what has gone wrong.
Regards,
Ravi

Exception Handling and Stack Traces in JDK 1.1.8

Hi,
I'm presently maintain and upgrading a Web-Objects 4.5 application that uses the JDK 1.18. There are two constantly recurring exceptions that keep getting thrown, exceptions for which there are no stack traces. These are exceptions thrown by methods that do not presently have throws or try/catch code associated with them.
My questions are:
1) Why are there no stack traces available? Is it because the exception handling code is not there, or could there be another reason?
2) Will the inclusion of exception-handling code ALWAYS lead to stack traces and messages becoming available (if I put a e.printStackTrace() in my catch(Excetion e) clause), or will there be situations where it will not be available?
3) What is the best way for me to handle these types of exceptions in order to gain the most information possible about their root causes and possible solutions?
Thanks for your help.

I have never seen a case where there was no stack trace.
I have seen cases where the stack trace does not provide line numbers. I have also seen cases where it is less than useful as it terminates on a native call (which is to be expected.)
However, if you don't call printStackTrace() then you don't get it. And if you catch an exception an throw a different one you also loose information. So you might want to check those possibilities.

Exception Handling Standards -The exception Exception should never been thrown. Always Subclass Exception and throw the subclassed Classes.

In the current project my exception handling implementation is as follows :
Exception Handling Layer wise :
DL layer :
catch (Exception ex)
bool rethrow = ExceptionPolicy.HandleException(ex, "Ui Policy");
if (rethrow)
throw;
BL Layer
catch (Exception ex)
bool rethrow = ExceptionPolicy.HandleException(ex, "Ui Policy");
if (rethrow)
throw;
UI Layer
catch (Exception ex)
bool rethrow = ExceptionPolicy.HandleException(ex, "Ui Policy");
if (rethrow)
Response.Redirect("ErrorPage.aspx", false);
We have a tool to check the standards. And tool output is as follows :
The exception Exception should never been thrown. Always Subclass Exception and throw the subclassed Classes.
I need suggestions on how to implement the same according to standards.

Your tool is wrong if it says to never throw Exception. This was a common recommendation back in the .NET v1 days but has long since been thrown out. It is perfectly fine to use Exception when you have a general exception that provides no information
that an application can use to make an informed opinion.
The general rules of exception throwing is to throw the most specific exception that makes sense. If there is no specific exception that applies and it would be useful for the caller to handle the exception differently than other exceptions then creating
a custom exception type is warranted. Otherwise throwing Exception is reasonable. As an example you might have an application that pulls back product data given an ID. There is no built in exception that says the ID is invalid. However an invalid ID
is something that an application may want to handle differently than, say, an exception about the product being discontinued. Therefore it might make sense to create an ItemNotFoundException exception that the application can react to.
Conversely there is no benefit in having different exception types for disk full and disk quota met. The application will respond the same in either case.
Michael Taylor
http://blogs.msmvps.com/p3net

Exception Handling in Message Mapping and Alert

Hello,
1. Pls let me know the concept of Exception Handling and Alerts.
2. Pls provide some blogs for Exception Handling in Message Mapping.
3.What are Alerts and how it help us in XI. Pls provide some blogs for Alert
4.How are Alerts and Exception Handling can be related say for some scenario
Regards

Hi,
Plz check out these blogs of Sravya on Error Handling:
/people/sravya.talanki2/blog/2006/11/22/error-handling-framework-xiout-of-the-box-episode-1
/people/sravya.talanki2/blog/2006/11/23/error-handling-framework-xiout-of-the-box-episode-2
Also check this SAP Presentation:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9418d690-0201-0010-85bb-e9b2c1af895b
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
Error Handling :
http://help.sap.com/saphelp_nw04/helpdata/en/56/b46c3c8bb3d73ee10000000a114084/frameset.htm
Alerts:
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
http://help.sap.com/saphelp_nw04/helpdata/en/56/d5b54020c6792ae10000000a155106/content.htm
BPM:
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Working with acknowledgements
regards

4 Types of exception and the code to handle them

Dear all,
I would like to know wheter runtime exception, errors exception, unchecked exception and checked exception are classified as the 4 types of exception.
What are the java coding of them? please help.

There are two main families of exception in Java: checked and unchecked.
The base class for all exceptions is Throwable. Java provides Exception and Error that extend Throwable. RuntimeException (and many others) extend Exception.
RuntimeException and its descendants, and Error and its descendants, are called unchecked exceptions. Everything else is a checked exception.
If your method, or any method it calls, can throw a checked exception, then your method must either catch that exception, or declare that your method throws that exception. This way, when I call your method, I know at compile time what can possibly go wrong and I can decide whether to handle it or just bubble it up to my caller. Catching a given exception also catches all that exception's descendants. Declaring that you throw a given exception means that you might throw that exception or any of its descendants.
Unchecked exceptions (RuntimeException, Error, and their descendants) are not subject to those restrictions. Any method can throw any unchecked exception at any time without declaring it. This is because unchecked exceptions are either the sign of a coding error (RuntimeException), which is totally preventable and should be fixed rather than handled by the code that encounters it, or a problem in the VM, which in general can not be predicted or handled.
http://java.sun.com/docs/books/tutorial/essential/exceptions/index.html

Add three stored procs in one big proc and add exception handling

I have three proc's,
1. sp_staging
2. sp_upload
3. sp_process.
Now, I have to create a new proc as sp_daily which has the other three proc's in it in the same order.
if the first proc sp_staging fails, then the sp_daily proc should stop executing the other proc's which are in the order.
CREATE PROCEDURE sp_daily
AS
BEGIN TRY
EXEC sp_staging (already has EXCEPTION handling IN it)
GO
EXEC sp_upload (already has EXCEPTION handling IN it)
GO
EXEC sp_process (already has EXCEPTION handling IN it)
GO
END TRY
BEGIN CATCH
-- If any of the above proc's fail, the next proc's should not be executed
END CATCH
Something like this????

Hi naveej,
Whether the Stored Procedure sp_daily stops executing if the first sp_staging fails depends on how you code. To give a better demonstration, I will show the scenario that sp_upload runs with error. Please see the below code.
--create the scenario
USE master;
IF db_id('TestDB') IS NULL
CREATE DATABASE TestDB;
USE TestDB;
IF OBJECT_ID('T1') IS NOT NULL
DROP TABLE T1;
GO
CREATE TABLE T1
procName varchar(99)
IF OBJECT_ID('sp_staging') IS NOT NULL
DROP PROCEDURE "sp_staging";
GO
CREATE PROCEDURE "sp_staging" @denominator FLOAT
AS
BEGIN TRY
DECLARE @quotient FLOAT;
SET @denominator=1/@denominator; -- when @denominator=0, error occurs
INSERT INTO T1 VALUES('sp_staging finished');
END TRY
BEGIN CATCH
END CATCH
GO
IF OBJECT_ID('sp_upload') IS NOT NULL
DROP PROCEDURE "sp_upload";
GO
CREATE PROCEDURE "sp_upload" @denominator FLOAT
AS
BEGIN TRY
DECLARE @quotient FLOAT;
SET @denominator=1/@denominator;
INSERT INTO T1 VALUES('sp_upload finished');
END TRY
BEGIN CATCH
DECLARE @ERRMSG VARCHAR(99);
SELECT @ERRMSG=ERROR_MESSAGE()+'sp_upload failed, process continues';
INSERT INTO T1 VALUES(@ERRMSG);
END CATCH
GO
IF OBJECT_ID('sp_process') IS NOT NULL
DROP PROCEDURE "sp_process";
GO
CREATE PROCEDURE "sp_process" @denominator FLOAT
AS
BEGIN TRY
DECLARE @quotient FLOAT;
SET @denominator=1/@denominator;
INSERT INTO T1 VALUES('sp_process finished');
END TRY
BEGIN CATCH
END CATCH
GO
IF OBJECT_ID('sp_daily') IS NOT NULL
DROP PROCEDURE "sp_daily";
GO
CREATE PROCEDURE "sp_daily" @p1Deno FLOAT,@p2Deno FLOAT,@p3Deno FLOAT
AS
BEGIN TRY
EXEC sp_staging @p1Deno;
EXEC sp_upload @p2Deno;
EXEC sp_process @p3Deno;
END TRY
BEGIN CATCH
INSERT INTO T1 SELECT ERROR_MESSAGE()+'error captured by sp_daily';
END CATCH
GO
--Test Example
TRUNCATE TABLE T1;
EXEC sp_daily 1,0,1;
SELECT * FROM T1;
We can judge from the rows in T1, sp_daily continued even when there came a error in sp_upload. The reason for the continuity is that the error which occurred in sp_upload was caught and handled by sp_upload itself. Sp_daily's CATCH block didn't capture
any error(we didnt see any row like "error captured by sp_daily") so sp_dailys continued running with no interruption.
Let’s make a little modification on the sp_upload. see the below code.
ALTER PROCEDURE "sp_upload" @denominator FLOAT
AS
BEGIN TRY
DECLARE @quotient FLOAT;
SET @denominator=1/@denominator;
INSERT INTO T1 VALUES('sp_upload');
END TRY
BEGIN CATCH
DECLARE @ERRMSG VARCHAR(99),@ErrSeverity INT;
SELECT @ERRMSG=ERROR_MESSAGE()+'sp_upload failed, process got terminated',@ErrSeverity=ERROR_SEVERITY();
RAISERROR(@ERRMSG ,@ErrSeverity,1);
END CATCH
GO
--Test Example
TRUNCATE TABLE T1;
EXEC sp_daily 1,0,1;
SELECT * FROM T1;
At this time, sp_daily got terminated when sp_upload encountered an error. Sp_upload didn’t handle the error, it threw the error instead. Then the CATCH block in sp_daily caught the error and interrupted sp_daily itself. If you don’t
need to handle the error which may occur inside of the inner called procedures, the TRY and CATCH block in the procedure which calls them would be enough to catch and handle the errors anywhere it occurs, just remove the blocks from the called ones.
ALTER PROCEDURE "sp_staging" @denominator FLOAT
AS
DECLARE @quotient FLOAT;
SET @denominator=1/@denominator;
INSERT INTO T1 VALUES('sp_staging finished');
GO
ALTER PROCEDURE "sp_upload" @denominator FLOAT
AS
DECLARE @quotient FLOAT;
SET @denominator=1/@denominator;
INSERT INTO T1 VALUES('sp_upload finished');
GO
ALTER PROCEDURE "sp_process" @denominator FLOAT
AS
DECLARE @quotient FLOAT;
SET @denominator=1/@denominator;
INSERT INTO T1 VALUES('sp_process finished');
GO
ALTER PROCEDURE "sp_daily" @p1Deno FLOAT,@p2Deno FLOAT,@p3Deno FLOAT
AS
BEGIN TRY
EXEC sp_staging @p1Deno;
EXEC sp_upload @p2Deno;
EXEC sp_process @p3Deno;
END TRY
BEGIN CATCH
INSERT INTO T1 SELECT ERROR_MESSAGE();
END CATCH
GO
--Test Example
TRUNCATE TABLE T1;
EXEC sp_daily 1,0,1;
SELECT * FROM T1;
As we can see from the above modification, sp_daily calls sp_staging, sp_upload, sp_process in order. Sp_staging runs fine so it finishes. When it comes to sp_upload, error gets captured so the execution terminates. Anyway if you hope that the 3
called procedures work atomically(it is a pretty common business requirement), which means unless all of the three finish otherwise no one finishes, the TRAN block would help. Please see the below code.
ALTER PROCEDURE "sp_daily" @p1Deno FLOAT,@p2Deno FLOAT,@p3Deno FLOAT
AS
BEGIN TRY
BEGIN TRAN
EXEC sp_staging @p1Deno;
EXEC sp_upload @p2Deno;
EXEC sp_process @p3Deno;
COMMIT TRAN;
END TRY
BEGIN CATCH
ROLLBACK TRAN;
INSERT INTO T1 SELECT ERROR_MESSAGE();
END CATCH
GO
--Test Example
TRUNCATE TABLE T1;
EXEC sp_daily 1,0,1;
SELECT * FROM T1;
If you have question, feel free to let me know.
Best Regards,
Eric Zhang

MC.9 and MCY1 and Exception Handling in (Logistics Inf. Sys)LIS

Similar Messages

Maybe you are looking for