Process Flow hangs

Question

I'm executing a process flow with several activities.
After each activity I check for status and error out if the activity fails. If the activity succeeds I go on to the next activity.
When I execute a map within the process flow, the process flow executes successfully only if the map is the last activity. The map functions to output data to a file.
The Process Flow hangs if after the execution of the map
a stored procedure is called. The stored procedure dynamically creates a DBLINK and updates a table.
When I cancel the execution of the process flow I see the map has successfully outputted all
records. But why hasn't it gotten to the stored procedure.
Each activity on its own works fine but in combination with each other they hang the process flow.

Answer 1

Mahesh,
I am assuming that RAB stands for Runtime Audit Browser.
The Runtime Audit Browser tells me how many records were
rejected but not which ones and why.
The debugger does not give adequate information in fact it does not issue a "break" where it should.
Are there any tools OWB provides for "catching", or
auditting data that cannot for whatever reason be extracted to a file.
I see that they have a mechanism for capturing problems with data coming from a file into a table. I don't see
where there is an explanation of error handling going from a table into a file.
Thanks!
Marion