does not produce any report for first run after report server reboot
after the server reboot, the first report job run comes up with jobid = 0, which does not produce any report with error message of 'binding failure'. the second run with jobid = 1, will produce. We have been with this for many years, with temp arrangement that everytime after server reboot, the admin manually runs any report to leave users for the second run.
I would like to see any other Oracle Report site has any better way to handle it.
thanks for any reply.