What's the difference between Stopping and Aborting the session

Jon and sham are very good friends. Jon is working as a informatica developer and he is very good at it.

Sham wants to learn informatica and he is taking help of his good friend Jon. Jon is very happy teaching him and answering his questions.

So they decided to meet up daily for an hour or so and discuss and teach informatica to Sham.

Today they are discussing about difference between Stop and Abort of informatica.Today is sunday morning and both of them are sitting

in garden of Jon; under a tree sipping coffee and the climate is really woderfull.

Lets see what they dicussing,

Sham: Yestarday i saw these two options,stop and abort in workflow monitor of informatica.Whats the difference bewteen them??

Jon:  (With a smile) tell me what both words mean according to dictionary.

Sham: (sham googled(every one do the same!!!!!) and came up with these meaning)

       Abort means:'bring to a premature end because of a problem or fault'

       Stop means:(of an event, action, or process) come to an end.

Jon: So let me explain you difference they cause in informatica based on the meaning you derieved.

     (sipped coffee and started) see each session in informatica uses SHARED/LOCKED memory blocks.

     Abort function just kills the code threads.

Sham:So do you mean to say that, menory which is  LOCKED or SHARED are allocated to that process for ever!!!!

Jon: you got it. That space is gone. But there is a good news,you can recover it.

Sham: How!!

Jon: All you need to do is to warm boot/cold boot(restart) the informatica server machine. AIX operating system is an expection.

Sham: ha ha ha...thats really bad right...really too bad.

Jon: This will cause our informatica server to run slower over time as there will be not enough memory to allocate to new sessions.

Sham:Yes abort will do a premature end.. then how about STOP option.

Jon: Its a very decent call. First it will request to datbase to stop running the source query and waits for its roll back.

     Then it will clean the buffers in memory so that data remain unwritten to database.

Sham:Good...

Jon: listen its not the end. Bigger the memory allocated to session more time it will take to clean up the buffers.

     Then it wait for the target to rollback higher the commit point more data target DB has to roll back.

     Finally it will shuts down the session.

Sham: (scraching his head)Such a long process it is...... It will take alot of time right to make the process to come to a proper end.

Jon:Ya...if you really need to stop your session you need to ask your DBA to kill the source query in DATABASE.

Sham: How it helps.

Jon: It will send EOF(end of file) downstream to informatica and infa will take less time to stop session.

Sham: I have a quesiton, what happen if i abort a session and it got aborted and i restart it again.

Jon: Then you please forget any hope of performence in source database.you are compiting against a defunt(no loger existing query)  query for resources that is still rolling back.


Sham:Thank u very much jon..This discussion really helped me to know the difference thanks again.