Restart Cognos services often

[chakrab2925]

hi all,
we have a production environment running on windows and the db on linux where i think there is a problem with. The issue is that we have to restart the services atleast once a week. The initial error would be
'CAM_AAA_Authenticate' failed

The only and quickest solution is restart C8 services.
My questions are:

1. How often these services have to be restarted. Is there anything specified by IBM.
2. Once the services freeze, where do i check for this. Does it spit out any logs.

I am a new bee to this application and all your help would be appreciated.
Thanks

 

[blom0344]

scan for .dmp files. These are huge and will clog your server. There is a setting that allows you to stop the generation of these dumps:

Steps to disable the .dmp file create:

1. Navigate to your installation path of Cognos
2. Open the \configuration directory
3. Locate the cclWin32SEHConfig.xml file and make a backup of it before changing.
4. Locate the following line and change 2:2 to 0:0

<env_var name="CCL_HWE_ABORT" value="0:0"/>

5. Save the file


Ties Blom

 

[toddl]

Some of my users get the 'CAM_AAA_Authenticate' and not being able to login using our AD SSO environment.

I've had an open call for about a year with Cognos on it, with no end in sight

However, we just restart the services on a daily basis and I've never had any problems.

Blom - Are you saying .dmp being created cause the CAM AAA errors? Or does the .dmp file contain information about the error?

Todd

 

[blom0344]

The .dmp are for analysis by Cognos. But not monitoring their growth will eat away all server space.
What is the 8 version and did you apply fixpacks? There is no end to the number of fixes after each major release..

Ties Blom

 

[toddl]

Hi Blom,

They've rejected my .dmp files, saying they were too big and unable to isolate a problem. They're still working on a fix to the AAA error.

I'm on 8.3.81.20 and have applied a ton of hot site fixes. We've basically decided that the AAA error isn't really a problem since we can restart the Cognos services on a daily error and not have any problems. If we needed 24/7 cognos availability, we'd be in a heep of problems, but we don't