Troubleshooting
Problem
Cognos portal appears to hang if the user performs any simple action
Symptom
Any navigation action is taking a very long time for the user. Users have to wait till any invoked actions are completed during which time the Cognos portal becomes unusable and users are not able to perform any other actions.
CPU utilisation also hits 99% for the java process invoked by the BiBusTKServerMain process
(BiBusTKServerMain process is involved with running the report.
While running the report new objects keep consuming Java heap memory which in turn spikes the memory utilisation. These new objects include report objects such as Lists, and or Crosstabs etc. for which memory is allocated within the Java heap.
Saving report outputs involve Authentication and Content Manager (CM) services are Java based processes and consume JVM memory.)
Cause
Audit Logging level for every component service is set to "Full"
Resolving The Problem
Set the Audit logging level to "Minimal" for every component service.
Steps:
1) In Cognos Connection:
Launch->IBM Cognos Administration->Configuration->Dispatcher and Services
Select the dispatcher. Under Actions click on Set properties->Settings.
2)Select Logging from the Category drop down.
User can see the Logging for different services. In the value select "Minimal" for every service.
Note:
If user wants to populate the Audit table COGIPF_USERLOGON then set the logging level for <Audit logging level for Content Manager service> and <Audit logging level for the dispatcher> to "Request".
Reference Technote # 1341343
Related Information
Was this topic helpful?
Document Information
Modified date:
23 June 2018
UID
swg21410195