FIX: Checkpoint Process Access Violation when Log FillsID: Q158234
|
On SQL Server 6.5 SP1 (6.00.213) Alpha platforms, the checkpoint process
will encounter an access violation (AV) if both of the following are true:
To work around this problem, do not use the database option "trunc. log on
chkpt." Instead, do one of the following:
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5 Service Pack 1. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.
The first symptom of this problem is a process filling up the transaction
log, resulting in the following error in the errorlog:
spid n Error : 1105, Severity: 17, State: 2
spid n Can't allocate space for object 'Syslogs' in database 'pubs' 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.
spid n Automatic checkpointing is disabled in database 'pubs' because the log is out of space. It will continue when the DBO successfully checkpoints the database. Please free up some space or extend the database and then run CHECKPOINT.
kernel checkpoint: Process 3 generated access violation; SQL Server is terminating this process.
Additional query words: SP1
Keywords : kbnetwork SSrvErr_Log SSrvRISC kbbug6.50 kbfix6.50.sp2
Version : winnt:6.5 Service Pack 1 and later
Platform : winnt
Issue type :
Last Reviewed: April 3, 1999