COGNOiSe.com - The IBM Cognos Community

IBM Cognos 10 Platform => Cognos 10 BI => Cognos Administration => Topic started by: actcognosuser on 09 Sep 2022 10:31:10 AM

Title: Cogsever.log
Post by: actcognosuser on 09 Sep 2022 10:31:10 AM
Hi Users,

Does Cogserver.log save information for

1. Activity /reports run from My folders on the cognos connection
2. Analysis studio queries?

If it doesn't where is this information stored to troubleshoot any failures or long running queries?
Title: Re: Cogsever.log
Post by: MFGF on 09 Sep 2022 12:48:12 PM
Quote from: actcognosuser on 09 Sep 2022 10:31:10 AM
Hi Users,

Does Cogserver.log save information for

1. Activity /reports run from My folders on the cognos connection
2. Analysis studio queries?

If it doesn't where is this information stored to troubleshoot any failures or long running queries?

Hi,

Typically you would add an Audit database to your instance and configure auditing to start collecting activity on the server.

https://www.ibm.com/support/pages/how-configure-audit-reporting-cognos-analytics

Cheers!

MF.
Title: Re: Cogsever.log
Post by: cognostechie on 09 Sep 2022 02:00:27 PM
Quote from: actcognosuser on 09 Sep 2022 10:31:10 AM
Hi Users,

Does Cogserver.log save information for

1. Activity /reports run from My folders on the cognos connection
2. Analysis studio queries?

If it doesn't where is this information stored to troubleshoot any failures or long running queries?

There is a way to figure out which queries/containers are taking how much time which might tell you which queries are slow (presuming you have multiple queries and are trying to find out which ones are the culprit).

Turn on the Diagnostic Logging and enable 'Include Performance Details' in the report run options.

Run the report and it will show you which list/crosstab/chart took how much time.
Title: Re: Cogsever.log
Post by: actcognosuser on 09 Sep 2022 02:53:32 PM
Thank You all for your response. An Audit DB is not configured. One of the queries caused a lock on the DB tables. So we are
unable to figure out the user that ran the report.