标题: 求教，数据库置疑，不能打开，急！！！ [打印本页] 作者: youwei 时间: 2009-08-27 18:39 标题: 求教，数据库置疑，不能打开，急！！！ 以下，是，数据库启动的日志！是wumis 库不能打开！谢谢各位多多指教！！
00:00000:00001:2009/08/27 18:07:33.76 server Recovering database 'sybsystemprocs'.
00:00000:00001:2009/08/27 18:07:33.83 server The transaction log in the database 'sybsystemprocs' will use I/O size of 2 Kb.
00:00000:00001:2009/08/27 18:07:33.88 server Database 'sybsystemprocs' is now online.
00:00000:00001:2009/08/27 18:07:34.07 server Recovering database 'winmis'.
00:00000:00001:2009/08/27 18:07:34.16 server The transaction log in the database 'winmis' will use I/O size of 2 Kb.
00:00000:00001:2009/08/27 18:07:34.21 server Database 'winmis' is now online.
00:00000:00001:2009/08/27 18:07:34.24 server Recovering database 'wumaster'.
00:00000:00001:2009/08/27 18:07:34.29 server The transaction log in the database 'wumaster' will use I/O size of 2 Kb.
00:00000:00001:2009/08/27 18:07:34.33 server Database 'wumaster' is now online.
00:00000:00001:2009/08/27 18:07:34.33 server
*** Bypassing recovery of database id 7
00:00000:00001:2009/08/27 18:07:34.38 server Error: 3403, Severity: 22, State: 2
00:00000:00001:2009/08/27 18:07:34.38 server During recovery initialization, page 1279246 was encountered. This page belongs to object 0, not the log.
00:00000:00001:2009/08/27 18:07:34.40 server Could not make log consistent during special recovery of database 7. Please contact Technical support for assistance.
00:00000:00001:2009/08/27 18:07:34.40 server Recovery complete.
00:00000:00001:2009/08/27 18:07:34.40 server SQL Server's default sort order is:
00:00000:00001:2009/08/27 18:07:34.40 server 'nocase_cp850' (ID = 42)
00:00000:00001:2009/08/27 18:07:34.40 server on top of default character set:
00:00000:00001:2009/08/27 18:07:34.40 server 'cp850' (ID = 2).
00:00000:00001:2009/08/27 18:07:34.40 server Loaded default Unilib conversion handle.
00:00000:00001:2009/08/27 18:07:34.40 server WARNING: spid 1, with suid 0 and curdbid 2 has active XDES #1 with xactid (0, 0).作者: WFCJZ 时间: 2009-08-27 18:44
dbcc traceon(3604)
go
dbcc tablealloc(syslogs)
go
dbcc checktable(syslogs)
go作者: youwei 时间: 2009-08-27 20:16
可以解释下分别是什么作用吗！
执行了，上面的语句，问题还是没有解决!
各位还有什么方法吗？
谢谢！作者: WFCJZ 时间: 2009-08-27 20:49 http://bbs.chinaunix.net/archiver/?tid-123187.html
Message text
During recovery initialization, page %ld was encountered. This page belongs to object %ld, not the log.
This error may be caused by a hardware problem.
Explanation
During recovery, Adaptive Server scans the transaction log until the last page is found. During this scan, if a page is found that has an object ID on the page header that is not the same as that of syslogs, error 3403 occurs.
This may occur either as a result of a hardware failure or due to an Adaptive Server problem.
WARNING! This is a serious error and you must rebuild the affected database either using bcp or from clean backups.
Action
If you have a good backup, restore the database from your backup:
Drop the database. If the drop fails, follow the instructions in “Dropping a database when drop database fails” in the chapter “Other Useful Tasks” in the most recent version of the Troubleshooting and Disaster Recovery guide.
Create a database for load. Make sure the database you create has sizes as least as large as those in sysusages for the original database (and that all other sysusages values match the original values). For more information about creating a database for load, refer to “create database” in the Reference Manual: Commands.
Load the database from backup. (Refer to “load database” in the Reference Manual: Commands.)
Use the online database command to make the database available for use.
To prevent this error from being raised in the future, either perform a normal shutdown of Adaptive Server (specifically, do now use the nowait option), or checkpoint each database that is being used before shutting down Adaptive Server.
Additional information
Refer to “Developing a Backup and Recovery Plan” in the System Administration Guide: Volume 2 for complete information about how to safely create, dump, load, and re-create databases.
Versions in which this error is raised
All versions