Last updated on DECEMBER 30, 2008
Applies to:Oracle Communications Billing and Revenue Management - Version: 184.108.40.206.0
This problem can occur on any platform.
When a report is scheduled on the Business Objects Enterprise (BOE) Report Server it take a very long time for the report to allow an user to fill in the report's input parameters. The reason behind this is because BOE is running the report's SQL in the background. Eventually the SQL will fail because an input parameter is required (i.e. a start/end date). Once the report server fails to execute the report SQL it will return an error message. By acknowledging the error message the scheduler can go back and enter in an input parameter.
This is not a problem in a small database where there is a small amount of data because BOE returns an error message quickly. However, in a large database (i.e. production) this bug cause a big problem because it take a long time (approximately 30+ minutes) for the error message to be returned. At the same time the running of the report SQL in the background uses up resources on the report server thus affecting the scheduling of other report.
-- Steps To Reproduce:
Select a report that returns a large amount of data where input parameters are required. Attempt to enter input parameters and schedule the report against a large environment (i.e. a report that evaluates data against the event_t table).
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