Tuesday, December 17, 2013
ODI 12c debugger : row-by-row debugging
ODI is a set-based data processing tool. It does not automatically switch to a row-by-row mode for debugging. But what you *can* do is to use the IKM SQL Incremental Update. This will cause the engine to do row-by-row processing and voila! you can do row-by-row debugging.
Wednesday, December 4, 2013
ODI debugger - Part 2
Descendant Sessions debugging
In ODI one Session can launch a child Session in different ways.- user can have an OdiStartScen tool invocation either in Package or Procedure
- user can have an OdiInvokeWebService invocation either via Package or Procedure
- user can have an OSCommand or OdiOSCommand tool invocation calling startscen.sh/cmd or restartsess.sh/cmd either in Package or Procedure
There is another subtle gotcha. When ODI Studio notifies you that a child Session is starting, if user chooses not to attach Studio to that debuggable Session, then user *will not receive any notifications for any debuggable child Sessions started by this child Session*
Starting Session in debug mode
All the ways for starting a Session have debugger flags that user may set. This includes startscen.sh/cmd, restartsess.sh/cmd, ODI incoming web service (a.k.a public web service), OdiStartScen tool, SDK APIs and Studio.
Subscribe to:
Posts (Atom)