Switch to standard view 
  Sybase logo
 
 
 



This TechNote explains Adaptive Server Enterprise access errors 691, 692, 693, 694, 695, 696 and 697.

Note:

This information also appears in the 11.9.2 Troubleshooting and Error Messages Guide. Unless otherwise specified, all references in this TechNote are to sections in that document.

Error 691

Severity

20

Error Message

Encountered invalid logical page '%ld' while accessing
object '%ld' in database '%d'. This is an internal system error
Please contact Sybase Technical Support.

Note:

This message was introduced in Version 11.0.3 to improve the ability to diagnose 605 object ID mismatch errors. Some errors that previously raised the 605 error are now reported as 691 errors. These errors may be due to hardware problems.

Explanation

This error occurs when Adaptive Server tries to access an object but requests an invalid page number. There are two possibilities:

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

Action

Take the following steps:

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

  2. 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 

  3. To determine the full extent of the corruption, run the dbcc checkdb and dbcc checkalloc commands (or dbcc checktable and dbcc tablealloc) as soon as possible. On version 11.5 and higher, you can also run dbcc checkstorage.

  4. To check if this error is a result of hardware failure, examine your operating system error log and correct hardware problems.

If the 691 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 writeup for Error 605 for a discussion of potential causes of hardware error.

Have the following information ready before calling Sybase Technical Support:

Versions in Which This Error is Raised

11.0.3 and later

Error 692

Severity

20

Error Message

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

Note:

This message was introduced in Version 11.0.3 to improve the ability to diagnose 605 object ID mismatch errors. Some problems that previously raised the 605 error are now reported as 692 errors. These errors may be due to hardware problems.

Explanation

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.

Action

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.

  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:

    1> select first, root, doampg, ioampg from sysindexes
    2> where name = object_name(<object_id>)
    3> go 

  5. To determine the full extent of the corruption, run the dbcc checkdb and dbcc checkalloc commands (or dbcc checktable and dbcc tablealloc) as soon as possible. On version 11.5 and higher, you can also run dbcc checkstorage.

  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 "Encyclopedia of Tasks" for assistance.

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 writeup for a discussion of potential causes of hardware error. Refer to"Useful dbcc Commands" in "Encyclopedia of Tasks", for more dbcc information.

Have the following information ready before calling Sybase Technical Support:

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

Versions in Which This Error is Raised

11.0.3 and later

Error 693

Severity

20

Error Message

Multiple copies of logical page '%ld' from database '%d'
reside in more than one cache. This is an internal 
system error. Please contact Sybase Technical Support.

Note:

This message was introduced in Version 11.0.3 to improve the ability to diagnose 605 object ID mismatch errors. Some errors that previously raised the 605 error are now reported as 693 errors.

Explanation

This error occurs when Adaptive Server tries to access an object but is unable to establish the identity of a logical page for the object. Copies of the page are found in more than one cache, and the current session is accessing the wrong version.

Error 693 is caused by an Adaptive Server problem. It results in a stack trace and breaks your connection to Adaptive Server.

Action

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

  2. Obtain cache 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.

  3. Contact Sybase Technical Support with the information you collected.

Additional Information

Refer to Error 605 for a complete list of related object mismatch errors.

Have the following information ready before calling Sybase Technical Support:

Versions in Which This Error is Raised

11.0.3 and later

Error 694

Severity

24

Error Message

An attempt was made to read logical page '%ld', virtpage 
'%ld' from virtual device '%d' for object '%ld' in 
database '%d'. The page was not read successfully. 
You may have a device problem or an operating system 
problem.

Note:

This message was introduced in Version 11.0.3 to improve the ability to diagnose 605 object ID mismatch errors. Some errors that previously raised the 605 error are now reported as 694 errors. These errors may be due to hardware problems.

Explanation

This error occurs when Adaptive Server tries to access an object but is unable to read the page mentioned in the message. Adaptive Server automatically issues a second read request to verify the consistency of the first read attempt. One of the following cases will be true:

In all cases, Adaptive Server writes the following message into the error log:

Suspect a Device or OS problem, %s

and raises Error 694, resulting in a stack trace and breaking your connection to Adaptive Server.

