Cognos Analytics

Cognos Analytics

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

 View Only

  • 1.  Jobs are just in executing status

    Posted Thu August 04, 2022 09:42 AM

    Hi,

    In recent days our cognos server is struggle to run jobs sometime. I mean just it is in executing status and after that non of the jobs were running. fails even when we try rerun. It is happening irrespective of any jobs any time. Especially in active reports. We are seeing the below error only when jobs get stuck. Also once jobs were stuck after that cognos is not establishing any connections to datasource until we restart the cognos.

    Is there any other way we can just close jobs and start as fresh ?? without restarting the whole cognos service ?

    Any help! Thanks



    ------------------------------
    Ramesh Kaliyaperumal
    ------------------------------

    #CognosAnalyticswithWatson


  • 2.  RE: Jobs are just in executing status

    Posted Thu August 04, 2022 09:46 PM
    You may try it by expending the executing job details and noting down the process id, Tracking down the process id in OS, and terminating the associated BIBusTKServer process. Once the process is completed completely then re-run the job. Hope it helps.

    ------------------------------
    Noor Ansari
    ------------------------------

    Original Message


  • 3.  RE: Jobs are just in executing status

    Posted Fri August 05, 2022 02:09 AM
    Edited by System Admin Fri January 20, 2023 04:40 PM
    If the problem persists you can also try to drop all NC tables in the audit database. This might be a solution for stuck jobs but you will loose run history details for all jobs.

    There's a script in <install-dir<\configuration\schemas\delivery\<db-vendor>\NC_DROP_xx.SQL

    See https://www.ibm.com/support/pages/how-use-ncdrop-script-cognos-analytics-11

    ------------------------------
    Robert Dostal
    Team Leader BI
    GEMÜ
    Ingelfingen
    ------------------------------

    Original Message


  • 4.  RE: Jobs are just in executing status

    Posted Fri August 05, 2022 03:41 AM

    Hi Noor,

    We are seeing more than one BIBusTKServerMa process running in OS level. So how to know which process id to kill exactly. 

    As you mentioned above, Can you share the steps to identify PID in cognos executing job details ? I checked and i couldn't find in the admin console when job were executing.

    Thanks.



    ------------------------------
    Ramesh Kaliyaperumal
    ------------------------------

    Original Message


  • 5.  RE: Jobs are just in executing status

    Posted Fri August 05, 2022 05:15 AM
    Hi Ramesh,

    In Cognos Administration, you can see the Process ID (PID) for a report listed as Waiting.
    In Manage / Activities, you cannot see the Process ID.
    Note: the PID listed in Manage / Activities should be available in v11.2.3.

    Best regards,

    ------------------------------
    Patrick Neveu
    Positive Thinking Company
    ------------------------------

    Original Message


  • 6.  RE: Jobs are just in executing status

    Posted Fri August 05, 2022 06:38 AM

    Hi Patrick,

    I could able to see PID number when i run the report. But PID is unavailable when i run jobs. Any guess ?

    Thanks



    ------------------------------
    Ramesh Kaliyaperumal
    ------------------------------

    Original Message


  • 7.  RE: Jobs are just in executing status

    Posted Mon August 08, 2022 08:39 AM
      |   view attached

    This is what i am seeing . Process ID:unavailable. Attached screenshot for reference.

    Also let me know why jobs gets hang or just in executing status.

    Is it due to the issue from cognos side or data source side ?

    Thanks



    ------------------------------
    Ramesh Kaliyaperumal
    ------------------------------

    Original Message


  • 8.  RE: Jobs are just in executing status

    Posted Tue August 09, 2022 05:39 PM
    Edited by System Admin Fri January 20, 2023 04:43 PM
    This process needs to be terminated in the BIBusTK server process that is linked to the job. You may try to identify this job id in the job description.
    Once the process is completed completely then re-run the job.
    Thanks for the help.

    ------------------------------
    captain jhoni
    ------------------------------

    Original Message