Issues with report bursting

[raj_aries81]

I have a report filter with a list of hardcoded values for which the report needs to be bursted.The issue is I'm unable to see the reports for all values used in the filter.
However, when I reburst the report by hardcoding the missing values I could see the report output.

With this approach, I had to rerun the report multiple times to ensure all the values are covered. Can this be due to cognos setting on the number of DB connections while bursting or is this controlled by database.

Any help is highly appreciated !!

Regards
Raj

[New_Guy]

Hi,

I have a report filter with a list of hardcoded values for which the report needs to be bursted.The issue is I'm unable to see the reports for all values used in the filter.

Does the above statement means you are getting the values from a prompt and the report is not getting bursted for some values? If the filter is being by fed by a query, check the query, if it is getting all the values or not, or if the prompt is having static choices please check for errors in the used values.

Good luck
New guy

[raj_aries81]

Hi,

I have a report filter with a list of hardcoded values for which the report needs to be bursted.The issue is I'm unable to see the reports for all values used in the filter.

Does the above statement means you are getting the values from a prompt and the report is not getting bursted for some values? If the filter is being by fed by a query, check the query, if it is getting all the values or not, or if the prompt is having static choices please check for errors in the used values.

Good luck
New guy

Thanks New_Guy, yes its not bursting for some values, when I reburst the report for those missing values only I can see the report output.

I think its due to restriction on number of database connections.I will work with DBA to see  if there is any such property which is causing that issue

Regards
Raj

[New_Guy]

Hi,
If you are running the report for second time and you are able to get the missing values, this means that you have permissions on them. Are you the one running or scheduling the reports all the time or the users. If the users are running the report then it can be context set up issue in the database based on the user profile that is running the report. Number of connections cannot be the issue as it will throw an error if that  is the case.
Good luck
New guy

[raj_aries81]

Hi New_Guy,

Sorry for the late reply, as this is a monthly its on the back burner.

Worked with DBAs to understand if there is any limit set on the number of connections. Apparently, DB is configured to accept only 15 connections and hence report wont be generated  for all the values in the filter.

Another issue we noticed is even after the report runs for the first time for those 15 set of values sucessfully, the connections are still active for 'X' mins and when I rerun it for next 15, DB is rejecting the connection.

Will keep you posted once we fix this issue. Thanks for your inputs !!

Regards
Raj