If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Cogserver.log and Audit not getting updated

Started by cognoslearner1, 24 Oct 2017 07:38:55 AM

Previous topic - Next topic

cognoslearner1

Hi All,

Recently  Cogserver.log and Audit db stopped updating. I had checked logging levels for CM,dispatcher,batch report and report services which are set to "Basic". Before it stopped writing audit and cogserver.log I can see below message in log file

server.Audit.IPF        Execute AuditDatabaseConnection jdbc:oracle:thin:@(DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=XXXX) (PORT=1521) ) (CONNECT_DATA= (SERVICE_NAME=XXXX) ) )    Failure  Log Server generic error        <parameters><item name="DB URL"><![CDATA[jdbc:oracle:thin:@(DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=XXXX) (PORT=1521) ) (CONNECT_DATA= (SERVICE_NAME=XXXX) ) )]]></item><item name="DB SQL Exception"><![CDATA[Failure to insert in COGIPF_RUNREPORT, No more data to read from socket]]></item></parameters>

What would be the cause ? I have checked IPFclientconfig and that is not enabled.

Thank you.

misscognos

Does restarting the service fix the problem even if it is a temporary fix?

Issues on the Oracle side?

Do other tables update?

Does your jdbc driver match the Oracle server version exactly?

Are you able to attach the cogserver.log?

Was everything working before? Do you have data in that table?

cognoslearner1

Hi ,

Thanks for the suggestions. I restarted Cogno services and audit started getting populated .

Thanks a lot.

misscognos

My guess would be something killed the log service.... If it happens again it would be useful to see the log and what was written to it before the issue..

MMcBride

When Cognos is connected to the Content Store, if the DBMS is restarted or communications is interrupted the connections will "self heal" or try to reconnect.

The Audit connection is a little different, when communication is truncated to the Audit store or the DBMS is restarted, you must restart Cognos to re-establish these connections and allow the Audit logging to begin again.

In the past I have had these same type of problems and it turned out the DBMS was being recycled for some reason early in the morning - but the Cognos services were not being restarted - this resulted in my Audit logs not being written.
Once I put in a policy stating any time the Audit DBMS was restarted the Cognos Services must be restarted my Audit logs became much more reliable.