緊急求助：應(yīng)用系統(tǒng)運(yùn)行時(shí)出現(xiàn) 605 錯(cuò)，救命啊... ...

小小白云

    
應(yīng)用系統(tǒng)運(yùn)行時(shí)出現(xiàn) 605 錯(cuò)，故障現(xiàn)象為輸入單據(jù)速度越來越慢，errorlog日志記錄如下：
server  End diagnostics for read failure:
server  Run the DBCC command 'dbcc tablealloc' for both the objects 112003430, 240003886
server  Error: 605, Severity: 21, State: 1
server  An attempt was made to fetch logical page '1819643' in database 'xxx' from cache 'default data cache'. Page belongs to object with id '240003886', not to object 'xx04'.
kernel  ************************************
kernel  SQL causing error : update xx04 SET ttt ='4' WHERE xx04.dd ='7723'
kernel  ************************************
server  SQL Text: update xx04 SET ttt ='4' WHERE xx04.dd ='7723'
kernel  curdb = 5 pstat = 0x10100 lasterror = 605
kernel  preverror = 0 transtate = 0
kernel  curcmd = 197 program = ZZZ

操作系統(tǒng)： HP_UX 11.0/sybase 11.9.2.5

xxx表之xx04表有800萬條記錄，所以在輸入單據(jù)（其它表）而修改數(shù)據(jù)表xx04狀態(tài)的時(shí)候，系統(tǒng)出現(xiàn)605錯(cuò)，錯(cuò)誤級(jí)別21，請(qǐng)各位大俠鼎力相助，感激涕零～～～

特急～特急～特急～～～

molin

1.Run the dbcc checktable command on the second object specified in the error message.
2.To help determine the full extent of the corruption, run the dbcc checkdb and dbcc checkalloc commands as soon as feasible.
3.Check the SQL Server error log for other errors which often accompany a 605 error. If the 605 error is not transient, the problem is severe and you will probably need to restore from known clean backups.
4.Either of the following situations may also apply to your
SQL Server:
- If this error occurs after rebuilding the master device or reconfiguring the configuration block to the defaults, then the sort order on the new device may not match the sort order in the dump. If the sort orders do not match, call Technical Support for further assistance.
- To check if the error occurred as the result of hardware failure, examine your operating system error log and correct hardware problems.
If you have dial-in facilities, Technical Support may be able to help you recover from this error without having to restore from backups. However, this recovery procedure often results in a loss of data, and therefore is often unacceptable, especially to production systems.