ODI Handling DQ

If you have some SQL scripts to send output to some business users, especially for data quality issues or other information, how would you handle this. In case you do not have a data quality tool for that.

Step 1 : Prepare your data quality scripts.
Step 2 : Put those scripts into files.
Step 3 : Prepare PL/SQL or ODI code to read contents of those files. Send this script to your database, insert output to an ERROR table.
Step 4 : Read ERROR table by ERROR_CODE and loop it from beginning to end.
Step 5 : Send e-mail for each script, attach the appropriate file and mention how many rows are generated in this ERROR_CODE.
Step 6 : Continue with Step 4.

ODI Alert Mechanism

Today, I have read an article about recommendation about not using red lines (ko) in ODI packages. I just want to explain how I manage alert mechanism in ODI.
This is a sample package that I use in extraction phase.

NYOUG (New York Oracle User Group) Long Island SIG Webinar

I’m invited to New York Oracle User Group (NYOUG) for the below webinar. To register the event, please use this link.

7 December 2012 Friday, 3:00pm – 4:00pm EST (20:00 – 21:00 GMT+2)

Best practices with Oracle Data Integrator (ODI), do you know how flexible ODI is ? By Gurcan Orhan – Oracle ACE Director

Join us for a Webinar on December 7 Space is limited. Reserve your Webinar seat now at: https://www3.gotomeeting.com/register/714573278

ODTUG-Ask the Experts Panel – ODI

For the first time – ever – ODTUG is organizing a virtual panel session. Thanks for Cameron Lackpour for inviting me for that kind of important job. Here are some facts and how to register to this wonderful virtual event.

If you want to see complete page of Cameron just click here or here.