What would you recommend the values to be for both ReportService and BatchReportService
Original Message:
Sent: Thu June 04, 2026 03:26 PM
From: John Cusack
Subject: Cognos 12.1.2 optimization
Hi Mayur
In theory, you have potentially caused a different problem by making these changes. For example - if 16 batch reports are running and 16 users are logged running reports - you have 32 processes running -- at 2gb each -- you potentially are using 64gb of memory. Windows should use between 2 and 4gb. Cognos uses 8gb by default for the Query Service JVM -- another 8gb for the content mgr JVM and I feel there is another JVM in there somewhere as well. Add that up and you have exceeded the 66gb of memory on that box (or both boxes). I say "in theory" -- because as long as the reports do not hog the 2gb of memory -- you are ok because you won't hit the 2gb limit for any of the reports.
But at the same token, you may have hamstrung your environment for your users and they might start getting error messages that they didn't get before.
------------------------------
John Cusack
Analytica iQ
------------------------------
Original Message:
Sent: Thu June 04, 2026 03:08 PM
From: Mayur Madoo
Subject: Cognos 12.1.2 optimization
I'm running in 32B mode. 2 windows servers. Both running Intel(R) Xeon(R) Gold 6326 CPU @ 2.90GHz 2.89 GHz (16 processors) with 66.0 GB.
Yes i have users as well as schedules.
On average 690 users daily.
For reportService I have also set it to the following :
Number of high affinity connections for the report service during non-peak period : 1
Number of low affinity connections for the report service during non-peak period : 1
Maximum number of processes for the report service during non-peak period : 16
Number of high affinity connections for the report service during peak period : 1
Number of low affinity connections for the report service during peak period : 1
Maximum number of processes for the report service during peak period : 16
------------------------------
Mayur Madoo
------------------------------
Original Message:
Sent: Thu June 04, 2026 01:30 PM
From: John Cusack
Subject: Cognos 12.1.2 optimization
I think you are not taking into account your overall server environment. if you are running in 64b mode -- you potentially don't have enough memory to handle 16 batch report processes. What about your report processes? Users are actually logging into the system and running reports interactively right? How many users are you actually handling - aka - how many are logging in on a daily basis?
------------------------------
John Cusack
Analytica iQ
------------------------------
Original Message:
Sent: Thu June 04, 2026 01:21 PM
From: Mayur Madoo
Subject: Cognos 12.1.2 optimization
Thanks John.
I've updated both non peak and peak high and low affinity to 1 and Maximum number of processes for the batch report service to 16.
I also applied the following : https://www.ibm.com/support/pages/how-limit-how-many-requests-bibustkservermain-process-will-service-order-prevent-it-hanginggoing-orphan and also went with recommendations from another thread : https://community.ibm.com/community/user/discussion/configuration-recommendations-with-limited-hardware-resources#bmd6069b43-0d9d-481d-9b90-019bd834b708
------------------------------
Mayur Madoo
------------------------------
Original Message:
Sent: Thu June 04, 2026 12:52 PM
From: John Cusack
Subject: Cognos 12.1.2 optimization
Hi Mayur,
You need to lower your Affinity setting from 16 down to a smaller number (4 or 8) as Patrick has already mentioned. The error message you are receiving appears to be associated to the report processes running out of memory. When Cognos runs in 32b execution mode, each process is limited to 2gb (4gb under 64b mode).
A quick way to tell if this is actually happening is to look in the BIN directories for any core dumps (file size > 200mb). A core dump occurs when the BIBus (aka the report process) crashes because it attempted to exceed the memory ceiling set by the execution mode.
A typical report will consume less than 500mb at time of generation - so 4 x 500mb is 2gb and that is why the default usually works when it is set to 4 for 32b mode & 8 for 64b mode. But that is all dependent on the complexity and format of the report(s) in the environment.
Hope this is helpful.
------------------------------
John Cusack
Analytica iQ
------------------------------
Original Message:
Sent: Thu June 04, 2026 07:50 AM
From: Ramanujam Rajagopal
Subject: Cognos 12.1.2 optimization
Stop the batch report process for http_host:DCPCOGNOS01:9300 and test it again. Run the report on the other server, or stop all services on the DCPCOGNOS01 server. Clear the cache and consider manually upgrading the report.
------------------------------
Ramanujam Rajagopal
------------------------------
Original Message:
Sent: Wed June 03, 2026 10:11 AM
From: Mayur Madoo
Subject: Cognos 12.1.2 optimization
Most of our reports are run during peak time. So assumed this was correct.
------------------------------
Mayur Madoo
------------------------------
Original Message:
Sent: Wed June 03, 2026 10:04 AM
From: Patrick Neveu
Subject: Cognos 12.1.2 optimization
Mayur,
The non-peak period (during the time usually) is when Cognos Analytics to be very busy.
At this time, you have:
Maximum number of processes for the batch report service during non-peak period : 8
Maximum number of processes for the batch report service during peak period : 12
You should have the opposite (8 for peak and 12 for non-peak):
Maximum number of processes for the batch report service during non-peak period : 12
Maximum number of processes for the batch report service during peak period : 8
Best regards,
------------------------------
Patrick Neveu
BSL Consulting
IBM Champion
------------------------------