jdesmm
Well Known Member
We have two custom reports. One was designed from scratch and has been in Production since we went live (Dec. 2001). It looks at inventory and sales information, and is definitely a beefy report that sometimes takes a while to run, but we typically have not had any problems with it.
The second report is a new copy of the R04423B - Open A/P Details with Aging. The report copy was modified to look up related purchase order and sales order information via simple table I/O select/fetch next and fetch singles. Where select is used, close is also used. The report ran a little slowly in DEV, but no more than a few minutes. When we promoted the report to the test environment and a user ran it, the report ran for over 2 hours and appeared to conflict with the first report.
Both reports showed that they were processing but had taken over 2 hours. It didn't make sense to us how they could be conflicting, as they are running over business data in two separate environments (PROD and PY), but when we killed the second report, it freed up the first report, which then completed normally.
Is there any possibility that the conflict could be coming from a clash in accessing the system database? Has anyone ever seen one report hang up another in different environments? The database showed no deadlocks, no errors. Neither did the jde.log.
Any insight greatly appreciated!
The second report is a new copy of the R04423B - Open A/P Details with Aging. The report copy was modified to look up related purchase order and sales order information via simple table I/O select/fetch next and fetch singles. Where select is used, close is also used. The report ran a little slowly in DEV, but no more than a few minutes. When we promoted the report to the test environment and a user ran it, the report ran for over 2 hours and appeared to conflict with the first report.
Both reports showed that they were processing but had taken over 2 hours. It didn't make sense to us how they could be conflicting, as they are running over business data in two separate environments (PROD and PY), but when we killed the second report, it freed up the first report, which then completed normally.
Is there any possibility that the conflict could be coming from a clash in accessing the system database? Has anyone ever seen one report hang up another in different environments? The database showed no deadlocks, no errors. Neither did the jde.log.
Any insight greatly appreciated!
