Sybase Server Error: 692, Severity: 20, State: 1

[Former Member]

Hello Experts,

We are frequently getting the error 692 in our development and Quality Servers(Production is not at go-live). After getting this error we are unable to work in the system, getting ST22 dumps like DBIF_REPO_SQL_ERROR , [ASE Error SQL21][SAP][ASE ODBC Driver][Adaptive Server Enterprise]WARNING - Fatal Error 692 occurred at Dec 19 2014 10:36PM. Please note the error and time, and contact a user with System Administrator (SA) authorization.#".

Error in the ASE Error log is

server  Error: 692, Severity: 20, State: 1

server  Uninitialized logical page '4136632' was read while accessing database 'SID' (4), object 'WDY_WB_GENINFO' (959403181), index 'WDY_WB_GENINFO~001' (3), partition 'WDY_WB_GENINFO~001_959403181' (959403181). Please contact Sybase Technical Support.

server  Error: 692, Severity: 20, State: 1

server  Uninitialized logical page '4135787' was read while accessing database 'SID' (4), object 'REPOSRC' (1540366417), index 'REPOSRC~0' (2), partition 'REPOSRC~0_1540366417' (1540366417). Please contact Sybase Technical Support.

The dbcc checktable logs on these are attached to this thread.

Please help us.

dbcc_checktable.txt.zip

[sladebe · Accepted solution]

It's a page corruption problem in Sybase.  This is a bad thing.   A lot of things could cause it.

• Some sort of bad operating system interaction.  Eg. some other process modifying the devices/files Sybase is using to write it's data.   Or maybe you have your Sybase devices on NFS?   
• One of your disks is physically bad.  Do you have disk mirroring at the operating system level or within Sybase?
• Or maybe the box was shutdown while the server was busy writing data?
• Maybe a backup was loaded into the wrong chunks in a destination database?
• You hit a Sybase bug?   Do you have any stacktraces in Sybase before the 692 error(s)

[former_member187136]

Krishna,

Generally 692 errors can be handled by dbcc page command rather than the checktable()

Obtain page information by running dbcc page as soon as possible, using the database ID and page number shown in your ASE Error log:

  1> dbcc page (db_id, page_number, 0, 1, 1, -1)

  2> go

Or You can even suspect there may be Operating system error which would have caused this error, if you have access check the OS logs or contact the OS team.

Regards

Kiran Kumar A