11-100455711 - 9.1 SP4 Memory Handling Issues

Post bug reports and the status of reported bugs
Post Reply
User avatar
Alan Kirk
Site Admin
Posts: 5839
Joined: Sun May 11, 2008 2:30 am
OLAP Product: TM1
Version: PA2 Classic (PAW-free zone)
Excel Version: 2010 and 2016
Location: Sydney, Australia
Contact:

11-100455711 - 9.1 SP4 Memory Handling Issues

Post by Alan Kirk » 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.
MemoryFail.jpg
MemoryFail.jpg (29.54 KiB) Viewed 3680 times
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.

User avatar
BigDSter
Posts: 55
Joined: Thu May 15, 2008 8:02 am
OLAP Product: TM1
Version: 9.4.1
Excel Version: 2007
Location: Preston

Re: 11-100455711 - 9.1 SP4 Memory Handling Issues

Post by BigDSter » Mon Mar 01, 2010 12:19 pm

Alan Kirk wrote: 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.
We are just in the process of trying to upgrade to 9.4.1 FP1 (Can't go to FP3 as 8.4.3 clients can't see it, though they can see FP1! and we can't upgrade all the clients first)

We've been running in parallel on a 32 bit server on a 64 bit machine, making sure we don't have any issues. Aside from the fact it seems inherently more unstable and picky than 8.4.3 it seemed to be "good enough" to go to ensure we were able to start out our Office 2007 rollout.

However come this morning (first day of proper switchover) and suddenly we have started to get memory issues, despite being absolutely nowhere near the 3gb-4gb limit that we would expect.


1772 INFO 2010-03-01 09:40:36.658 TM1.Server Done computing feeders for cube "WIP Requirements"
1772 INFO 2010-03-01 09:40:39.345 TM1.Server Computing feeders for cube "}StatsByClient"
1772 INFO 2010-03-01 09:40:39.345 TM1.Server Done computing feeders for cube "}StatsByClient"
388 INFO 2010-03-01 09:40:52.843 TM1.Server Starting PseudoElement thread. Thread Id: 388
1716 INFO 2010-03-01 09:42:34.298 TM1.Server TM1 Server is ready
1716 ERROR 2010-03-01 09:51:03.392 TM1.Server.Memory BIGAllocBlock - alloc (size = 32781) failed: Not enough storage is available to process this command.

1716 WARN 2010-03-01 09:51:03.392 TM1.Server.Memory al_Alloc() outOfMemory Exception <<< MEMORY_ALMOST_FATAL_LEVEL >>> - threadID "0" - apifunc# "0"
1716 WARN 2010-03-01 09:51:03.392 TM1.Server.Network net_Create Low Memory
1300 ERROR 2010-03-01 09:51:33.099 TM1.Server.Memory CommonAlloc - alloc (size = 131072) failed: Not enough storage is available to process this command.

1300 WARN 2010-03-01 09:51:33.099 TM1.Server.Memory CommonAlloc() outOfMemory Exception <<< MEMORY_ALMOST_FATAL_LEVEL >>> - threadID "1300" - apifunc# "0"
1760 ERROR 2010-03-01 09:53:15.805 TM1.Server.Memory BIGAllocBlock - alloc (size = 32781) failed: Not enough storage is available to process this command.

1760 WARN 2010-03-01 09:53:15.805 TM1.Server.Memory al_Alloc() outOfMemory Exception <<< MEMORY_ALMOST_FATAL_LEVEL >>> - threadID "0" - apifunc# "0"
1760 WARN 2010-03-01 09:53:15.805 TM1.Server.Network net_Create Low Memory
1380 ERROR 2010-03-01 09:54:00.087 TM1.Server.Memory BIGAllocBlock - alloc (size = 16456) failed: Not enough storage is available to process this command.

1380 WARN 2010-03-01 09:54:00.087 TM1.Server.Memory BIGAllocBlock() outOfMemory Exception <<< MEMORY_FATAL_LEVEL >>> - threadID "1380" - apifunc# "0"
2296 FATAL 2010-03-01 09:54:03.574 TM1.Server Server terminated
1760 ERROR 2010-03-01 09:54:17.803 TM1.Server.Memory BIGAllocBlock - alloc (size = 32781) failed: Not enough storage is available to process this command.

1760 WARN 2010-03-01 09:54:17.803 TM1.Server.Memory BIGAllocBlock() outOfMemory Exception <<< MEMORY_FATAL_LEVEL >>> - threadID "0" - apifunc# "0"
1760 ERROR 2010-03-01 09:54:17.803 TM1.Server TM1 Server Abort: System Out Of Memory.
1760 INFO 2010-03-01 09:54:17.803 TM1.Server Closing...

straight after server restart. However now we have had to do an emergency reverse onto 8.4.3 while we figure out what is going on, it seems fine and has had no issues.


A tad bit confusing and frustrating to say the least.
David Newton
Burtons Foods

Post Reply