Cognos Analytics

Cognos Analytics

Connect, learn, and share with thousands of IBM Cognos Analytics users! 

 View Only
Back to discussions
Expand all | Collapse all

Error on cognos Report "Query Service is busy"

  • 1.  Error on cognos Report "Query Service is busy"

    Posted Tue February 26, 2019 07:55 AM
    I'm facing issue on cognos. I create a report base on data module but when I run the report is take time and it's give me the mensagem below.

    "XQE-CON-0007 XQE error encountered: Your request could not be completed because the Query Service is busy. Try again later. If the problem persists, contact your system administrator.
    RSV-SRV-0042 Trace back:
    RSReportService.cpp(762): XQEException: CCL_CAUGHT: RSReportService::processImpl()
    RSReportServiceMethod.cpp(253): XQEException: CCL_RETHROW: RSReportServiceMethod::process(): asynchWait_Request
    RSASyncExecutionThread.cpp(873): XQEException: RSASyncExecutionThread::checkException
    RSASyncExecutionThread.cpp(317): XQEException: CCL_CAUGHT: RSASyncExecutionThread::runImpl(): asynchRun_Request
    RSASyncExecutionThread.cpp(918): XQEException: CCL_RETHROW: RSASyncExecutionThread::processCommand(): asynchRun_Request
    Execution/RSRenderExecution.cpp(600): XQEException: CCL_RETHROW: RSRenderExecution::execute
    Assembly/RSDocAssemblyDispatch.cpp(343): XQEException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssembly
    Assembly/RSLayoutAssembly.cpp(79): XQEException: CCL_RETHROW: RSLayoutAssembly::assemble
    Assembly/RSDocAssemblyDispatch.cpp(450): XQEException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchChildrenAssemblyForward
    Assembly/RSReportPagesAssembly.cpp(185): XQEException: CCL_RETHROW: RSReportPagesAssembly::assemble
    Assembly/RSDocAssemblyDispatch.cpp(388): XQEException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssembly
    Assembly/RSPageAssembly.cpp(314): XQEException: CCL_RETHROW: RSPageAssembly::assemble
    Assembly/RSDocAssemblyDispatch.cpp(388): XQEException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssembly
    Assembly/RSTableRowAssembly.cpp(177): XQEException: CCL_RETHROW: RSTableRowAssembly::assemble
    Assembly/RSDocAssemblyDispatch.cpp(388): XQEException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssembly
    Assembly/RSTableCellAssembly.cpp(151): XQEException: CCL_RETHROW: RSTableCellAssembly::assemble
    Assembly/RSDocAssemblyDispatch.cpp(450): XQEException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchChildrenAssemblyForward
    Assembly/RSDocAssemblyDispatch.cpp(388): XQEException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssembly
    RSResultSetIterator.cpp(1515): XQEException: CCL_RETHROW: RSResultSetIterator::retrieveData
    QFSMasterDataset.cpp(278): XQEException: CCL_RETHROW: QFSMasterDataset::GetPartialDataset
    XQEConnector.cpp(300): XQEException: CCL_THROW: XQEConnector::send"

    ------------------------------
    Manuel Chau
    ------------------------------

    #CognosAnalyticswithWatson


  • 2.  RE: Error on cognos Report "Query Service is busy"

    Posted Wed February 27, 2019 06:25 AM
    Hi Manuel,
    This error message 'QueryService is busy' is a indication that basically your QueryService maximum heap size value is too low to be able to handle the processing of your report. If you have enough physical RAM available on your server, and if the QueryService max heap size is set at the default values ( 1024 or 4096 or 8192 depending of the CA version you're using), you might want to increase this value by setting it to a minimum of 4096 and a maximum of 10240 or 12288 . This change will require to restart the QueryService to be taken in account. 
    Now on another hand, if the QueryService max heap size is already at a relatively high value, the error message 'QueryService is busy' might indicates that there's a 'local processing' occurring at the Cognos server level instead of being done at the datasource/database level. This would mean that your report (mostly the queries used within your report) would need to be reviewed in order to have their generated SQL to be better pushed down to the datasource ( using more native DB translatable functions in the filters or expressions, checking that ensemblist operators Union,Except ... are pushed in the native SQL, etc...).
    Hope this could help a bit.
    Cheers

    ------------------------------
    CESAR CARDORELLE
    ------------------------------

    Original Message