Exchange 2007, Database resource failure error Out of memory...
Hi all.
I got the following error in our Exchange 2007 SP1 on Windows 2003 Server SP2 machine:
Database resource failure error Out of memory occurred in function JTAB_BASE::EcMakeKey while accessing the database "[DB Name]".
Event ID 1160, category "General", source "MSExchangeIS".
The server is a HP DL380 G5 with 8 Gb of RAM and uses local disks for the OS and the SAN for the logs and the data. There's plenty of disk left.
The server has the mailbox,HUB andCAS roles installed as well as ForeFront for Exchange. There's about 70 users and they use EAS and run Outlook 2003/2007 in cached mode.
The file-level anti-virus is Trend Micro on both the clients and the server.
The server was up and running for about a month before this happened which resulted in the information store stopping, prompting a server restart.
All the information I've managed to dig up so far about this issue is for either 5.5 or 2003 - there's no or little information to be found when it comes to the 2007 version.
Any ideas about how to prevent this from happening again would be very much appreciated.
TIA.
April 18th, 2008 10:22am
Your a/v scanners aren't trying to scan the databases at the file level are they? Have you been monitoring baseline performance on that box? If not, start...ExBPA can do it for you.
Free Windows Admin Tool Kit Click here and download it now
April 18th, 2008 7:51pm
The AV software is not scanning the log or database files.
There is no actual resource problem on the server.
We found out, after some digging, that the daily maintenance isn't running properly and that there's only 48 Mb of space left in a 41 Gb large database. Could this be the culprit?
I was under the impression that the database grew until it reached the max (72 Gb?) limit.
April 21st, 2008 12:31pm
48MB of Whitespace? That's actually a good thing. Whitespace is unclaimed storage thatformelly held data(say a purged mailbox), the DB will re-use the whitespace as it grows, andon std edition, you are rightabout the limit.If however, you only have 48MB of free disk space for the DB, that's trouble.
Have you turned up logging on the exchange server?
Free Windows Admin Tool Kit Click here and download it now
April 21st, 2008 6:54pm
No, logging is at the lowest for all components.
What component should I enable logging for and at what level?
April 22nd, 2008 2:53pm
Well, this is where it gets tricky, I can't find a single MS resource with all possible switches for cmdlet set-eventloglevel, but what you'd want is to set it for MSEXchangeIS and probably verbose level since it seems to be a database issue. Also, how many SG's DB's do you have and what is the sg to db ratio? Has the issue happened again?
Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2008 6:35pm
We have 2 SG's with one DB in one SG and two DB's in the other SG.
The issue has not happened again.
I'll enable verbose logging for all MSExchangeIS components (as I feared I would have to ).
Thanks.
April 23rd, 2008 9:50am
We have the same error on our environment except that we are running with active/passive cluster. When this happen a fail over is called and all services are move to the passive node. Then the system run for a couple of weeks and then fail again.We do have the same kind of environment with exchange installed on a local drive and data/log on a SAN.Only the mailbox role is installed on my server with forefront and TREND Micro OfficeScanAny suggestion for a resolution is welcome.Stephane
Free Windows Admin Tool Kit Click here and download it now
January 6th, 2010 5:52pm