Comments on: Memory leaking in Cognos 8.3 BI http://ykud.com/blog/cognos/memory-leaking-in-cognos-8-3-bi Tue, 31 Jan 2012 00:11:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: DesiCresnet http://ykud.com/blog/cognos/memory-leaking-in-cognos-8-3-bi/comment-page-1#comment-21134 DesiCresnet Tue, 17 Nov 2009 15:18:21 +0000 http://ykud.com/blog/?p=252#comment-21134 Sorry Sachin...gone to India...for a vacation. Those 2K, 3K logon are for Scheduler credentials...no harm.. when you run Jobs thru macros...those will get logged... Sorry Sachin…gone to India…for a vacation. Those 2K, 3K logon are for Scheduler credentials…no harm.. when you run Jobs thru macros…those will get logged…

]]> By: Sachin J. Kulkarni http://ykud.com/blog/cognos/memory-leaking-in-cognos-8-3-bi/comment-page-1#comment-20635 Sachin J. Kulkarni Wed, 28 Oct 2009 18:36:13 +0000 http://ykud.com/blog/?p=252#comment-20635 I am not sure if you have auditing turned on in your environment. If you do, do you see several hundred logon for users? If you actively use it, may be check for your id. For an active user, who runs macros/events we see about 2k to 3k logons in an 4 to 8 hr window! And each of the logon is alomst a minute after the previous one. I am not sure if you have auditing turned on in your environment. If you do, do you see several hundred logon for users? If you actively use it, may be check for your id. For an active user, who runs macros/events we see about 2k to 3k logons in an 4 to 8 hr window! And each of the logon is alomst a minute after the previous one.

]]> By: ykud http://ykud.com/blog/cognos/memory-leaking-in-cognos-8-3-bi/comment-page-1#comment-20633 ykud Wed, 28 Oct 2009 17:33:49 +0000 http://ykud.com/blog/?p=252#comment-20633 Hi Sachin. We weren't using Access Manager. Hi Sachin.
We weren’t using Access Manager.

]]> By: Sachin J. Kulkarni http://ykud.com/blog/cognos/memory-leaking-in-cognos-8-3-bi/comment-page-1#comment-20631 Sachin J. Kulkarni Wed, 28 Oct 2009 15:40:40 +0000 http://ykud.com/blog/?p=252#comment-20631 We faced this CAM error as well. We are using Access Manager and are thinking this may be possible suspect for the the failure to happen. One of the reasons being several hundred logons generated for users in Audit Tables. Can you tell us whether you were using Access Mgr or not? We faced this CAM error as well. We are using Access Manager and are thinking this may be possible suspect for the the failure to happen. One of the reasons being several hundred logons generated for users in Audit Tables.

Can you tell us whether you were using Access Mgr or not?

]]> By: DesiCresnet http://ykud.com/blog/cognos/memory-leaking-in-cognos-8-3-bi/comment-page-1#comment-20466 DesiCresnet Tue, 20 Oct 2009 13:34:38 +0000 http://ykud.com/blog/?p=252#comment-20466 Forgot to mention 4th point to bandaid the situation http://www-01.ibm.com/support/docview.wss?uid=swg21341959 Forgot to mention 4th point to bandaid the situation
http://www-01.ibm.com/support/docview.wss?uid=swg21341959

]]> By: DesiCresnet http://ykud.com/blog/cognos/memory-leaking-in-cognos-8-3-bi/comment-page-1#comment-20465 DesiCresnet Tue, 20 Oct 2009 13:24:24 +0000 http://ykud.com/blog/?p=252#comment-20465 BI 8.2 also has this issue. The same hotfix we put in for 8.3 worked for 8.2 and is required to put in only on Content Managers. Vanilla 8.4 has this issue too. The issue is CAMAAA component which makes JNI calls to LDAP causes this. The issue is still not completely gone. Heap setting and patch delays the crash for 1 week instead of 1 hour on peak concurrent usage. Regarding your reducing the 768MB settings : Be careful. It may may make system unstable. Please turn on Garbage collection and analyze the heap (using IBM Garbage collector). Turn on for a two to three weeks. see if you are making use of 768MB. According you can increase or reduce the heap. Remember, you are delaying the leak. Not correcting. On the same lines we have seen issues with Webservices server (on a rolebased architecture). Content Manager and Planning Webservices are serious weak links.We are surviing by just putting bandaids. Congrats on your certifications. I finsihed BI Modeler. About to finish Planning ones.. BTB did you ever tried decrypting those XMLBLOBS in Planning tables.? I had success in PeopleSoft Tables to decrypt to BASE64. I am not sure about encryption Mechanisms in planning tables. BI 8.2 also has this issue. The same hotfix we put in for 8.3 worked for 8.2 and is required to put in only on Content Managers. Vanilla 8.4 has this issue too.
The issue is CAMAAA component which makes JNI calls to LDAP causes this. The issue is still not completely gone. Heap setting and patch delays the crash for 1 week instead of 1 hour on peak concurrent usage.

Regarding your reducing the 768MB settings : Be careful. It may may make system unstable. Please turn on Garbage collection and analyze the heap (using IBM Garbage collector). Turn on for a two to three weeks. see if you are making use of 768MB. According you can increase or reduce the heap. Remember, you are delaying the leak. Not correcting. On the same lines we have seen issues with Webservices server (on a rolebased architecture). Content Manager and Planning Webservices are serious weak links.We are surviing by just putting bandaids.

Congrats on your certifications. I finsihed BI Modeler. About to finish Planning ones..

BTB did you ever tried decrypting those XMLBLOBS in Planning tables.?
I had success in PeopleSoft Tables to decrypt to BASE64. I am not sure about encryption Mechanisms in planning tables.

]]>