Audit database (no enties are added)

[Rajesh_Vanam]

What is logging level did u set in Cogno connection?

[Plantje]

I had everything to basic.

However, if I go to the server, to the bin directory in the Cognos location and start logconsole.exe and logviewV2.exe I can pull up some logging of the server. However, it seems to pull it all from the text logging; the database remains empty at all times. Ciber, are you sure you always need both a text logging AND a database logging entry in Cognos configuration if you want to use database logging.

Further it has come to my attention that what we are looking for is not only logging of the server, but also activity monitoring. Am I looking in the entire wrong direction if I want to see the users currently logged in and what queries they are running?

[Plantje]

We have logged a service request for this. Someone from Cognos gave the following reply:
"Ensure ipfclientconfig.xml  file does NOT exist in configuration folder (.sample files and other files do not matter, just the ipfclientconfig.xml)."

In our case the file WAS there. I renamed it to ipfclientconfig.xml.old, restarted the Cognos service and immediately we saw logs being entered in the database. I have asked them how and why the file was there in the first place, just to know what was going on. And the next thing is of course that I have to work with the audit package and get that figured out. But that should be a piece of cake now!

Enjoy your holidays everybody!

[ciber]

Plantje,

Thanks for your info / CALL request.
At our production server the ipfclientconfig.xml file was existing (the Server Administrator told me it wasn't, but it was....)
So, when we deleted the file, the Audit entries where there  .

I don't know if you need both, but the file logging is default (I never tried to delete it, but why do you want so?)
Only when you need to use the Audit functionality (and why don't you want it, it give you good information) I know you need to add an entry to the Cognos Configuration.
The logviewV2.exe gets the information from the text file.

(?? Why doesn't have IBM/Cognos this information on the Cognos Forum ??)

(Sorry for my late reply)

ciber

[Plantje]

Plantje,

Thanks for your info / CALL request.
At our production server the ipfclientconfig.xml file was existing (the Server Administrator told me it wasn't, but it was....)
So, when we deleted the file, the Audit entries where there  .

Nice! To be honest: I'm pretty confident that I didn't rename the file myself. But then again...perhaps in some effort to get it to work. I know that it wasn't by default there when I installed 8.4.1 last week.

I don't know if you need both, but the file logging is default (I never tried to delete it, but why do you want so?)
Only when you need to use the Audit functionality (and why don't you want it, it give you good information) I know you need to add an entry to the Cognos Configuration.
The logviewV2.exe gets the information from the text file.

I deleted it at some point in an effort to get logging to the database working. I thought perhaps the system would get mixed up with two areas to store logging.

(?? Why doesn't have IBM/Cognos this information on the Cognos Forum ??)

Good question!

(Sorry for my late reply)

ciber

Nevermind that! It's just nice to hear other people were helped by it as well!

[johnpenna]

look in the IBM user guide, you need to enable logging on the dispatcher in cognos connection...By default they are set to minimal, you have to change them to basic..Check the doc on the IBM site,it shows you how to do it...When you change from minimal to basic you need to restart the services...

It should work ..I had the same problem and now it works fine..

[hiddenkirby]

We have logged a service request for this. Someone from Cognos gave the following reply:
"Ensure ipfclientconfig.xml  file does NOT exist in configuration folder (.sample files and other files do not matter, just the ipfclientconfig.xml)."

In our case the file WAS there. I renamed it to ipfclientconfig.xml.old, restarted the Cognos service and immediately we saw logs being entered in the database. I have asked them how and why the file was there in the first place, just to know what was going on. And the next thing is of course that I have to work with the audit package and get that figured out. But that should be a piece of cake now!

Enjoy your holidays everybody!

So far this sounds identical to the issue we are having.
We had cognos audit logging to a database working just fine .. then we upgraded the oracle database to oracle11g RAC configuration.

since then we were unable to successfully log to a db.

I do not have that file in my configuration directory.. on any of my cognos servers.  (yes to a .sample though)

Exact same behavior for us...  created tables just fine. correct user privelages. no errors anywhere. No rows populating in the log tables.

any other ipf config files i need to look out for?

Thanks,
    Kirby

[Plantje]

Do you have the logging in a separate database schema?

[cognos_users]

check  if there is any 'ipfclientconfig' file under c8 location>configuration. If it exists, then tracing is going on which is the reason for the logs not being written on to audit dbase.

[Plantje]

check  if there is any 'ipfclientconfig' file under c8 location>configuration. If it exists, then tracing is going on which is the reason for the logs not being written on to audit dbase.

As you can see in my reply on 25 Dec 2009 02:29:42 AM  this already has been suggested. For some people it is a solution for others there are some other issues.

[A152257]

i'm also having the exact same problem where the audit database  and the tables are not being updated..

[Plantje]

Apart from the answers provided here, I don't have any additional information.

Did you check everything that is being suggested here?

[jharmor]

Similar problem here.
On our companies Cognos development box the application stopped writing data to the audit tables about a month ago. The environment is Cognos 8.4 FP2, AIX 5.3 DB2. Cognos is still able to read the data that is in the Audit tables. I had the DBA ensure that we haven’t run out of room in any of the tables and none of the logs are full. We have stopped and restarted the Cognos services and the DB2 database. I had the DBA write a record to one of the tables using the Cognos application username and password and I have ensured that the configuration settings for each dispatcher have the logging levels all set to request. Where else can I look for trouble shooting this problem? Also based on some other posts I verified that ipfclientconfig.xml doesn’t exist in the configuration directory.  The installation is the same on our production box and that system is logging away just fine in the audit tables.
Thanks…

[Plantje]

Perhaps a long shot: some Windows updates installed somewhere?

[jharmor]

Update to earlier post. Created a new audit database and pointed the configuration to it. Then stopped and restarted the system. Cognos created all the Audit tables; but will only log data to the COGIPF_THRESHOLD_VIOLATIONS table. All the other tables remain empty. Still can't find the problem.