Environment: Sybase ASE 15.0.2 (32bit) on Linux. UTF8 character set and binary sort ordering.
Problem: If the index is suspect, an update index statistics results in dropping of the connection. The error message returned doesn’t have an error #, severity # or state #, which makes it very difficult to trap for automated processes.
Solution should be: The error #, severity # and state# should be sent back to the client and NOT close the connection.
The fact that the suspect index may be corrupt is immaterial as the update index statistics may be run in a different maintenance window than dbccs.
use sybmgmtdb go update index statistics js_keys using 128 values with sampling = 100 percent go
Error message returned (not easily trappable): Index id 2 cannot be used to access table id 1792006384 as it is SUSPECT. Please have the SA run the DBCC REINDEX command on the specified table. ASE is terminating this process.
I’ve opened a case with Sybase TechSupport and am waiting on the bug #. I’ll update this when I have it.
UPDATE: CR 481048 has been created to have the error enhanced with an error number, status & severity so it can be trapped by automated jobs.