Monday, March 19, 2012

Error: 17803, Severity: 20, State: 17

I have an application connected to a machine running MSSQL Server 2000 SP3a
Std Edition. Machine is 2.8GHZ, Windows Server 2000. This application runs
extensive query periodically. Over a period of time, I notice through Task
Manager the sqlservr.exe memory usage has grow to ~1.6GB. When this happen,
the application experience slowdown and eventually hang out.
SQL ERRORLog show
2005-04-22 07:16:36.45 spid1 LazyWriter: warning, no free buffers found.
2005-04-22 07:16:36.45 spid1 Buffer Distribution: Stolen=159182 Free=0
Procedures=22931
Inram=0 Dirty=24545 Kept=0
I/O=0, Latched=2022, Other=0
2005-04-22 07:16:36.45 spid1 Buffer Counts: Commited=208680
Target=208680 Hashed=26567
InternalReservation=2130 ExternalReservation=57 Min Free=512
2005-04-22 07:16:36.45 spid1 Procedure Cache: TotalProcs=3969
TotalPages=22931 InUsePages=22931
2005-04-22 07:16:36.45 spid1 Dynamic Memory Manager: Stolen=182112 OS
Reserved=2544
OS Committed=2487
OS In Use=2468
Query Plan=166599 Optimizer=3
General=14803
Utilities=7 Connection=2910
2005-04-22 07:16:36.45 spid1 Global Memory Objects: Resource=11637
Locks=147
SQLCache=1236 Replication=2
LockBytes=2 ServerGlobal=43
Xact=1862
2005-04-22 07:16:36.45 spid1 Query Memory Manager: Grants=1 Waiting=0
Maximum=13450 Available=13392
2005-04-22 07:16:36.70 server Error: 17803, Severity: 20, State: 17
2005-04-22 07:16:36.70 server Insufficient memory available..
I'm currently using SQL Server 2000 Driver for JDBC (with
SelectMethod=Cursor). From SQL Profiler, I do see alot of sp_cursorfetch
calls that don't have a corresponding sp_cursorclose.
Help is greatly appreaciated here!SQL ran out of free buffers (Free=0). You should probably apply the latest
SQL Server hotfix and update JDBC drivers to prevent problems such as 818095
and 837957. In addition, there are changes in the latest SQL hotfixes which
allow Lazy Writer to run more aggressively when it detects a low number of
free buffers.
If the problems persist engage MS product support and have them check your
server for additional leaks.
Adrian
"SS" <SS@.discussions.microsoft.com> wrote in message
news:884EB064-D4C5-4454-A8B4-A151EBC0ED11@.microsoft.com...
>I have an application connected to a machine running MSSQL Server 2000 SP3a
> Std Edition. Machine is 2.8GHZ, Windows Server 2000. This application runs
> extensive query periodically. Over a period of time, I notice through Task
> Manager the sqlservr.exe memory usage has grow to ~1.6GB. When this
> happen,
> the application experience slowdown and eventually hang out.
> SQL ERRORLog show
> 2005-04-22 07:16:36.45 spid1 LazyWriter: warning, no free buffers
> found.
> 2005-04-22 07:16:36.45 spid1 Buffer Distribution: Stolen=159182
> Free=0
> Procedures=22931
> Inram=0 Dirty=24545 Kept=0
> I/O=0, Latched=2022, Other=0
> 2005-04-22 07:16:36.45 spid1 Buffer Counts: Commited=208680
> Target=208680 Hashed=26567
> InternalReservation=2130 ExternalReservation=57 Min Free=512
> 2005-04-22 07:16:36.45 spid1 Procedure Cache: TotalProcs=3969
> TotalPages=22931 InUsePages=22931
> 2005-04-22 07:16:36.45 spid1 Dynamic Memory Manager: Stolen=182112 OS
> Reserved=2544
> OS Committed=2487
> OS In Use=2468
> Query Plan=166599 Optimizer=3
> General=14803
> Utilities=7 Connection=2910
> 2005-04-22 07:16:36.45 spid1 Global Memory Objects: Resource=11637
> Locks=147
> SQLCache=1236 Replication=2
> LockBytes=2 ServerGlobal=43
> Xact=1862
> 2005-04-22 07:16:36.45 spid1 Query Memory Manager: Grants=1 Waiting=0
> Maximum=13450 Available=13392
> 2005-04-22 07:16:36.70 server Error: 17803, Severity: 20, State: 17
> 2005-04-22 07:16:36.70 server Insufficient memory available..
> I'm currently using SQL Server 2000 Driver for JDBC (with
> SelectMethod=Cursor). From SQL Profiler, I do see alot of sp_cursorfetch
> calls that don't have a corresponding sp_cursorclose.
> Help is greatly appreaciated here!
>

No comments:

Post a Comment