Cognos Analytics

Cognos Analytics

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

 View Only
  • 1.  Cognos 12.1.2 optimization

    Posted 3 hours ago

    Hi ,

    We recently upgraded to Cognos 12.1.2 Interim Fix 1, but of recent we have some reports that keep failing with the below errors. These reports are submitted to run in the background either by users or they are scheduled.

    ReportServerHandler.missingProcess requestId:qvwdGswCsl2svddwsy4jhdMM8dqdqwwM4lG4sqhj sessionId:f:0:B38926E0A05C6BE482797C30632CB85B779A0564E009F09D4ABB3839F31D2205 nodeId:dcpcognos01:9300/p2pd/servlet/dispatch requestId:qvwdGswCsl2svddwsy4jhdMM8dqdqwwM4lG4sqhj http_host:DCPCOGNOS01:9300 soapaction:http://www.ibm.com/xmlns/prod/cognos/batchReportService/202507/.absolute requestURI:/p2pd/servlet/dispatch , 0: "30940", Handler trace back: [the_dispatcher] com.cognos.pogo.handlers.performance.PerformanceIndicationHandler [the_dispatcher] com.cognos.pogo.handlers.logic.ChainHandler [service_lookup] com.cognos.pogo.handlers.engine.ServiceLookupHandler [load_balancer] com.cognos.pogo.handlers.logic.ChainHandler [wrapped_lb_forwarder] com.cognos.pogo.auth.NewAuthHandler [lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler [batchreportservicechain] com.cognos.pogo.handlers.logic.ChainHandler [warptask_with_authenticate] com.cognos.pogo.handlers.logic.ChainHandler [do_batch_warp] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmtaChain] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmta] com.cognos.pogo.reportservice.BatchReportServerHandler


    Handler trace back: [the_dispatcher] com.cognos.pogo.handlers.performance.PerformanceIndicationHandler [the_dispatcher] com.cognos.pogo.handlers.logic.ChainHandler [service_lookup] com.cognos.pogo.handlers.engine.ServiceLookupHandler [load_balancer] com.cognos.pogo.handlers.logic.ChainHandler [wrapped_lb_forwarder] com.cognos.pogo.auth.NewAuthHandler [lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler [batchreportservicechain] com.cognos.pogo.handlers.logic.ChainHandler [warptask_with_authenticate] com.cognos.pogo.handlers.logic.ChainHandler [do_batch_warp] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmtaChain] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmta] com.cognos.pogo.reportservice.BatchReportServerHandler

    We have 2 windows servers. Both running Intel(R) Xeon(R) Gold 6326 CPU @ 2.90GHz   2.89 GHz  (16 processors) with 66.0 GB.


    BatchReportService set to : 

    Number of high affinity connections for the batch report service during non-peak period : 1
    Number of low affinity connections for the batch report service during non-peak period : 16
    Maximum number of processes for the batch report service during non-peak period : 8


    Number of high affinity connections for the batch report service during peak period : 1
    Number of low affinity connections for the batch report service during peak period : 16
    Maximum number of processes for the batch report service during peak period : 12

    Does anyone have any recommendations??



    ------------------------------
    Mayur Madoo
    ------------------------------


  • 2.  RE: Cognos 12.1.2 optimization

    Posted an hour ago
    Edited by Patrick Neveu an hour ago

    Hi Mayur,

    Is it safe to assume it was working before? Did you change something else before upgrading to CA v12.1.2 IF1?

    It might be useful to check around (before and after) the error in cognosserver.log if you have other Cognos errors.

    Check what kind of error messages you have around requestId:qvwdGswCsl2svddwsy4jhdMM8dqdqwwM4lG4sqhj.

    You write "We have 2 windows servers.", can you describe your architecture?

    The following value are too high (try to use a smaller value, such as 4):

    Number of low affinity connections for the batch report service during non-peak period : 16

    Number of low affinity connections for the batch report service during peak period : 16


    Would you be able to share report service value?

    Best regards,



    ------------------------------
    Patrick Neveu
    BSL Consulting
    IBM Champion
    ------------------------------



  • 3.  RE: Cognos 12.1.2 optimization

    Posted an hour ago

    Thanks for your reply.

    Yes was working before. nothing changed. We did an over-the-top upgrade. 

    seeing this error :

    2026-06-03T15:27:25.451+0200    ERROR    com.cognos.pogo.reportservice.RequestInvoker    [Default Executor-thread-91616]    28Gylhs2M9vC4ls9ljyC4hwj2lvh8wv8G2w4l4Cl        28Gylhs2M9vC4ls9ljyC4hwj2lvh8wv8G2w4l4Cl    NA    172.30.130.82    50327    LoginUser-149614924    AggAAAB+SylqAAAAAAoAAAD2nPjb0friz8wjFAAAAO1NS53AkSSV44YZlIrhP+sdiYwOBwAAAFNIQS0yNTYgAAAAs7boA14CmFVGBl7xMYSbMP1/JEI9KS92y8Z1jnIrL/A=    /v1/disp/analytics/sso/cisapi/bi/v1/disp    bi-service    31036    DPR-ERR-2074 Failed to receive a timely response from an external process with a PID 13352. Ensure that the process with a process ID 13352 is started. If the cause of problem cannot be determined, increase the logging level for the target service in the IBM Cognos Administration tool and reproduce the conditions that caused the error. If the problem persists, see the problem determination information on the IBM Cognos Support Portal page at http://www-947.ibm.com/support/entry/portal/Overview/Software/Information_Management/Cognos
    requestId:dqvw8wCGlwl29dj2s8Ghsjsdwywwd2syjvl844Mv
    sessionId:f:0:D9AF9A3B535D3D98DCB45DA93B4A4EA9CD8E7F381D58FECEDCB1903ED4B6FC4C
    nodeId:dcpcognos01:9300/p2pd/servlet/dispatch
    requestId:dqvw8wCGlwl29dj2s8Ghsjsdwywwd2syjvl844Mv
    http_host:-
    soapaction:http://www.ibm.com/xmlns/prod/cognos/reportService/202512/.absolute
    requestURI:-



    ------------------------------
    Mayur Madoo
    ------------------------------



  • 4.  RE: Cognos 12.1.2 optimization

    Posted 53 minutes ago

    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
    ------------------------------



  • 5.  RE: Cognos 12.1.2 optimization

    Posted 46 minutes ago

    Most of our reports are run during peak time. So assumed this was correct.



    ------------------------------
    Mayur Madoo
    ------------------------------