Insufficient memory Available

  • Hi all, last night one of production sql servers service hung and required a reboot.

    I was unable to get much out of the event viewer. However I found this in the SQL Server log

    it repeated this for about an hour before the service was killed and system rebooted.

    SERVER            Insufficient memory available. Error: 17803 Severity:19 state 1

    The schedulert 1 appears to be hung. SPID 89,ECID 0, UMS Context 0x03d20090.

    This server has approx 43 databases on it. The largest being 23 gig (read only/standby)

    SQL Server 2000 standard edition sp3a. Windows Server 2000 service pack 4.

    4g ram Dual Intel XEON 3.0 GHz .

    Help!

     

     

  • This was removed by the editor as SPAM

  • Insufficient memeory is sometimes very hard to troubleshooting. You might have a job, trigger or something that uses cursor that you might forget to deallocate or something...

    Also you might want to check this link as well.

    http://support.microsoft.com/default.aspx?scid=kb;en-us;319892

     

  • Sounds like you could have memory leak, that could happen in SQL Server, applications or even OS itself. You need run performance monitor to monitor all of the counters in the Memory object over time to see what happens in your machine.

    One way to help get rid of many memory leaks is to ensure that you always have the latest service packs or updates for your server's software.

     

  • Since you have SP3a, might want to check this as well... Still, follow the Allen's suggestion. That would be the first place to look.

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q814410

     

     

  • One thing to note is that SQL2K Standard edition only addresses 2GB of memory.

    With 43 databases, you are probably hitting the 2GB limit. But it is hard to troubleshoot.

    Good Luck!



    ----------------
    Jim P.

    A little bit of this and a little byte of that can cause bloatware.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply