ODIExperts.com

The blog for Oracle Data Integrator ( ODI )

Killing session in ODI 11g

Hi everyone…

This post is about a something new on ODI 11g…

I must confess that  when I saw the first time I didn’t get the concept but now, it’s more clear!

I hope you all enjoy!

In ODI 10g we had this big issue of killing the job especially its big headache when we need to ping or disturb DBA . ODI 11g seems to handle this situation smartly by introducing new options called STOP NORMAL and STOP IMMEDIATE.

You can find this option under the running session.Lets look how this two options work.

image

STOP NORMAL

I am killing the running session using the option STOP NORMAL. The SID for this query is 143  and so I right click and click on Stop Normal

image

A pop up will be shown for  Stop Session dialogue and click OK to kill it.

image

After running a few test I have seen that Stop Normal takes time to kill the session and  after a while we get the Session Stopped dialogue. Generally in the Normal  kill command,  Oracle marks the query with status of Kill so most of the time the Oracle will wait for the operation or query to be processed and mark the query as Killed and pretty much the similar logic is being carried out for the STOP NORMAL, so this kill operation takes time.

image

image

My SID query also return nothing as the Session is killed in the Database too.

STOP IMMEDIATE

image

Similar to the Stop Normal the  Stop Immediate will ask the permission to be killed or not . Click OK for the confirmation.

image

Being an Immediate clause ,  the query is killed immediately.

image

Note:- This process can only work when the User used in Topology have the necessary Kill  permissions.

That is it! I hope be useful to all of you!

Thanks for visiting us!

8 Comments

  1. Woot! Thanks you very much for sharing your knowledge.

  2. Hi,

    I have 2 load plans A,B. A is Daily and B is on friday once.if A loads successfully then only B run on Friday.That is B depends on A.If A gets fail B has to populate past data.Thanks in advance.

  3. I deleted a session instead of killing (stop Normal) but it’s running background……please help me

  4. Hi,
    The session was execute from laptop with Local Agent, now I need killing this session from other PC, I have SUPERVISOR account but I can’t killing this session, show message ” This session is running from other Agent with same name”. How to stop this session?

    • Hi Martin,

      that is a normal behavior…

      This session isn’t running any more, even Operator shows that. Once the agent (local agent from other PC) was killed during execution, it doesn’t updated the Operator tables to “ended” status… Just delete the session. It is a “ghost” in the list, not exists anymore….

      Thank you for visit us!!!

  5. Hi Dude,

    I have a small requirement. Could you please let me know the approach.

    How to assign the Stored Procedure Output (Table Type) as an Source to the ODI Interface?

    Though my question is simple, I know it is little bit complicated. Thought you are the right person to ask.

    Thanks in Advance.

    Regards
    Chandrashekar.Ch

    • Hi,

      Let me try to help…
      As far as I know you can’t use the return directly from a table type output.. The only way there I can see in a fast view is, in a ODI procedure:

      1 Step) create a temporary table, storage the returned table (from stored procedure) in the source tab in the transaction 0. Use a anonymous pl/sql block
      2 Step) at source tab, transaction 0 select from the temp table
      at target, use the returned data….

      Does this work for you?

Leave a Reply

Required fields are marked *.