Re: =?iso-8859-1?Q?=25=24=A7=21=40=21=21=21_SQL=2DServer?=

Dale E. Reed Jr. ( (no email) )
Wed, 26 Feb 1997 10:53:37 -0800 (PST)

On Wed, 26 Feb 1997, Peter A. Sang wrote:

> Allocation Discrepancy: Page is allocated but not linked; check the
> following pages and ids: allocation pg#=3D90368 extent id=3D90488 logical
> pg#=3D90489 object id on extent=3D1461580245 (object name =3D Traffic) in=
> on extent=3D3
> What does it mean, and how do I fix it?? DBCC CHECKDB gives me no errors
> at all, everything looks fine.

Did you try DBCC CheckAlloc()? This should check the allocation
pages (the errors are pointing to). I also found a usefull DBCC command
undocumented yesterday called DBCC CheckIdent().
> 2. This is from our error.log file:
> 97/02/26 06:39:53.06 spid11 Fehler: 1105, Schweregrad: 17, Zustand: 1
> 97/02/26 06:39:53.06 spid11 Kann f=FCr Objekt 'MSProxyLog' in Datenbank
> 'Emerald' keinen Speicher reservieren, da 'default' Segment voll ist. In
> Syslogs kann durch Speichern des Protokolls Platz geschaffen werden.
> Sonst ALTER DATABASE oder sp_extendsegment verwenden, um die
> Segmentgr=F6=DFe zu erh=F6hen.

Yeah, right. :)

> For those not German-challenged: Cannot allocate space for Object 'xxx'
> in db 'yyyy' because the 'default' segment is full .....

Do you have your logspace on another device? Sounds like you
either ran out of room in the Emerald or master database.

> The db has a size of 1GB, used space is around 500 MB. What does
> 'default-segment' mean _exactly_? What am I missing???? How do I fix
> it???

Did you look at your master DB?