Error 806

Severity

Message text

Could not find virtual page for logical page  %ld in database '%S_DBID'.

This error may be caused by a hardware problem.

Explanation

A virtual page is a page within a Sybase device. A logical page is a page in an Adaptive Server database. There is a one-to-one correspondence between these two types of pages.

Error 806 occurs when Adaptive Server fails to convert a logical page number to a virtual page number. Depending on what caused the error, it can be serious or transient.

If error 806 is accompanied by the message “Page %d is not in the range of pages for database id %d,” it means you used dbcc page with an invalid parameter. This is not a serious problem.

If error 806 occurs on recovery, it may be transient or serious (see information under “Action” for specifics).

Error 806 can occur during normal processing, such as creating an index or running a stored procedure. In this case, the error is probably caused by corruption or a problem with Adaptive Server and it is a serious error.

Action

If error 806 specifies tempdb in the message output, restart Adaptive Server. Since tempdb is rebuilt each time Adaptive Server is restarted, this may clear the error. If the error occurs again (on tempdb), call Sybase Technical Support.

During recovery

If error 806 occurs on recovery, the database will be marked suspect. If the error is transient, resetting the suspect status will solve the problem. To resolve this problem:

Bypass recovery by starting Adaptive Server with status -32768.
Run dbcc checkdb and dbcc checkalloc on the database listed in the error message output.
Set status back to 0.
Shut down Adaptive Server:
```
1> shutdown with nowait
2> go
```
Try recovery again.

If error 806 occurs again, call Sybase Technical Support to help you recover from this error if the corruption is not too widespread. However, recovery from clean backups may be necessary.

During normal processing

Run dbcc checkdb and dbcc checkalloc on the database listed in the error message output. Call Sybase Technical Support. Technical Support may be able to help you recover from this error if the corruption is not too widespread. However, recovery from clean backups may be necessary.

Additional information

Refer to the chapter “Checking Database Consistency” in the System Administration Guide: Volume 2 for information about dbcc commands.

Before contacting Sybase Technical Support, have the information on hand listed in “Reporting errors”, including dbcc checkdb, dbcc checkalloc, and dbcc page output.

Versions in which this error is raised

All versions