数据库启动时报错，Recovery failed如何解决(在线等急）

pepsion

下面是启动日志：请各位帮忙看看如何解决，在线等，如果有MSN请加我pepsion@hotmail.com

"SYB.log" 1648 lines, 166826 characters
00:00000:00000:2005/08/02 16:21:36.19 kernel  Warning: There is no valid license for ASE server product. Server is booting with all
the option features disabled.
00:00000:00000:2005/08/02 16:21:36.19 kernel  Using config area from primary master device.
00:00000:00000:2005/08/02 16:21:36.19 kernel  Configuration Error: Configuration file, '/opt/sybase/SYB.cfg', does not exist.
00:00000:00000:2005/08/02 16:21:36.19 kernel  Warning: A configuration file was not specified and the default file '/opt/sybase/SYB.
cfg' does not exist. SQL Server creates the default file with the default configuration.
00:00000:00000:2005/08/02 16:21:36.25 kernel  Using 1024 file descriptors.
00:00000:00000:2005/08/02 16:21:36.25 kernel  Adaptive Server Enterprise/12.0/P/SWR 8774 ESD 1/Sun_svr4/OS 5.6/1580/32bit/FBO/Tue De
c  7 03:10:20 1999
00:00000:00000:2005/08/02 16:21:36.25 kernel  Confidential property of Sybase, Inc.
00:00000:00000:2005/08/02 16:21:36.25 kernel  Copyright 1987, 1999
00:00000:00000:2005/08/02 16:21:36.25 kernel  Sybase, Inc.  All rights reserved.
00:00000:00000:2005/08/02 16:21:36.26 kernel  Unpublished rights reserved under U.S. copyright laws.
00:00000:00000:2005/08/02 16:21:36.26 kernel
00:00000:00000:2005/08/02 16:21:36.26 kernel  This software contains confidential and trade secret information of Sybase,
00:00000:00000:2005/08/02 16:21:36.26 kernel  Inc.   Use,  duplication or disclosure of the software and documentation by
00:00000:00000:2005/08/02 16:21:36.26 kernel  the  U.S.  Government  is  subject  to  restrictions set forth in a license
00:00000:00000:2005/08/02 16:21:36.26 kernel  agreement  between  the  Government  and  Sybase,  Inc.  or  other  written
00:00000:00000:2005/08/02 16:21:36.26 kernel  agreement  specifying  the  Government's rights to use the software and any
00:00000:00000:2005/08/02 16:21:36.26 kernel  applicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2005/08/02 16:21:36.26 kernel  Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608, USA
00:00000:00000:2005/08/02 16:21:36.26 kernel  Using '/opt/sybase/SYB.cfg' for configuration information.
00:00000:00000:2005/08/02 16:21:36.26 kernel  Logging ASE messages in file '/opt/sybase/ASE-12_0/install/SYB.log'.
00:00000:00000:2005/08/02 16:21:36.27 kernel  Directory Control Layer (DCL) using directory driver: InterfacesDriver
00:00000:00000:2005/08/02 16:21:36.27 kernel  Network and device connection limit is 1014.
00:00000:00000:2005/08/02 16:21:36.28 server  Number of proc buffers allocated: 4095.
00:00000:00000:2005/08/02 16:21:36.32 server  Number of blocks left for proc headers: 4056.
00:00000:00000:2005/08/02 16:21:36.32 server  Proc header memory allocated 2028 pages for each per engine cache
00:00000:00000:2005/08/02 16:21:36.32 server   Memory allocated for the default data cache cachelet 1: 30820 Kb
00:00000:00000:2005/08/02 16:21:36.33 server  Size of the 2K memory pool: 30820 Kb
00:00000:00000:2005/08/02 16:21:36.33 kernel  Initializing virtual device 0, '/data/master_dev.dat' with dsync 'on'.
00:00000:00000:2005/08/02 16:21:36.33 kernel  Virtual device 0 started using asynchronous i/o.
00:00000:00000:2005/08/02 16:21:36.33 kernel  Worker Thread Manager is not enabled for use in SQL Server.
00:00000:00000:2005/08/02 16:21:36.33 kernel  Either the config parameter 'use security services' is set to 0, or ASE does not suppo
rt use of external security mechanisms on this platform. The Security Control Layer will not be initialized. No external security me
chanisms will be supported.
00:00000:00000:2005/08/02 16:21:36.33 kernel  engine 0, os pid 7359  online
00:00000:00000:2005/08/02 16:21:36.33 server  No active traceflags
00:00000:00001:2005/08/02 16:21:36.33 kernel  Component Integration Services loaded; version 'Component Integration Services/12.0/P/
SWR 8774 ESD 1/Sun_svr4/OS 5.6/1580/32bit/FBO/Tue Dec  7 03:10:20 1999'.
00:00000:00001:2005/08/02 16:21:36.33 kernel  Component Integration Services: using 'Sybase Client-Library/12.0/P/SPARC/Solaris 2.5.
1/1/OPT/Mon Oct  4 12:07:29 1999'
00:00000:00001:2005/08/02 16:21:36.33 server  Opening Master Database ...
00:00000:00001:2005/08/02 16:21:36.34 server  Loading SQL Server's default sort order and character set
00:00000:00001:2005/08/02 16:21:36.34 server  Loaded default Unilib conversion handle.
00:00000:00002:2005/08/02 16:21:36.34 kernel  ninit:0: listener type: master
"SYB.log" 1648 lines, 166826 characters
00:00000:00001:2005/08/16 15:39:54.81 server  Error: 3414, Severity: 17, State: 3
00:00000:00001:2005/08/16 15:39:54.81 server  Database 'fmdb' (dbid 5): Recovery failed. Check the SQL Server errorlog for further i
nformation as to the cause.
00:00000:00001:2005/08/16 15:39:54.81 server  Recovering database 'pmdb'.
00:00000:00001:2005/08/16 15:39:54.81 server  Error: 840, Severity: 17, State: 2
00:00000:00001:2005/08/16 15:39:54.81 server  Device 'pmdb_log' (with physical name '/data/pmdb.log', and virtual device number 15)
has not been correctly activated at startup time.  Please contact a user with System Administrator (SA) role.
00:00000:00001:2005/08/16 15:39:54.81 server  Error: 3414, Severity: 17, State: 3
00:00000:00001:2005/08/16 15:39:54.81 server  Database 'pmdb' (dbid 6): Recovery failed. Check the SQL Server errorlog for further i
nformation as to the cause.
00:00000:00001:2005/08/16 15:39:54.81 server  Recovering database 'sysmdb'.
00:00000:00001:2005/08/16 15:39:54.81 server  Error: 840, Severity: 17, State: 2
00:00000:00001:2005/08/16 15:39:54.81 server  Device 'sysmdb_log' (with physical name '/data/sysmdb.log', and virtual device number
17) has not been correctly activated at startup time.  Please contact a user with System Administrator (SA) role.
00:00000:00001:2005/08/16 15:39:54.81 server  Error: 3414, Severity: 17, State: 3
00:00000:00001:2005/08/16 15:39:54.81 server  Database 'sysmdb' (dbid 7): Recovery failed. Check the SQL Server errorlog for further
information as to the cause.
00:00000:00001:2005/08/16 15:39:54.81 server  Recovery complete.
00:00000:00001:2005/08/16 15:39:54.81 server  SQL Server's default sort order is:
00:00000:00001:2005/08/16 15:39:54.81 server    'bin_cp936' (ID = 50)
00:00000:00001:2005/08/16 15:39:54.81 server  on top of default character set:
00:00000:00001:2005/08/16 15:39:54.81 server    'cp936' (ID = 171).

fbirds

Error 3414
Severity
10
Error Message
Database '%.*s' (dbid %d): Recovery failed. Check the
SQL Server errorlog for further information as to the
cause.
Explanation
This error occurs during startup when Adaptive Server could not complete
the recovery of the database listed in the error message.
You cannot use the database until whatever caused the error has been
corrected because Adaptive Server marks the database suspect.
Error 926 is a related error which is raised when attempting to access a
database that could not recover. Refer to Error 926.
Action
To determine why recovery failed, examine the Adaptive Server error log
for any errors prior to the 3414 error. It is important to identify the errors
before the first occurrence of the 3414 error because subsequent attempts
to start Adaptive Server may not give the detailed error information you
need to diagnose the problem.
If you do not have sufficient information to recover from the previous
errors, you can recover from known, clean backups or contact Sybase
Technical Support for assistance.
Version in Which This Error is Raised
11.0.x and later

fbirds

Error 840
Severity
17
Error Message
Device '%.*s' (with physical name '%.*s', and virtual
device number %d) has not been correctly activated
at startup time. Please contact a user with System
Administrator (SA) role.
¨ Note This error may be caused by a hardware problem.
Explanation
This error can occur when Adaptive Server is unable to access a device
during startup.
This error can occur for any of the following reasons:
• A database device is offline.
• A database device or file has been removed or renamed.
• A database device or file is inaccessible to Adaptive Server for any
other reason, such as insufficient permissions.
Action
1. Examine the availability and condition of the device involved using
your standard operating system procedures, and make sure the device
is accessible.
2. Adaptive Server will not be able to recover any databases that have
space on the device upon restarting because an 840 error will mark the
databases suspect. If you know that the databases were marked suspect
because the device was unavailable, resolve the problem with the device
and reset the status of the databases to allow recovery to continue.
WARNING! Do not use these procedures if other errors in the error log near the 840
error message suggest that the databases may have been marked suspect
for some other reason.
316
Buffer Manager Errors Error 840
Reset the suspect status using one of the methods supplied in “How to
Reset a Database's “suspect” Status” in “Encyclopedia of Tasks”.
After you reset the status, execute the dbcc checkdb and dbcc checkalloc
commands for the affected databases to ensure that no other damage was
caused by the device being unavailable. If other errors occur, refer to the
writeups for those errors in this manual. If errors still persist, call Sybase
Technical Support.
Version in Which This Error is Raised
11.0.x and later

fbirds

这是troubleshooting上的解释。楼主的和我们平时遇到的问题不一样。我们平时直接修改系统表上该数据库的状态后，进入后再dump日志后，修改回来就正常了。楼主的好象设备有点问题。

pepsion

谢谢各位，如何看出是设备有问题？
在data目录下有sysmdb.data没有sysm.log和sysm.dat文件