Re: SQL 2000 Error: 17803, Severity: 20, State: 14
From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 07/21/04
- Next message: Gregory A. Larsen: "Re: collecting db statistics"
- Previous message: Dominic: "RE: Weird parallel stored procedures execution problem"
- In reply to: Michelle vdM: "RE: SQL 2000 Error: 17803, Severity: 20, State: 14"
- Next in thread: Michelle vdM: "Re: SQL 2000 Error: 17803, Severity: 20, State: 14"
- Reply: Michelle vdM: "Re: SQL 2000 Error: 17803, Severity: 20, State: 14"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 21 Jul 2004 11:03:15 -0400
OK your running 2000 SP3 but what edition? Std or Enterprise? What OS,
Server or ADV Server? How is the memory configured on SQL Server? Do you
have the /3GB switch set how is the SQL Memory configured?
-- Andrew J. Kelly SQL MVP "Michelle vdM" <Michelle vdM@discussions.microsoft.com> wrote in message news:4B23B062-FEEC-4480-AD34-17E7987798A5@microsoft.com... > We are running SQL2000 SP3. We have seperated the Weblogic server and the SQL server and we are still getting the Error: 17803, Severity: 20, State: 14 error log as stated below. > > "Michelle vdM" wrote: > > > Error: 17803, Severity: 20, State: 14 > > server Insufficient memory available.. > > spid1 LazyWriter: warning, no free buffers found. > > spid1 Buffer Distribution: Stolen=147940 Free=0 Procedures=2 > > Inram=0 Dirty=48338 Kept=0 > > I/O=0, Latched=12416, Other=0 > > spid1 Buffer Counts: Commited=208696 Target=208696 Hashed=60754 > > InternalReservation=271 ExternalReservation=0 Min Free=512 > > spid1 Procedure Cache: TotalProcs=1 TotalPages=2 InUsePages=2 > > spid1 Dynamic Memory Manager: Stolen=147942 OS Reserved=3752 > > OS Committed=3692 > > OS In Use=3670 > > Query Plan=120830 Optimizer=2189 > > General=23020 > > Utilities=145 Connection=4994 > > spid1 Global Memory Objects: Resource=19624 Locks=165 > > SQLCache=75 Replication=2 > > LockBytes=2 ServerGlobal=46 > > Xact=3185 > > spid1 Query Memory Manager: Grants=0 Waiting=0 Maximum=31493 Available=31493 > > Other info: > > Connection to the SQL database is via Weblogic. We were running Weblogic and SQL on the same box(1x1GHz cpu, 1GB RAM). We have moved the database to another server (4x1.5GHz CPUs and 3.5GB RAM) and we get the same messages in the error log. > > Other symptoms: tempdb grows large.
- Next message: Gregory A. Larsen: "Re: collecting db statistics"
- Previous message: Dominic: "RE: Weird parallel stored procedures execution problem"
- In reply to: Michelle vdM: "RE: SQL 2000 Error: 17803, Severity: 20, State: 14"
- Next in thread: Michelle vdM: "Re: SQL 2000 Error: 17803, Severity: 20, State: 14"
- Reply: Michelle vdM: "Re: SQL 2000 Error: 17803, Severity: 20, State: 14"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|