11-100455711 - 9.1 SP4 Memory Handling Issues
Posted: Mon Nov 17, 2008 2:37 am
Here's a tip for those of you submitting bug reports; put the server log in as an attachment. Because when I put it in line, as drafted below, I got a Cognos Insight error SBL-UIF-00299, telling me that there was something invalid in my Description field. This is an error code which, naturally, couldn't be found anywhere in a search of the Cognos site. I extracted that into a text file and uploaded it as an attachment and it worked fine. Other than that, the rerport is quoted below:
======================================================================
It appears that SP4 still has some issues with memory handling.
In SP3, one of the problems we had was that when two chores crashed the server, they generated a dialog on the server box which had to be cleared manually before the service would restart.
The same thing appears to be happening in SP4, albeit from a different cause.
As per the situation described in 11-101026871, I loaded the test server with all of the cubes that we have in 8.2.12, albeit after setting all of the data cubes to Load on Demand.
On this occasion TM1 Top WAS able to connect to the server, but as soon as I tried to log in I got the message shown in the attached screen shot: "Log In Failed: No Error"
"No error" other than the fact that it crashed the server with the traditional 9.1 "The memory could not be 'written' " dialog that had to be cleared on the server box before the server session would restart, anyway.
The TM1Server.log file provides the following information:
7220 INFO 2008-11-17 00:45:45,498 TM1.Chore Registering chore: zSaveData Start time: 2007/10/31 02:50:56 Frequency: 00:12:00:00
3908 INFO 2008-11-17 00:45:46,889 TM1.Server TM1 Server is ready
3908 INFO 2008-11-17 00:45:46,889 TM1.Server Notifying the Admin server
3856 ERROR 2008-11-17 00:51:07,764 TM1.Server.Memory BIGAllocBlock - alloc (size = 150110) failed: Not enough storage is available to process this command.
3856 WARN 2008-11-17 00:51:16,764 TM1.Server.Memory al_Alloc() outOfMemory Exception <<< MEMORY_ALMOST_FATAL_LEVEL >>> - threadID "3856" - apifunc# "1"
3856 INFO 2008-11-17 00:51:16,795 TM1.Server Out of Memory - Last client gone, aborting
3856 FATAL 2008-11-17 00:51:16,795 TM1.Server Server terminated
Now it may well be that the amount of data that we run comfortably in 8.2.12 is too much for 9.1's little memory to handle; that would be something that we'd need to address ourselves.
However the fact that this thing can still tank with the only course of action being to proxy on to the server and manually click a dialog is, I think, something that YOU need to address.
======================================================================
It appears that SP4 still has some issues with memory handling.
In SP3, one of the problems we had was that when two chores crashed the server, they generated a dialog on the server box which had to be cleared manually before the service would restart.
The same thing appears to be happening in SP4, albeit from a different cause.
As per the situation described in 11-101026871, I loaded the test server with all of the cubes that we have in 8.2.12, albeit after setting all of the data cubes to Load on Demand.
On this occasion TM1 Top WAS able to connect to the server, but as soon as I tried to log in I got the message shown in the attached screen shot: "Log In Failed: No Error"
"No error" other than the fact that it crashed the server with the traditional 9.1 "The memory could not be 'written' " dialog that had to be cleared on the server box before the server session would restart, anyway.
The TM1Server.log file provides the following information:
7220 INFO 2008-11-17 00:45:45,498 TM1.Chore Registering chore: zSaveData Start time: 2007/10/31 02:50:56 Frequency: 00:12:00:00
3908 INFO 2008-11-17 00:45:46,889 TM1.Server TM1 Server is ready
3908 INFO 2008-11-17 00:45:46,889 TM1.Server Notifying the Admin server
3856 ERROR 2008-11-17 00:51:07,764 TM1.Server.Memory BIGAllocBlock - alloc (size = 150110) failed: Not enough storage is available to process this command.
3856 WARN 2008-11-17 00:51:16,764 TM1.Server.Memory al_Alloc() outOfMemory Exception <<< MEMORY_ALMOST_FATAL_LEVEL >>> - threadID "3856" - apifunc# "1"
3856 INFO 2008-11-17 00:51:16,795 TM1.Server Out of Memory - Last client gone, aborting
3856 FATAL 2008-11-17 00:51:16,795 TM1.Server Server terminated
Now it may well be that the amount of data that we run comfortably in 8.2.12 is too much for 9.1's little memory to handle; that would be something that we'd need to address ourselves.
However the fact that this thing can still tank with the only course of action being to proxy on to the server and manually click a dialog is, I think, something that YOU need to address.