This is more an observation than a question, to hopefully help someone else from some headaches in the future.
I am not a Cognos admin, but I do know a little. So our team performed an upgrade from 11.1 R3 to 11.1 R7 recently. Most things seemed to run okay, but certain reports were getting an error about the query service being busy. After much head to desk banging, it was discovered that some dispatcher properties related to JVM memory allocation had been reset to their default values. As a result, I believe reports that used more than a little local processing were throwing the query service busy errors (or something else cryptic).
I say all of that to let everyone know to be thorough about checking non-default properties that you have set in your environment, whenever upgrading. It is very possible that they could get overwritten during an upgrade.
In case anyone cares, the properties that were overwritten were:
- Initial JVM heap size for the query service (MB)
- JVM heap size limit for the query service
Thanks!