BOB: Business Objects Board
Not endorsed by or affiliated with SAP

Register | Login 

Want to sponsor BOB? 
Want to sponsor BOB? (Opens a new window)  

General Notice: BOB is going to retire...please see details here.
General Notice: No events within the next 45 days.

Tools to follow error


 
Search this topic... | Search DI: Performance and Tuning... | Search Box
Register or Login to Post    Forum Index -> Data Integrator -> DI: Performance and Tuning  Previous TopicPrint TopicNext Topic
Author Message
mbdsi
Forum Member
Forum Member



Joined: 01 Dec 2016

Posts: 2



PostPosted: Wed Mar 29, 2017 6:52 am 
Post subject: Tools to follow error

Hello all,

I join a project where they use BODS (Data Services) to sequence their data flow and use try/catch to list errors.

They feed a table for each flow with this technic and they ask me to find an another way to do that.

Does BODS doesn't have a tool to follow and see errors? Do we really need to use try/catch to have acces to error log ? I'm very surprised of this behavior.

Thanks by advance to help to see more clearly the situation.
Back to top
Marek Chladny
Forum Advocate
Forum Advocate



Joined: 27 Nov 2003

Posts: 19318
Location: Bratislava


flag
PostPosted: Wed Mar 29, 2017 7:06 am 
Post subject: Re: Tools to follow error

[Moderator Note: Moved from General Discussion to Data Integrator -> DI: Performance and Tuning]
Back to top
Nemesis
Forum Enthusiast
Forum Enthusiast



Joined: 08 Jun 2004

Posts: 1094
Location: London, England


flag
PostPosted: Wed Mar 29, 2017 7:47 am 
Post subject: Re: Tools to follow error

mbdsi wrote:
Does BODS doesn't have a tool to follow and see errors? Do we really need to use try/catch to have acces to error log ? I'm very surprised of this behavior.


You need to get your project to use the 'Validation' transform. Then you will be able to filter out your error records.

_________________
Contracting in London again.
Back to top
mbdsi
Forum Member
Forum Member



Joined: 01 Dec 2016

Posts: 2



PostPosted: Wed Mar 29, 2017 8:37 am 
Post subject: Re: Tools to follow error

Thanks, i will tell about it to my team and try as soon as possible. I'll come back to tell if it answer to our need.
Back to top
Nemesis
Forum Enthusiast
Forum Enthusiast



Joined: 08 Jun 2004

Posts: 1094
Location: London, England


flag
PostPosted: Wed Mar 29, 2017 8:41 am 
Post subject: Re: Tools to follow error

Here's a useful starting point:-
https://wiki.scn.sap.com/wiki/display/EIM/Data+Validation

_________________
Contracting in London again.
Back to top
ErikR
Forum Enthusiast
Forum Enthusiast



Joined: 10 Jan 2007

Posts: 1111
Location: Wellington, NZ


flag
PostPosted: Sun Jun 04, 2017 6:38 pm 
Post subject: Re: Tools to follow error

mbdsi wrote:
Does BODS doesn't have a tool to follow and see errors? Do we really need to use try/catch to have acces to error log ? I'm very surprised of this behavior.


To answer your question as stated - no, the try/catch functionality is not required to capture errors. These will end up in your error log regardless, though depending on the type of error the entries may be useful or not so much.

There is a difference between error logging, which is what the error log does of course, and error handling. If you have done any kind of programming, then the use of try/catch statements should absolutely not come as a surprise.

Without try/catch blocks, any error your ETL process encounters will be terminal, with your job execution halting right there and then. A Try/Catch block allows you to isolate the execution at whatever level your design requires. This can be an individual script, data flow or a more elaborate work flow or even the entire job itself. Once an error occurs, the catch block will allow you to take any measures required to handle this error.

Because error objects are contextual objects, the Catch block is also the only place in which you can trap the error metadata (e.g. error message, error context, error number, error timestamp) as these will be specific for the error caught in this particular Catch block. (Given the parallel nature of Data Services, it is entirely possible to have two parallel work flows that both trigger errors, therefore the catch block in each would capture the different error that occurred in each parallel stream.)

Once you have caught the error, possibly logged the error metadata in your own framework (e.g. a database table, a text file, etc.), perhaps did some e-mail notifications, you can then also include any steps that may be required to re-attempt the logic that failed, trigger something else, or just gracefully end the job all together. Whatever is required for your situation and design.

One thing to note that is that Data Services will consider the error as handled when it ends up in the Catch block. If you do nothing, the job execution will actually not be flagged as being erroneous - e.g. it will get a green light in your management console. Again, depending on your situation, you may want to manually raise an exception once you have "taken care of business" first.
Back to top
Display posts from previous:   
Register or Login to Post    Forum Index -> Data Integrator -> DI: Performance and Tuning  Previous TopicPrint TopicNext Topic
Page 1 of 1 All times are GMT - 5 Hours
 
Jump to:  

Index | About | FAQ | RAG | Privacy | Search |  Register |  Login 

Get community updates via Twitter:

Not endorsed by or affiliated with SAP
Powered by phpBB © phpBB Group
Generated in 0.0288 seconds using 17 queries. (SQL 0.0035 Parse 0.0009 Other 0.0244)
CCBot/2.0 (https://commoncrawl.org/faq/)
Hosted by ForumTopics.com | Terms of Service
phpBB Customizations by the phpBBDoctor.com
Shameless plug for MomentsOfLight.com Moments of Light Logo