Resource type TDIPLOCK: waits for transient data intrapartition requests

If you have a task suspended on resource type TDIPLOCK, with a resource name that corresponds to a transient data queue name, the task has issued a request against an intrapartition transient data queue. Another task is already accessing the same queue and the waiting task cannot resume until that activity is complete.

If tasks frequently get suspended on resource type TDIPLOCK, you need to determine which other transactions use the same intrapartition destination. You might then consider redefining the intrapartition destinations.

For more information about the constraints that apply to tasks writing to intrapartition destinations, see Transient data control.



dfhs117i.html | Timestamp icon Last updated: Monday, 5 June 2017