Hi All,
I have a requirement to create a audit report using the table COGIPF_VIEWREPORT.
But this table contains no data in database, other audit table are working fine excelpt this table.
Tried to configure dispatcher server settings in server configuration by setting the logging level to 'Basic' for the presentation service.
This solution is not working :(
Any other solutions,plz reply..
Thanks & Regards,
Naveen
I think there should be a separate logging setting for reporting as well.
Hi ,
In addition to that COGIPF_RUNJOB also not working.
try to schedule on job which contains 2 steps. this steps getting stored in COGIPF_RUNJOBSTEP. but job info not stored in COGIPF_RUNJOB. WHILE YOU DO RUN the job with run with option it getting stored.
Hi Guys,
which version of Cognos 8 are you talking about, because there have been bugs with logging reported on earlier versions of Cognos 8 ?
Regards
Filip
Mine is 8.4
Same here also..8.4
Naven,
have you set the logging parameter for the batch processes/services as well ? If I'm not mistaken the View Report is logged as a btach process. In general, I think it's a good idea to set the logging level to at least basic for all processes/services and afterwards you can lower the logging level for those processes you do not need.
Regards
Filip
Filip,
I have already tried setting logging levels of all processes to BASIC.
But no positve results.
Thanks,
Naveen
Isn't the report logging something where you also need an xml connection?
See page 87 "Set Up the Sample Report Usage Audit Report" of the "Administration and security guide" (ug_cra.pdf).
Hello there,
In my 8.3 environment all the logging parameters are set to Basic too.
I don't mean to be silly but maybe in your environment no one is actually viewing the reports? I believe that what triggers an entry in this table is the user to actually click the report name and view the report on screen, but the reports needs to be actually saved and not invoking the batch or interactive server process to execute the report. Open a few saved reports on screen then go back to the table.
I hope this helps, good luck with your issue.
Kleber
I am having a related issue with COGIPF_RUNJOB and am currently working with Cognos support to troubleshoot. However I ran across a few IBM technotes that you might want to try.
http://www-01.ibm.com/support/docview.wss?uid=swg21340771
http://www-01.ibm.com/support/docview.wss?uid=swg21343243
Oh, and if you have access to the Cognos bug portion of IBM.com there is a bug out on COGIPF_RUNJOB. The bug number is PK99429 or the url https://www-304.ibm.com/support/entdocview.wss?uid=swg1PK99429
I spent over 20 hours trying to figure out what the problem was. In the process I found just about every suggestion available on the internet (including this message thread) all were useful but none solved my problem.
What eventually fixed the logon issue was within Cognos Configuration. For some reason we had accidentally changed the "IP Version Host Name Resolution" from IPV4 addresses to IPV6 addresses. When we changed it back to IPV4 we resolved all our logging issues.
I'm still not totally sure what that value has to do with logging but I did discover that it fixed our issue.