Troubleshooting Out Of Memory error in Anlaysis Server

原创 2006年05月17日 01:21:00

This article discusses how to categorize the cause of and troubleshoot the following error in application event log of Analysis Server. For example:

Event Type:   Error
Event Source:       MSSQLServerOLAPService
Event Category:    Server
Event ID:       123
Date:             3/28/2006
Time:             9:49:33 AM
User:             N/A
Computer:      <Computer Name>
Description:
The server is out of memory.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Sometimes you also will see the additional error as below:

Event Type:   Error
Event Source:       MSSQLServerOLAPService
Event Category:    Server
Event ID:       117
Date:             2006-5-3
Time:             4:11:23
User:             N/A
Computer:      <Computer Name>
Description:
Unexpected fatal error occurred.  Attempting to restart server.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Analysis Services load all dimensions for all databases into volatile memory on startup. During processing, the server consumes additional memory to process updates to dimensions and cubes. If insufficient memory is available for these and other operations, you will receive this message. When this error occurred, it only indicates there is memory pressure at that time. Analysis Service will trigger background process to release memory generally. If this error did not induce the analysis service restart, we can simply ignore this message.

You can resolve this issue in several ways menteiond in the following article:
Error 123
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_as_errors_3s6s.asp

In Analysis Service 2005 (SSAS), we also will see similiar error like this during process operation.
Memory Error: The operation cannot be completed because the memory quota estimate (xxxMB) exceeds the available system memory (xxxMB)

Before Cube processing, SSAS will estimate the required memory size and does memory quota limit check, if the available memory is not enough, the error will occur. To resolve such issue, you can follow the suggestions in the above artile in Analysis Service 2000.

Also, there is a known issue as below
914595 FIX: Dimension processing may fail, and you may receive an error message in SQL Server 2005 Analysis Services
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914595

To work around this problem, we can override the memory quota limit check by setting MemoryLimitErrorEnabled=0 in the config file (msmdsrv.ini): MemoryLimitErrorEnabled=0. After disable the memory quota limit check, SSAS will do the memory check before process so that we will not encoutner this error again.

To troubleshoot such issue we need collect following information:

1. Confirm whether the OOF error is related to MDX query or Process operation.
2. The Anlaysis Service database size, need check the size of the database folders, which are under c:/Program Files/Microsoft Analysis Services/Data.
3. Whether SQL and Analysis Server running on the same box.
4. What is the version of the file msmdsrv.exe, which is under C:/Program Files/Microsoft Analysis Services/Bin by default.
5. Open the Regedit utility, export the values under the
“HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/OLAP Server” sub-tree into a file and get them for further analysis.
6. Collect performance log
7. If the OOF error is related to process log, we need processing log for detailed checking.
8. When the processing log and performance log is enabled, please reproduce the same error (Out of memory). Then provide the following information for research:
a. Performance log
b. processing log

Thanks and regards,
Michael

相关文章推荐

编译android源码时,jack server 出现out of memory error 错误的解决方法

编译android源码时,jack server 出现out of memory error 错误的解决方法: 问题现象如下: 问题的解决方案如下,共两步: Step1:修改ja...

android.view.InflateException: Binary XML file line #95: Error inflating class(out of memory)

今天的异常很有意思,叫做android.view.InflateException: Binary XML file line #95: Error inflating class(out of me...

ORA-27102:out of memory Linux-X86_64 Error: 28: No space left on device

startup Linux下oracle报以下错 ORA-27102:out of memory Linux-X86_64 Error: 28: No space left on device ...

Android Out of Memory Error: Causes, Solution and Best practices

OOM是一种常见的ERROR当我们处理多图片、大的Bitmap或者一些动画的时候。我们必须特别仔细的控制图片对象的创建和销毁。 当你的程序申请的内存超出系统分配给你的堆大小时(heap limit)就...

GC Out of memory Error: GC overhead limit exceeded

In the T/D project , I occurred a problem that "Out of memory Error: GC overhead limit exceeded", wh...

Android Out of Memory Error Causes, Solution and Best practices

Android Out of Memory Error:Causes, Solution and Best practices          译文:http://blog.csdn.net/ise...

Out Of Memory Issues in java

Memos for Java Out Of Memory Issues * Exception in thread “CompilerThread1″ java.lang.OutOfMemoryEr...
  • lzy_168
  • lzy_168
  • 2012年05月22日 14:42
  • 1640

Caused by: java.sql.SQLException: Out of memory; restart server and try again (needed 142328 bytes)

Caused by: java.sql.SQLException: Out of memory; restart server and try again (needed 142328 bytes...

While starting out of two DBs one DB getting error: ORA-01102: cannot mount database in EXCLUSIVE mo

While starting out of two DBs one DB getting error: ORA-01102: cannot mount database in EXCLUSIVE mo...
  • loryliu
  • loryliu
  • 2016年09月06日 16:50
  • 345

tomcat out of memory solution

  • 2013年01月12日 13:34
  • 5KB
  • 下载
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:Troubleshooting Out Of Memory error in Anlaysis Server
举报原因:
原因补充:

(最多只允许输入30个字)