Hi!

The table Kontr_scanned_images is a large table containing an image field.
When I use DBCC on that
table I get an error message:

1> dbcc checktable(Kontr_scanned_images)
2>go

Checking Kontr_scanned_images: Logical pagesize is 2048 bytes
Msg 692, Level 16, State 1:
Server 'PADDA', Line 1:
Uninitialized logical page '4917923' was read while accessing object
'146099561'
in database '4'. Please contact Sybase Technical Support.
DBCC execution completed. If DBCC printed error messages, contact a user
with
System Administrator (SA) role.
1> quit


How do I fix this?

Kjell P.

Hi Kjell,

Here's the write-up from the 12.5.1 Troubleshooting Manual. Hopefully
the error is a "soft", "memory only" error and not due to hardware
issues.

You don't say what version you are running. Check the appropriate
manual to see if the write-up is any different.

Good Luck,

Sara ...


Error 692

Severity

20

Error message text

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

Explanation
These errors may be due to hardware problems.

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:

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

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.

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

Find information about this object in sysindexes:
1> select first, root, doampg, ioampg from sysindexes
2> where name = object_name(<object_id>)
3> go

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.

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" Tasks chapter 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 the Encyclopedia of
Tasks chapter for more dbcc information.

Have the following information ready before calling Sybase Technical
Support:

Adaptive Server version and SWR version level
Server error log
Operating System error log
Output of the sysindexes 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


"Kjell Pettersen" <kjell (AT) gpsgroup (DOT) cc> wrote