Could not write a CHECKPOINT record in database ID %d because the log is out of space.

Details
Product: SQL Server
Event ID: 3619
Source: MSSQLServer
Version: 10.0
Component: SQLEngine
Symbolic Name: SYS_NOLOG
Message: Could not write a checkpoint record in database ID %d because the log is out of space. Contact the database administrator to truncate the log or allocate more space to the database log files.
   
Explanation

The transaction log is out of disk space.

   
User Action

Truncate the log to release some space, or allocate more space to the log. For more information see, “Troubleshooting a Full Transaction Log (Error 9002)” in SQL Server Books Online.

   
   
Version: 9.00.1281.60
Symbolic Name: SYS_NOLOG
Message: Could not write a checkpoint record in database ID %d because the log is out of space. Contact the database administrator to truncate the log or allocate more space to the database log files.
   
Explanation

The transaction log is out of disk space.

   
User Action

Truncate the log to release some space, or allocate more space to the log. For more information see, “Managing a Full Transaction Log” in SQL Server 2005 Books Online.

   
   
Version: 9.0
Component: SQLEngine
Symbolic Name: SYS_NOLOG
Message: Could not write a checkpoint record in database ID %d because the log is out of space. Contact the database administrator to truncate the log or allocate more space to the database log files.
   
Explanation

The transaction log is out of disk space.

   
User Action

Truncate the log to release some space, or allocate more space to the log. For more information see, “Managing a Full Transaction Log” in SQL Server 2005 Books Online.

   
   
Version: 8.0
Component: SQL Engine
Message: Could not write a CHECKPOINT record in database ID %d because the log is out of space.
   
Explanation
The transaction log for the specified database has reached its capacity. The limit could be due to a configuration setting or to the amount of physical space available for one or more of the files configured for this database.

For more information about possible reasons why the transaction log grew, see the Microsoft Knowledge Base article 317375.

   
User Action
Follow these steps:

  1. Issue the BACKUP LOG statement to remove committed transactions from the transaction log.
  2. If the database has been marked suspect, execute sp_resetstatus with the database name as the parameter, and then restart the SQL Server instance.
  3. If the transaction log has grown larger than necessary, you can now shrink the log. For more information about how to shrink the transaction log, see the Microsoft Knowledge Base article 272318.
  4. Determine why the transaction log grew unexpectedly and adjust your configuration and/or your applications to compensate.

Related:

Leave a Reply