Difference between Stop and Abort in Informatica

Abort Request:
1. User sends the abort request either through workflow monitor or PMCMD utility.

2. It immediately kills the DTM process and user been notified for session aborted.
3. Later, it fires a request to the source database, waits for the source database to roll-back.
4. It fires a request to the target database, waits for the target database to roll-back.
5. It fires a request to the Informatica repository database to release the locks on session object.


Note: Each session uses SHARED/LOCKED memory blocks, but the ABORT function kills just the CODE threads, leaving the memory LOCKED and SHARED and allocated.

Stop Request:
1. User sends the stop request either through workflow monitor or PMCMD utility.
2. It fires a request to the source database, waits for the source database to roll-back.
3. It then cleans up the buffers in memory by releasing the data.
4. It fires a request to the target database, waits for the target database to roll-back.
5. It fires a request to the Informatica repository database to release the locks on session object.
6. It immediately kills the process DTM process and user notified for session aborted.

Note: The bigger the data in the source query, the more time it takes to "roll-back" the source query, to maintain transaction consistency in the source database. So when ever a request is passed, it waits for the entire process to roll-back before notifying the user.