Last updated on DECEMBER 14, 2016
Applies to:Oracle Reports Developer - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Environment configured with jobStatusRepository and/or jobRepository (e.g. High Availability) per instructions in:
How to Setup jobStatusRepository Feature in Reports 11g (Doc ID 858200.1)
Once the job count exceeds the maxQueueSize, you may notice that past Jobs are not in correct order in Reports Server Group Queue Status. Doing showjobs does not show the latest jobs on top in "Past Jobs" view.
2. Select Past Jobs
3. Select the Group
4. You see that the first page (10 jobs) are not the recent ones, but from previous times. The recent ones are embedded either in the middle or end of listing. It's inconsistent in terms of placement.
In a High Availability/cluster environment, if you perform a showjobs for each individual In-Process Reports Server, it will not show the most recent jobs either. It still displays previous/old jobs. The database instance where the jobs history is saved does not have problems. You can see the current jobs in the rw_server_job_queue table in the database.
It is observed that the sequence that is used to populate the ID column in the RW_JOBS table is cycled every 100000. Since the query used for the showjobs command is ordered by the ID column in descending order, every time the sequence cycles back to 1 the display will be incorrect because it will show the ID's around 100000 before the ID's with a value less than 100. Since maxQueueSize in this case is 8000, this situation will continue until the older jobs are deleted out. So if 10,000 reports are run per day and current sequence value is at 63661, then have about 4 days until the display will start showing older jobs instead of the most current jobs that have run.
Upgraded to Reports 11gR2.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms