In WebSphere Studio Asset Analyzer, it is not a good idea to have DMH0700 placing work on the queue while DMH6000 is trying to take work off the queue.
Resolving the problem
Both processes are designed to do very granular commits (ie, DMH0700 on each successful work request queued, DMH6000 at least on every file processed). There is, however, a high likelihood of conflict if DMH6000 is doing a large cascade delete due to a rescan.
Many shops allow DMH0700 to run any time, but schedule DMH6000 for earlier morning run, to minimize the conflict potential.