FIX: Checkpoint Handler GP Faults with Full Transaction Log
  
PSS ID Number: Q104713
Article last modified on 10-31-1994
 
4.20
 
WINDOWS
 

----------------------------------------------------------------------
The information in this article applies to:
 
  - Microsoft SQL Server version 4.2
----------------------------------------------------------------------
 
BUG# NT: 483 (4.2)
 
SYMPTOMS
========
 
If a user-defined transaction is executing, and it causes the SQL
Server transaction log to become completely full, you will receive an
1105 error:
 
   Can't allocate space for object Syslogs in database <db name>
   because the logsegment segment is full. If you ran out of space
   in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE
   or sp_extendsegment to increase the size of the segment.
   (Msg 1105, Level 17, State 2)
 
In addition, you may have the following error reported in the SQL
Server error log:
 
   Unable to write CHECKPOINT record in database <db id> because the
   log is out of space.
   checkpoint: Process 2 generated access violation; SQL Server is
   terminating this process
 
If you issue a sp_who, there will be no checkpoint handler listed.
 
CAUSE
=====
 
SQL Server may incorrectly handle the error when the transaction log
becomes full during a user-defined transaction.
 
WORKAROUND
==========
 
To restart the checkpoint handler, stop and restart SQL Server. If
this occurs frequently, you should enlarge the size of the transaction
log, or increase the frequency of transaction log dumps to prevent the
log from filling.
 
STATUS
======
 
Microsoft has confirmed this to be a problem in SQL Server version 4.2.
This problem was corrected in SQL Server version 4.2P33. For more
information, contact your primary support provider.
 
Additional reference words: 4.20 1105 checkpoint gp-fault Windows NT
KBCategory: kbprg
KBSubCategory: SSrvWinNT
 
=============================================================================
 
Copyright Microsoft Corporation 1994.