This error indicates hardware or operating system problems.

Action

Additional Information

Refer to the writeup for Error 605 for a discussion of potential causes of hardware error.

Versions in Which This Error is Raised

11.0.3 and later

Error 695

Severity

20

Error Message

An attempt was made to read logical page '%ld' 
for object '%ld' in database '%d' from cache '%.*s'. 
Wrong logical page '%ld' was brought into cache. 

Note:

This message was introduced in Version 11.0.3 to improve the ability to diagnose 605 object ID mismatch errors. Some problems that previously raised the 605 error are now reported as 695 errors. These errors may be due to hardware problems.

Explanation

Error 695 occurs when Adaptive Server tries to read a page from disk (the first logical page in the message), but the page number in the header of the returned page does not match the requested page. This means that the page is corrupt on disk, and has been overwritten by another page. The error may be due to an Adaptive Server problem but could also be caused by problems such as overlapping partitions or hardware errors.

Error 695 results in a stack trace and breaks your connection to Adaptive Server. Additional errors may be reported on the console and in the server error log prior to this error.

Action

  1. Check the server error log for other errors that may have been raised prior to the 695 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.

  3. To determine the scope of the problem, locate the device on which the database resides, and check if any other databases use the same device. Refer to "How to Determine Which Physical Devices a Database is On" in "Encyclopedia of Tasks".

  4. Check that the device is partitioned correctly. See "Correct Use of Raw Partitions" in "Encyclopedia of Tasks".

  5. Run dbcc log to find the history of transactions against this page.

    1> dbcc log (<dbid>, 0, <page_no>, 0, 0, -1)
    2> go

    WARNING!

    Use the dbcc log command only as directed above.

  6. To determine the full extent of the corruption, run the dbcc checkdb and dbcc checkalloc commands (or dbcc checktable and dbcc tablealloc) as soon as possible. On version 11.5 and higher, you can also run dbcc checkstorage.

  7. 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 "Encyclopedia of Tasks", for assistance. Also see Error 605 for a discussion of potential causes of hardware error.

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

See "Useful dbcc Commands" in "Encyclopedia of Tasks" for more dbcc information.

Have the following information ready before calling Sybase Technical Support:

Versions in Which This Error is Raised

11.0.3 and later

Error 696

Severity

21

Error Message

An attempt was made to fetch logical page '%ld' 
in tempdb from cache '%.*s'. Page belongs to 
object '%ld' and not to object '%ld'. Restart of SQL Server 
will clear the error. Please contact your System Administrator 
for help.

Note:

This message was introduced in Version 11.0.3 to improve the ability to diagnose 605 object ID mismatch errors. Some errors that previously raised the 605 error are now reported as 696 errors.

Explanation

This error occurs when Adaptive Server discovers page allocation corruption. Adaptive Server tries to access a particular object but discovers a page in the object's page chain whose object ID is different than that of the object being accessed.

This error is similar to the 605 error. However, Error 696 always occurs in the context of the tempdb database. Since the object ID mismatch is detected in cache, this is a transient (soft) error.

Action

Shut down and restart Adaptive Server to clear the cache problem. If Error 696 occurs again, call Sybase Technical Support.

Additional Information

Have the following information ready before calling Sybase Technical Support:

Versions in Which This Error is Raised

11.0.3 and later

Error 697

Severity

20

Error Message

An attempt was made to fetch logical page '%ld' 
for object '%ld' in database '%d' from cache '%.*s'. 
Wrong logical page '%ld' was found in cache.

Note:

This message was introduced in Version 11.0.3 to improve the ability to diagnose 605 object ID mismatch errors. Some errors that previously raised the 605 error are now reported as 697 errors. These errors can be due to hardware problems.

Explanation

This error occurs when Adaptive Server tries to access an object in cache but arrives at an invalid page. The page number is correct on disk, but it does not match the page number of the page in memory.

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

Action

Since the problem occurs in cache, it is a soft error. Shut down and restart Adaptive Server to clear the memory corruption.

Versions in Which This Error is Raised

11.0.3 and later




Back to Top
© Copyright 2010, Sybase Inc.