Well... classic first question would be, if you run this on a single node does the problem go away? Secondly, have you had your DBA monitor the session when it is hung?
-craig
"You can never have too many knives" -- Logan Nine Fingers
What kind of database are you accessing? Can the DBA monitor for usage on the file? Typically it isn't the job that is hanging it up, it is someone else accessing the table that is preventing the job from continuing,
The subject line indicates SQL Server. With sufficient access rights, you can see the individual threads and locks from the SQL Server Management Studio program.
Where are the locks coming from? If it is from the job itself, have you tried running on a single node as previously noted? That would eliminate the target as the source of the locks but would still lock if they are being generated on the source side.
-craig
"You can never have too many knives" -- Logan Nine Fingers
However, assuming the job itself is not the problem and the record lock is from something external, setting Isolation Level to "Read Uncommitted" should work.
If the entire table is locked, then you are probably out of luck, since Read Uncommitted only allows you to "get around" record level locks. Note that this will allow you to read "dirty" data, so use with caution.
</a>