Error 4216



Message text

%s failed in database %.*s:  unexpected end of log encountered on page %ld while scanning for page %ld.

NoteThis error may be caused by a hardware problem.


The transaction log consists of a series of log pages chained together in a doubly linked list; each log page has a page header with pointers to the next and previous log pages. The previous page pointer for the first page is zero, as is the next page pointer for the last page, indicating the beginning and end of the log chain respectively.

Error 4216 is raised when Adaptive Server finds what it considers to be a premature end of the transaction log chain during execution of a command. This error is raised during dump transaction or dump database and is often seen in conjunction with error 4219.

Error 4216 can be caused by a bad page chain or allocation (syslogs corruption).


  1. Determine the status of syslogs:

    1> use <database_name>
    2> go
    1> dbcc checktable (syslogs)
    2> go
    1> dbcc tablealloc (syslogs)
    2> go

    Where <database_name> is the name of the database appearing in the error message.

    dbcc reports any problems found in syslogs, and the number of data pages being used by the log. If your log is on a separate device, dbcc checktable also tells you how much space is used and how much is free.

  2. If no problems were reported, the transaction log is clean. Call Sybase Technical Support for assistance.

  3. If problems were reported, try to fix them using the sections in this manual that describe those errors. If errors are still reported, call Sybase Technical Support.

Additional information

For information about estimating and managing the transaction log size, refer to “Creating and Managing User Databases” in the System Administration Guide: Volume 2.

Before calling Technical Support, have the information listed in “Reporting errors” on hand, including the output of dbcc checktable and dbcc tablealloc.

Versions in which this error is raised

Version 11.0 and later