Report error .

[cognoslearner1]

Hello All,

We have a large report . When trying to get the excel output I am getting error rsv-srv-0040.

When I checked the cogserver logs.

I noticed these below major things.

RSV-SRV-0040 The report server encountered an internal error
CCL-SRV-0513 The BIBusTKServer process ran out of memory.
Failure   RSV-SRV-0063 An error occurred while executing the 'asynchRun_Request' command

any idea what could be the issue ? I checked RAM and CPU utilization. Everything looks fine.

--Cognoslearner1

[MFGF]

Hello All,

We have a large report . When trying to get the excel output I am getting error rsv-srv-0040.

When I checked the cogserver logs.

I noticed these below major things.

RSV-SRV-0040 The report server encountered an internal error
CCL-SRV-0513 The BIBusTKServer process ran out of memory.
Failure   RSV-SRV-0063 An error occurred while executing the 'asynchRun_Request' command

any idea what could be the issue ? I checked RAM and CPU utilization. Everything looks fine.

--Cognoslearner1

Hi,

Sadly this is one of the common issues you see when trying to force Cognos to behave like an ETL tool. Cognos is a reporting tool, not something designed to be used for massive data dumps. Your report is blowing the inherent memory limit of your 32-bit Report Service, which means it must be trying to force massive amounts of data to be rendered. Your choices are:

1. Don't dump data out to Excel. Instead, find out what the end users really require from the data, and create a report that delivers these insights.
2. Use a data movement tool to dump the data from your database into Excel. Cognos is not designed as a data dump tool.
3. Switch your Report Service to 64-bit. This will introduce some limitations in the data sources your Cognos instance can use, though. For the report service to be 64-bit, all your packages need to use Dynamic Query Mode, which means ODBC / Native Client access to data is not supported.

Cheers!

MF.

[cognoslearner1]

Hi MFGF,

Thank you for the neat explanation.

So the only way to overcome from this problem is to shift from CQM to DQM so that BIBus process will get promoted from 2 gb to 4 gb this may solve problem temporarily. My report is presently extracting excel ouput with 95k rows. As suggested I will ask my business owners to use data extraction tool rather than using cognos as etl tool :)

Thanks ,
Cognoslearner1.

[cognoslearner1]

Hi MFGF,

One quick question : If I increase the number of BIBUS process for the batch report service. Is there any chance that the if the memory cross 2 gb for the CQM large excel output report  it will spawn another BIBUS and it will spread across BIBUS process and report can get completed successfully ?

Thanks,
Cognoslearner1

[MFGF]

Hi MFGF,

Thank you for the neat explanation.

So the only way to overcome from this problem is to shift from CQM to DQM so that BIBus process will get promoted from 2 gb to 4 gb this may solve problem temporarily. My report is presently extracting excel ouput with 95k rows. As suggested I will ask my business owners to use data extraction tool rather than using cognos as etl tool :)

Thanks ,
Cognoslearner1.

It doesn't work like that. The memory limit for a 64-bit process isn't 4Gb, it's more like 16Tb, so you have masses of headroom to work with.

What use is a 95,000 row report? Who is going to derive any value from it? Why would anyone want a report that big, unless it was to take the data and use it in another analytics tool? Why do that when Cognos is an outstanding Analytics tool in its own right?

Hi MFGF,

One quick question : If I increase the number of BIBUS process for the batch report service. Is there any chance that the if the memory cross 2 gb for the CQM large excel output report  it will spawn another BIBUS and it will spread across BIBUS process and report can get completed successfully ?

Thanks,
Cognoslearner1

No, that's not how it works. A report is rendered by the report service in a single thread.

Cheers!

MF.

[cognoslearner1]

Thanks for the valuable info.

In my above query sometimes the same report completes with success. May be if I run the same report for 5 times. It will fail for 2-3 times and gets completed with success in 1-2 times. I am really confused. If the BIBUS process consumes more than 2 gb then how can reports completed few times ?

[smiley]

Maybe the allocated memory from the first report run was not released yet, or the bibus was also running other reports.
If you want to know exactly how much it takes, make sure you´re the only user on the system, kill all bibusses, and wait for a single fresh one to start up.
Then start your report, and open up taskmanager and see how much the bibus allocates on memory.

Unless you want to start a new bibus for every report you fire, it does not really matter.
If you need to hang on to CQM, you have to bring down the memory consumption. 

[cognoslearner1]

DQM would be the best option in my case so that my report can take advantage of more BIBUS memory.

So from above discussion it means that , Please correct me if I am wrong .

1- In a 64 bit Cognos install with 32 bit execution mode BIBUS can run multiple reports.

2- Reports are run through a threads within BIBUS with a CAP of 2 gb for CQM.

3- Out of memory error will be thrown when report execution thread crosses 2 gb limit.So have to go with DQM option to overcome    memory issue.

So for example if there are 2 reports are running in parallel and 1 BIBUS is spawned handling two reports. If report1  execution thread is consuming 1.8 gb and report2 thread is consuming 0.6 gb of memory then both will complete with success as the both report thread consumes memory less than 2 gb within the single BIBUS .

Report execution threads within the BIBUS must be less than 2gb whereas BIBUS itself can exceed 2 gb right ?
I can see in my environment there are BIBUS process which are in a range of 2.1 - 2.5 gb memory utilization. For 64 bit install on 64 bit OS total BIBUS process size is 4 gb each  I had read this somewhere .. Is this my understanding is correct  ?

Thanks,
Cognoslearner1

[smiley]

Bibus is a 32 bits single threaded c++ executable.
Depending on configuration, it needs to handle 8 concurrent requests max.
"Number of low affinity requests for the report service during the peak period" = 8 (Default setting 10.2 and higher. It was 4 in older versions)

Any 32 bits process running on an X64 based OS, can allocate either 2 gig memory or 4 gig max.
https://msdn.microsoft.com/en-us/library/aa384219(v=VS.85).aspx
No idea if the bitkservermain.exe is LAA capable.