Error 692



Message text

Uninitialized logical page '%ld' was read while accessing object '%ld' in database '%d'. Please contact Sybase Technical Support.


Error 692 occurs when Adaptive Server tries to read a page that is not formatted (initialized) or is improperly formatted. The server retries the read if the first read attempt failed, and raises the 692 error if the second read attempt also fails.

Error 692 results in a stack trace and breaks your connection to Adaptive Server.

NoteThese errors may be due to hardware problems.


Take the following steps:

  1. Check the server error log for other errors that may have been raised prior to the 692 error. Save the entire error log.

  2. Obtain page information by running dbcc page as soon as possible, using the database ID and page number shown in the message:

    1> dbcc page (<db_id>, <page_number>, 0, 1, 1, -1)
    2> go

    WARNING! Use the dbcc page command only as directed above. This command is undocumented, nonstandard, and is provided “as is” without any warranty. Sybase Technical Support does not support this command for general use. Although the command syntax is provided here for reference, you should use this command only in the specific diagnostic situations described, and with the specific syntax shown in this section. Failure to do so could cause performance problems and/or database corruption.

  3. Identify the object named in the error message using the following isql commands:

    1> use <database name>
    2> go
    1> select name from sysobjects where id=<object_id>
    2> go
  4. Find information about this object in sysindexes (pre-15.0) or syspartitions (version 15.0 and later):

    • Versions earlier than 15.0:

      1> select first, root, doampg, ioampg from sysindexes
      2> where name=object_name(<object_id>)
      3> go
    • Version 15.0 and later:

      1> select firstpage, rootpage, datoampage, indoampage 
      2> from syspartitions
      3> where id=<object_id>
      4> go
  5. To determine the full extent of the corruption, run dbcc checkstorage, the dbcc checkdb and dbcc checkalloc commands, or dbcc checktable and dbcc tablealloc) as soon as possible.

  6. To check if this error is a result of hardware failure, examine your operating system error log and correct hardware problems. See “Checking the operating system error log” in the chapter “Other Useful Tasks” in the most recent version of Troubleshooting and Disaster Recovery for assistance.

WARNING! If the 692 error is not a soft error (one that exists only in memory), the problem is severe. Sybase Technical Support may be able to help you recover from the error. However, this recovery procedure often results in loss of data; if this is unacceptable, you will probably need to restore from backups.

Additional information

Refer to the “Error 605” write-up for a discussion of potential causes of hardware error. Refer to “dbcc” in the “Commands” chapter of the Reference Manual: Commands for more dbcc information.

Have the information on hand that is listed in “Reporting errors” ready before calling Sybase Technical Support, including the output of the sysindexes or syspartitions query and dbcc checks from steps 2, 4, and 5 above.

A database dump and transaction log dumps may also be required.

Versions in which this error is raised

All versions