3 Ways to Optimize Cognos Timeout Settings

February 5, 2015     Tips & Tricks

If you're trying to optimize your Cognos timeout settings, we've outlined three of the most common properties that might require adjustments at the dispatcher level in Cognos administration. 

#1: Maximum execution time for the report service (seconds)

  • This is the maximum amount of time that an interactive report will be allowed to run before it is killed by Cognos
  • Default is 0 (unlimited)
  • Some customers change this to a fixed value in order to prevent runaway reports (this may typically be set at 3600 seconds) 

#2: Maximum execution time for the batch report service (seconds)

  • This is the maximum amount of time that a batch (scheduled) report will be allowed to run before it is killed by Cognos
  • Default is 0 (unlimited)
  • As with the previous property, some customers change this to a fixed value in order to prevent runaway reports

#3: Queue time limit of the report service (seconds)

  • This is the maximum amount of time that a report is allowed to wait in the queue when all threads on all dispatchers are busy
    • If an execution thread doesn't become available in the allotted time, the report request will fail with error DPR-ERR-2002: "Unable to execute the request because there was no process available within the configured time limit"
    • Most of us have probably seen this error many, many times over the years
  • Default is 240 seconds (4 minutes)
  • Some customers increase this value in order to prevent report request failures during busy periods
    • However, if DPR-ERR-2002 errors occur frequently in an environment, it's often a sign that the environment is generally underpowered, poorly tuned, or both

OPEN