tlwalker3
Active Member
Hi List,
We are experiencing an issue when running the R09110Z (Batch Journal Entry) report. When the job is running we intermittently encounter locking and deadlocks on the database. This will cause the R09110Z to hang or complete with failures in the batch. The locking occurs on the F0911 and/or F0911Z1. We've increased the timeout on the database to 200 seconds and this is helping, but the issue still occurs. The only thing we can do when this happens is to kill the process and restart it until it finishes the load. The issue is also aggravated when posting is running at the same time.
JDE Support did not know why this was occurring, and could only suggest running the report single threaded. This is not an option for us for two reasons. One is that we are converting large amounts of data and single threading this UBE would kill our conversion times. Also, we are running the multithreaded version of the R09801 posting application, so there would still be contention with the reports and table used.
Has anyone seen this issue before, and is there a fix. Any help would be appreciated.
We are experiencing an issue when running the R09110Z (Batch Journal Entry) report. When the job is running we intermittently encounter locking and deadlocks on the database. This will cause the R09110Z to hang or complete with failures in the batch. The locking occurs on the F0911 and/or F0911Z1. We've increased the timeout on the database to 200 seconds and this is helping, but the issue still occurs. The only thing we can do when this happens is to kill the process and restart it until it finishes the load. The issue is also aggravated when posting is running at the same time.
JDE Support did not know why this was occurring, and could only suggest running the report single threaded. This is not an option for us for two reasons. One is that we are converting large amounts of data and single threading this UBE would kill our conversion times. Also, we are running the multithreaded version of the R09801 posting application, so there would still be contention with the reports and table used.
Has anyone seen this issue before, and is there a fix. Any help would be appreciated.