Scenario:
I am trying to abort a session in the workflow monitor by using 'Abort' option.
But the status of the session is still being shown as 'Aborting' and remains same for the past 4 days.
Finally I had to request the UNIX team to kill the process.
Could anybody let me know the reason behind this as I couldn't find any info in the log file as well.
Solution:
- If the session you want to stop is a part of batch, you must stop the batch
- If the batch is part of nested batch, stop the outermost batch
- When you issue the stop command, the server stops reading data. It continues processing and writing data and committing data to targets
- If the server cannot finish processing and committing data, you can issue the ABORT command. It is similar to stop command, except it has a 60 second timeout. If the server cannot finish processing and committing data within 60 seconds, You need to kill DTM process and terminates the session.
As you said to kill the process we need to contact UNIX Admin.
But last time I coordinated with oracle team updated OPB table info related workflow status.
Comments
Post a Comment