sl0325 发表于 2011-12-22 16:28

数据库日志文件丢失,怎么能读取数据

请教各位高手:
   我的数据库不小心删除了一个日志设备,数据设备都在,目前建立了一个测试库,和以前的数据库设备名相同,大小一样,把数据设备文件覆盖到测试库里,想能读取一些有用的数据出来。启动服务器报错,请教各位高手如何处理,日志如下:



00:00000:00001:2011/12/22 16:05:23.84 serverDatabase 'sybsystemdb', checkpoint=(1028, 7), first=(17179870212, 7), last=(1028, 7).
00:00000:00001:2011/12/22 16:05:23.84 serverCompleted estimating recovery log boundaries for database 'sybsystemdb'.
00:00000:00001:2011/12/22 16:05:23.84 serverStarted ANALYSIS pass for database 'sybsystemdb'.
00:00000:00001:2011/12/22 16:05:23.84 serverCompleted ANALYSIS pass for database 'sybsystemdb'.
00:00000:00001:2011/12/22 16:05:23.84 serverLog contains all committed transactions until 2011/12/21 16:47:07.84 for database sybsystemdb.
00:00000:00001:2011/12/22 16:05:23.84 serverStarted REDO pass for database 'sybsystemdb'. The total number of log records to process is 1.
00:00000:00001:2011/12/22 16:05:23.84 serverCompleted REDO pass for database 'sybsystemdb'.
00:00000:00001:2011/12/22 16:05:23.84 serverRecovery of database 'sybsystemdb' will undo incomplete nested top actions.
00:00000:00001:2011/12/22 16:05:23.84 serverStarted recovery checkpoint for database 'sybsystemdb'.
00:00000:00001:2011/12/22 16:05:23.85 serverCompleted recovery checkpoint for database 'sybsystemdb'.
00:00000:00001:2011/12/22 16:05:23.87 serverStarted filling free space info for database 'sybsystemdb'.
00:00000:00001:2011/12/22 16:05:23.89 serverCompleted filling free space info for database 'sybsystemdb'.
00:00000:00001:2011/12/22 16:05:23.90 serverStarted cleaning up the default data cache for database 'sybsystemdb'.
00:00000:00001:2011/12/22 16:05:24.28 serverCompleted cleaning up the default data cache for database 'sybsystemdb'.
00:00000:00001:2011/12/22 16:05:24.28 serverBoot Count: 8
00:00000:00001:2011/12/22 16:05:24.29 serverChecking external objects.
00:00000:00001:2011/12/22 16:05:24.31 serverThe transaction log in the database 'sybsystemdb' will use I/O size of 2 Kb.
00:00000:00001:2011/12/22 16:05:24.69 serverResident Node id: f7992c3e37c5
00:00000:00001:2011/12/22 16:05:24.69 serverTransaction coordinator initialized.
00:00000:00001:2011/12/22 16:05:24.69 serverDatabase 'sybsystemdb' is now online.
00:00000:00001:2011/12/22 16:05:24.72 serverRecovering database 'model'.
00:00000:00001:2011/12/22 16:05:24.73 serverStarted estimating recovery log boundaries for database 'model'.
00:00000:00001:2011/12/22 16:05:24.75 serverDatabase 'model', checkpoint=(1015, 3), first=(17179870199, 3), last=(1015, 3).
00:00000:00001:2011/12/22 16:05:24.75 serverCompleted estimating recovery log boundaries for database 'model'.
00:00000:00001:2011/12/22 16:05:24.75 serverStarted ANALYSIS pass for database 'model'.
00:00000:00001:2011/12/22 16:05:24.75 serverCompleted ANALYSIS pass for database 'model'.
00:00000:00001:2011/12/22 16:05:24.75 serverLog contains all committed transactions until 2011/12/21 16:47:07.84 for database model.
00:00000:00001:2011/12/22 16:05:24.75 serverStarted REDO pass for database 'model'. The total number of log records to process is 1.
00:00000:00001:2011/12/22 16:05:24.75 serverCompleted REDO pass for database 'model'.
00:00000:00001:2011/12/22 16:05:24.75 serverRecovery of database 'model' will undo incomplete nested top actions.
00:00000:00001:2011/12/22 16:05:24.75 serverStarted recovery checkpoint for database 'model'.
00:00000:00001:2011/12/22 16:05:24.78 serverCompleted recovery checkpoint for database 'model'.
00:00000:00001:2011/12/22 16:05:24.80 serverStarted filling free space info for database 'model'.
00:00000:00001:2011/12/22 16:05:24.82 serverCompleted filling free space info for database 'model'.
00:00000:00001:2011/12/22 16:05:24.83 serverStarted cleaning up the default data cache for database 'model'.
00:00000:00001:2011/12/22 16:05:25.21 serverCompleted cleaning up the default data cache for database 'model'.
00:00000:00001:2011/12/22 16:05:25.22 serverChecking external objects.
00:00000:00001:2011/12/22 16:05:25.26 serverThe transaction log in the database 'model' will use I/O size of 2 Kb.
00:00000:00001:2011/12/22 16:05:25.65 serverDatabase 'model' is now online.
00:00000:00001:2011/12/22 16:05:25.65 serverThe logical pagesize of the server is 2 Kb.
00:00000:00001:2011/12/22 16:05:25.65 server0 dump conditions detected at boot time
00:00000:00001:2011/12/22 16:05:25.66 serverClearing temp db
00:00000:00001:2011/12/22 16:05:32.41 serverProcessed 3073 allocation unit(s) out of 30728 units (allocation page 786432). 10% completed.
00:00000:00001:2011/12/22 16:05:38.80 serverProcessed 6146 allocation unit(s) out of 30728 units (allocation page 1573120). 20% completed.
00:00000:00001:2011/12/22 16:05:45.34 serverProcessed 9219 allocation unit(s) out of 30728 units (allocation page 2359808). 30% completed.
00:00000:00001:2011/12/22 16:05:51.82 serverProcessed 12292 allocation unit(s) out of 30728 units (allocation page 3146496). 40% completed.
00:00000:00001:2011/12/22 16:05:58.43 serverProcessed 15364 allocation unit(s) out of 30728 units (allocation page 3932928). 50% completed.
00:00000:00001:2011/12/22 16:06:05.83 serverProcessed 18437 allocation unit(s) out of 30728 units (allocation page 4719616). 60% completed.
00:00000:00001:2011/12/22 16:06:14.43 serverProcessed 21510 allocation unit(s) out of 30728 units (allocation page 5506304). 70% completed.
00:00000:00001:2011/12/22 16:06:23.65 serverProcessed 24583 allocation unit(s) out of 30728 units (allocation page 6292992). 80% completed.
00:00000:00001:2011/12/22 16:06:33.05 serverProcessed 27656 allocation unit(s) out of 30728 units (allocation page 7079680). 90% completed.
00:00000:00001:2011/12/22 16:06:43.24 serverProcessed 30728 allocation unit(s) out of 30728 units (allocation page 7866112). 100% completed.
00:00000:00001:2011/12/22 16:06:45.54 serverThe transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2011/12/22 16:06:45.94 serverDatabase 'tempdb' is now online.
00:00000:00001:2011/12/22 16:06:46.00 serverRecovering database 'sybsystemprocs'.
00:00000:00001:2011/12/22 16:06:46.01 serverStarted estimating recovery log boundaries for database 'sybsystemprocs'.
00:00000:00001:2011/12/22 16:06:46.02 serverDatabase 'sybsystemprocs', checkpoint=(111904, 20), first=(17179981088, 20), last=(111904, 20).
00:00000:00001:2011/12/22 16:06:46.02 serverCompleted estimating recovery log boundaries for database 'sybsystemprocs'.
00:00000:00001:2011/12/22 16:06:46.02 serverStarted ANALYSIS pass for database 'sybsystemprocs'.
00:00000:00001:2011/12/22 16:06:46.02 serverCompleted ANALYSIS pass for database 'sybsystemprocs'.
00:00000:00001:2011/12/22 16:06:46.02 serverLog contains all committed transactions until 2011/12/22 09:07:28.36 for database sybsystemprocs.
00:00000:00001:2011/12/22 16:06:46.02 serverStarted REDO pass for database 'sybsystemprocs'. The total number of log records to process is 1.
00:00000:00001:2011/12/22 16:06:46.02 serverCompleted REDO pass for database 'sybsystemprocs'.
00:00000:00001:2011/12/22 16:06:46.02 serverRecovery of database 'sybsystemprocs' will undo incomplete nested top actions.
00:00000:00001:2011/12/22 16:06:46.02 serverStarted recovery checkpoint for database 'sybsystemprocs'.
00:00000:00001:2011/12/22 16:06:46.04 serverCompleted recovery checkpoint for database 'sybsystemprocs'.
00:00000:00001:2011/12/22 16:06:46.06 serverStarted filling free space info for database 'sybsystemprocs'.
00:00000:00001:2011/12/22 16:06:46.16 serverCompleted filling free space info for database 'sybsystemprocs'.
00:00000:00001:2011/12/22 16:06:46.17 serverStarted cleaning up the default data cache for database 'sybsystemprocs'.
00:00000:00001:2011/12/22 16:06:46.55 serverCompleted cleaning up the default data cache for database 'sybsystemprocs'.
00:00000:00001:2011/12/22 16:06:46.56 serverChecking external objects.
00:00000:00001:2011/12/22 16:06:46.58 serverThe transaction log in the database 'sybsystemprocs' will use I/O size of 2 Kb.
00:00000:00001:2011/12/22 16:06:46.96 serverDatabase 'sybsystemprocs' is now online.
00:00000:00011:2011/12/22 16:06:47.01 kernelnetwork name MZEVA, interface IPv4, address 192.168.1.6, type tcp, port 4100, filter NONE
01:00000:00000:2011/12/22 16:06:47.02 kernelengine 1, os pid 3913online
01:00000:00000:2011/12/22 16:06:47.03 kernelEncryption provider initialization succeeded on engine 1.
02:00000:00000:2011/12/22 16:06:47.04 kernelengine 2, os pid 3919online
02:00000:00000:2011/12/22 16:06:47.05 kernelEncryption provider initialization succeeded on engine 2.
03:00000:00000:2011/12/22 16:06:47.06 kernelengine 3, os pid 3925online
03:00000:00000:2011/12/22 16:06:47.06 kernelEncryption provider initialization succeeded on engine 3.
04:00000:00000:2011/12/22 16:06:47.07 kernelengine 4, os pid 3931online
04:00000:00000:2011/12/22 16:06:47.08 kernelEncryption provider initialization succeeded on engine 4.
05:00000:00000:2011/12/22 16:06:47.09 kernelengine 5, os pid 3937online
05:00000:00000:2011/12/22 16:06:47.09 kernelEncryption provider initialization succeeded on engine 5.
06:00000:00000:2011/12/22 16:06:47.10 kernelengine 6, os pid 3943online
06:00000:00000:2011/12/22 16:06:47.11 kernelEncryption provider initialization succeeded on engine 6.
07:00000:00000:2011/12/22 16:06:47.12 kernelengine 7, os pid 3949online
07:00000:00000:2011/12/22 16:06:47.13 kernelEncryption provider initialization succeeded on engine 7.
08:00000:00000:2011/12/22 16:06:47.13 kernelengine 8, os pid 3955online
08:00000:00000:2011/12/22 16:06:47.14 kernelEncryption provider initialization succeeded on engine 8.
09:00000:00000:2011/12/22 16:06:47.15 kernelengine 9, os pid 3961online
09:00000:00000:2011/12/22 16:06:47.16 kernelEncryption provider initialization succeeded on engine 9.
10:00000:00000:2011/12/22 16:06:47.16 kernelengine 10, os pid 3967online
10:00000:00000:2011/12/22 16:06:47.17 kernelEncryption provider initialization succeeded on engine 10.
11:00000:00000:2011/12/22 16:06:47.18 kernelengine 11, os pid 3973online
11:00000:00000:2011/12/22 16:06:47.19 kernelEncryption provider initialization succeeded on engine 11.
12:00000:00000:2011/12/22 16:06:47.20 kernelengine 12, os pid 3979online
12:00000:00000:2011/12/22 16:06:47.20 kernelEncryption provider initialization succeeded on engine 12.
13:00000:00000:2011/12/22 16:06:47.21 kernelengine 13, os pid 3985online
13:00000:00000:2011/12/22 16:06:47.22 kernelEncryption provider initialization succeeded on engine 13.
14:00000:00000:2011/12/22 16:06:47.23 kernelengine 14, os pid 3991online
14:00000:00000:2011/12/22 16:06:47.23 kernelEncryption provider initialization succeeded on engine 14.
15:00000:00000:2011/12/22 16:06:47.24 kernelengine 15, os pid 3997online
15:00000:00000:2011/12/22 16:06:47.25 kernelEncryption provider initialization succeeded on engine 15.
16:00000:00000:2011/12/22 16:06:47.26 kernelengine 16, os pid 4003online
16:00000:00000:2011/12/22 16:06:47.27 kernelEncryption provider initialization succeeded on engine 16.
17:00000:00000:2011/12/22 16:06:47.27 kernelengine 17, os pid 4009online
17:00000:00000:2011/12/22 16:06:47.28 kernelEncryption provider initialization succeeded on engine 17.
18:00000:00000:2011/12/22 16:06:47.29 kernelengine 18, os pid 4015online
18:00000:00000:2011/12/22 16:06:47.30 kernelEncryption provider initialization succeeded on engine 18.
19:00000:00000:2011/12/22 16:06:47.31 kernelengine 19, os pid 4021online
19:00000:00000:2011/12/22 16:06:47.31 kernelEncryption provider initialization succeeded on engine 19.
00:00000:00001:2011/12/22 16:06:47.62 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.64 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.67 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.69 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.72 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.74 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.77 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.79 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.82 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.84 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.87 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.89 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.91 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.94 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.96 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:47.99 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.01 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.04 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.06 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.09 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.11 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.14 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.16 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.19 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.21 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.24 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.26 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.29 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.31 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.34 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.36 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.39 serverThe wash size of the 2K buffer pool in cache default data cache has been changed from 52428 Kb to 31458 Kb due to a change in the size of the pool.
00:00000:00001:2011/12/22 16:06:48.43 serverRecovery has tuned the size of '16K' pool in 'default data cache' to benefit recovery performance. The original configuration will be restored at the end of recovery.
00:00000:00001:2011/12/22 16:06:48.43 serverRecovery has tuned the size of '2K' pool in 'default data cache' to benefit recovery performance. The original configuration will be restored at the end of recovery.
00:00000:00001:2011/12/22 16:06:48.43 serverRecovery has tuned the '16K' pool in 'default data cache' by changing its 'local async prefetch limit' from 10 to 80. The original configuration will be restored at the end of recovery.
00:00000:00001:2011/12/22 16:06:48.43 serverRecovery has tuned the '2K' pool in 'default data cache' by changing its 'local async prefetch limit' from 10 to 80. The original configuration will be restored at the end of recovery.
00:00000:00001:2011/12/22 16:06:48.43 serverThe server will recover databases serially.
00:00000:00001:2011/12/22 16:06:48.53 serverStarting diagnostics for read failure:
00:00000:00001:2011/12/22 16:06:48.53 serverDevice Information:

sybman 发表于 2011-12-22 21:10

最后两行是关键,可是你没有把错误信息贴出来。
.
00:00000:00001:2011/12/22 16:06:48.53 serverStarting diagnostics for read failure:
00:00000:00001:2011/12/22 16:06:48.53 serverDevice Information:

zhaopingzi 发表于 2011-12-23 00:21

楼主可以尝试做下 rebuild log

hobbylu 发表于 2011-12-23 08:33

你尝试过-32768模式启动数据库没有?

sl0325 发表于 2011-12-23 08:51

00:00000:00001:2011/12/22 16:06:48.53 serverStarting diagnostics for read failure:
00:00000:00001:2011/12/22 16:06:48.53 serverDevice Information:
                               Device number = 11
                               Phyname = /opt/hisdata/bsrun6.dat
00:00000:00001:2011/12/22 16:06:48.53 serverBuffer Information:
                               Buf addr = 0x0x406f5c1a8, Mass addr = 0x0x406f5c1a8
                               Buf pageno = 43233159, Mass pageno = 43233159, dbid = 4
00:00000:00001:2011/12/22 16:06:48.53 server
                               Buf virtpg = 43233159, Mass virtpg = 4833159
                               Buf stat = 0x1, Mass stat = 0x1008
                               Mass keep = 1, Mass awaited = 0
00:00000:00001:2011/12/22 16:06:48.53 serverPage Information from first read attempt: Page read from disk ppageno = 45793159, pptnid = 1409437064, pindid = 0 pnextpg = 45793151, pprevpg = 46005240 plevel = 0, pstat = 0x11 pts_hi = 3, pts_lo = 251859148
00:00000:00001:2011/12/22 16:06:48.53 serverPage Information from second read attempt: Page read from disk ppageno = 45793159, pptnid = 1409437064, pindid = 0 pnextpg = 45793151, pprevpg = 46005240 plevel = 0, pstat = 0x11 pts_hi = 3, pts_lo = 251859148
00:00000:00001:2011/12/22 16:06:48.53 serverSDES Information:
                               dbid = 4, objid = 14, sptnid = 14 scur.pageid = 43233159
                               sstat = 0x0, sstat2 = 0x0
                               suid = 1, cacheid = 0
00:00000:00001:2011/12/22 16:06:48.53 serverPSS Information:
                               pstat = 0x1000, pcurdb = 1, pspid = 1
                               p2stat = 0x1110, p3stat = 0x904
                               plasterror = 0, preverror = 0, pattention = 0
00:00000:00001:2011/12/22 16:06:48.53 serverEnd diagnostics for read failure:
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x00000000012fcd13 pcstkwalk+0x323()
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x00000000012fc7c0 ucstkgentrace+0x170()
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x0000000001295fa9 ucbacktrace+0x69()
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x0000000000971b1d wrongpage__print_diagnostic+0x2ed()
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x0000000000971086 wrongpage+0x2c6()
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x000000000096ddad getpage_with_validation+0xbed()
00:00000:00001:2011/12/22 16:06:48.56 kernel
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x00000000008300de pg_fill_supergam+0x12e()
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x00000000008074ae db_fill+0x27e()
00:00000:00001:2011/12/22 16:06:48.56 kernel
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x000000000080f48c dbt(float, int, long, long)+0x16c()
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x000000000080d84b dbt_get+0x7fb()
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x0000000000802fae dbcontext_change+0x2e()
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x0000000000803565 usedb+0x35()
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x0000000000a7c75a boot__recover_and_online+0x3a()
00:00000:00001:2011/12/22 16:06:48.56 kernel
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x0000000000a7e909 rec__boot_recover_dbs+0xe9()
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x0000000000a7abd3 rec_run_parallel_recovery+0x2d3()
00:00000:00001:2011/12/22 16:06:48.56 kernel
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x0000000000a7e424 dorecover+0x174()
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x0000000000727b2d ds__recoverdbs+0x52d()
00:00000:00001:2011/12/22 16:06:48.56 kernelpc: 0x00000000007214d7 dsinit+0xad7()
00:00000:00001:2011/12/22 16:06:48.56 kernelend of stack trace, spid 1, kpid 196611, suid 0
00:00000:00001:2011/12/22 16:06:48.57 serverRecovering database 'bsrun201112'.
00:00000:00001:2011/12/22 16:06:48.57 serverStarted estimating recovery log boundaries for database 'bsrun201112'.
00:00000:00001:2011/12/22 16:06:48.60 serverStarting diagnostics for read failure:
00:00000:00001:2011/12/22 16:06:48.60 serverDevice Information:
                               Device number = 8
                               Phyname = /opt/hisdata/bsrun4.dat
00:00000:00001:2011/12/22 16:06:48.60 serverBuffer Information:
                               Buf addr = 0x0x40b629200, Mass addr = 0x0x40b629200
                               Buf pageno = 25465968, Mass pageno = 25465968, dbid = 4
00:00000:00001:2011/12/22 16:06:48.60 server
                               Buf virtpg = 25465968, Mass virtpg = 2425968
                               Buf stat = 0x1, Mass stat = 0x1008
                               Mass keep = 1, Mass awaited = 0
00:00000:00001:2011/12/22 16:06:48.60 serverPage Information from first read attempt: Page read from disk ppageno = 28025968, pptnid = 1409437064, pindid = 0 pnextpg = 28025958, pprevpg = 27980487 plevel = 0, pstat = 0x11 pts_hi = 2, pts_lo = 621732403
00:00000:00001:2011/12/22 16:06:48.60 serverPage Information from second read attempt: Page read from disk ppageno = 28025968, pptnid = 1409437064, pindid = 0 pnextpg = 28025958, pprevpg = 27980487 plevel = 0, pstat = 0x11 pts_hi = 2, pts_lo = 621732403
00:00000:00001:2011/12/22 16:06:48.60 serverSDES Information:
                               dbid = 4, objid = 8, sptnid = 8 scur.pageid = 25465968
                               sstat = 0x4001, sstat2 = 0x4000000
                               suid = 1, cacheid = 0
00:00000:00001:2011/12/22 16:06:48.60 serverPSS Information:
                               pstat = 0x1000, pcurdb = 4, pspid = 1
                               p2stat = 0x1110, p3stat = 0x10000804
                               plasterror = 0, preverror = 0, pattention = 0
00:00000:00001:2011/12/22 16:06:48.60 serverEnd diagnostics for read failure:
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x00000000012fcd13 pcstkwalk+0x323()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x00000000012fc7c0 ucstkgentrace+0x170()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x0000000001295fa9 ucbacktrace+0x69()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x0000000000971b1d wrongpage__print_diagnostic+0x2ed()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x0000000000971086 wrongpage+0x2c6()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x000000000096ddad getpage_with_validation+0xbed()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x0000000000972083 getrow+0x43()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x00000000009a2f1f apl__startscan+0x14ef()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x00000000009a12f1 startptnscan+0x381()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x00000000009b8b32 xsc__syslogs_setscan+0x1b2()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x00000000009b82f8 xls_startscan+0x178()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x000000000093c0e3 ckpt_get_record+0x53()
00:00000:00001:2011/12/22 16:06:48.60 kernel
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x0000000000a81aaa rec_logbounds+0x2ba()
00:00000:00001:2011/12/22 16:06:48.60 kernel
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x0000000000a7f995 recovery+0x4a5()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x0000000000a7c7ce boot__recover_and_online+0xae()
00:00000:00001:2011/12/22 16:06:48.60 kernel
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x0000000000a7e909 rec__boot_recover_dbs+0xe9()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x0000000000a7abd3 rec_run_parallel_recovery+0x2d3()
00:00000:00001:2011/12/22 16:06:48.60 kernel
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x0000000000a7e424 dorecover+0x174()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x0000000000727b2d ds__recoverdbs+0x52d()
00:00000:00001:2011/12/22 16:06:48.60 kernelpc: 0x00000000007214d7 dsinit+0xad7()
00:00000:00001:2011/12/22 16:06:48.60 kernelend of stack trace, spid 1, kpid 196611, suid 0
00:00000:00001:2011/12/22 16:06:48.61 serverError: 695, Severity: 21, State: 1
00:00000:00001:2011/12/22 16:06:48.61 serverAn attempt was made to read logical page '25465968' for database 'bsrun201112' (4), object 'syslogs' (8), index 'syslogs' (0), partition 'syslogs_8' (8) from disk. Wrong logical page '28025968' was brought into cache 'default data cache'.
00:00000:00001:2011/12/22 16:06:48.62 serverError: 3414, Severity: 21, State: 1
00:00000:00001:2011/12/22 16:06:48.62 serverDatabase 'bsrun201112' (dbid 4): Recovery failed. Check the ASE errorlog for further information as to the cause.
00:00000:00001:2011/12/22 16:06:48.62 serverRecovery has restored the value of 'local async prefetch limit' for '16K' pool in 'default data cache' from '80' to 'DEFAULT'.
00:00000:00001:2011/12/22 16:06:48.62 serverRecovery has restored the value of 'local async prefetch limit' for '2K' pool in 'default data cache' from '80' to 'DEFAULT'.
00:00000:00001:2011/12/22 16:06:49.17 serverBufunhash: Buffer 0x40b629200 from database id 4 has page number 28025968
in the page header and page number 25465968 in the buffer header. Buffer will be unhashed,
no action is necessary. Printing headers for diagnostics:
00:00000:00001:2011/12/22 16:06:49.17 serverMass: 0x0x40b629200 Buffer: 0x0x40b629200
-Mass pgno: 25465968 vdev: 8 virtpg: 2425968 dbid: 4 stat: 0x4001000 keep: 0 awaited: 0
tripsleft: 0, flushseq: 0 dirty seq: 0 filthyseq: 0
-Buf pgno: 25465968 vdev: 8 virtpg: 2425968 stat: 0x1 bpage: 0xbabbd000 linked: ( lru)
00:00000:00001:2011/12/22 16:06:49.17 serverPage: 0x3babbd000 pageno: 28025968 objid: 1409437064 indid: 0
- nextpg: 28025958 prevpg: 27980487 pstat: 0x11 ts: (2, 621732403) nextrno: 10
- freeoff: 1503 minlen: 96 level: 0
00:00000:00001:2011/12/22 16:06:49.20 serverRecovery has restored the original size for '16K' pool and '2K' pool in 'default data cache'.
00:00000:00001:2011/12/22 16:06:49.20 serverRecovery complete.
00:00000:00001:2011/12/22 16:06:49.20 serverASE's default unicode sort order is 'binary'.
00:00000:00001:2011/12/22 16:06:49.20 serverASE's default sort order is:
00:00000:00001:2011/12/22 16:06:49.20 server        'bin_iso_1' (ID = 50)
00:00000:00001:2011/12/22 16:06:49.20 serveron top of default character set:
00:00000:00001:2011/12/22 16:06:49.20 server        'iso_1' (ID = 1).
00:00000:00001:2011/12/22 16:06:49.20 serverMaster device size: 300 megabytes, or 153600 virtual pages. (A virtual page is 2048 bytes.)
00:00000:00001:2011/12/22 16:06:49.21 kernelWarning: Cannot set console to nonblocking mode, switching to blocking mode.
01:00000:00014:2011/12/22 16:09:53.29 kernelInitializing virtual device 19, '/opt/hisdata/test1.dat' with dsync 'on'.
01:00000:00014:2011/12/22 16:09:53.29 kernelVirtual device 19 started using asynchronous i/o.
01:00000:00014:2011/12/22 16:09:53.29 kernelInitializing device /opt/hisdata/test1.dat from offset 0 with zeros.
01:00000:00014:2011/12/22 16:09:53.37 kernelFinished initialization.
01:00000:00014:2011/12/22 16:10:10.93 kernelInitializing virtual device 20, '/opt/hisdata/test_log1.dat' with dsync 'on'.
01:00000:00014:2011/12/22 16:10:10.93 kernelVirtual device 20 started using asynchronous i/o.
01:00000:00014:2011/12/22 16:10:10.93 kernelInitializing device /opt/hisdata/test_log1.dat from offset 0 with zeros.
01:00000:00014:2011/12/22 16:10:11.02 kernelFinished initialization.

-32768模式启动数据库后,不能USE db
rebuild log也失败了。
andkylee的帖子 :ASE15.0.3升级后启动不起来了中使用了修改设备文件的方法,但不知道如何去按那个方法操作解决我现在的故障。
请高手们给个建议!!

Eisen 发表于 2011-12-23 10:03

昨天无聊,在自己机器上搞了个库,然后把log设备删了,成功重现你的错误,但是在采用log设备覆盖然后rebuild log后成功恢复。除了在途transaction丢失外没有丢失任何已commit数据。
接着无聊又再次配置了复制,并重玩一趟,一样成功。按说照大家给你的做法应该没错了,除非——你的新log设备大小或生成版本不对。

sl0325 发表于 2011-12-23 12:25

按照大家的建议做rebuild_log时,kernel setting console to nonblocking mode.failed attempt to remove old log extents.
rebuild失败,接着该如何处理呢?

sl0325 发表于 2011-12-23 14:54

启动日志报错如下:

00:00000:00001:2011/12/22 16:06:48.61 serverError: 695, Severity: 21, State: 1
00:00000:00001:2011/12/22 16:06:48.61 serverAn attempt was made to read logical page '25465968' for database 'bsrun201112' (4), object 'syslogs' (8), index 'syslogs' (0), partition 'syslogs_8' (8) from disk. Wrong logical page '28025968' was brought into cache 'default data cache'.
00:00000:00001:2011/12/22 16:06:48.62 serverError: 3414, Severity: 21, State: 1
00:00000:00001:2011/12/22 16:06:48.62 serverDatabase 'bsrun201112' (dbid 4): Recovery failed. Check the ASE errorlog for further information as to the cause.
00:00000:00001:2011/12/22 16:06:48.62 serverRecovery has restored the value of 'local async prefetch limit' for '16K' pool in 'default data cache' from '80' to 'DEFAULT'.
00:00000:00001:2011/12/22 16:06:48.62 serverRecovery has restored the value of 'local async prefetch limit' for '2K' pool in 'default data cache' from '80' to 'DEFAULT'.
00:00000:00001:2011/12/22 16:06:49.17 serverBufunhash: Buffer 0x40b629200 from database id 4 has page number 28025968
in the page header and page number 25465968 in the buffer header. Buffer will be unhashed,
no action is necessary. Printing headers for diagnostics:
00:00000:00001:2011/12/22 16:06:49.17 serverMass: 0x0x40b629200 Buffer: 0x0x40b629200
-Mass pgno: 25465968 vdev: 8 virtpg: 2425968 dbid: 4 stat: 0x4001000 keep: 0 awaited: 0
tripsleft: 0, flushseq: 0 dirty seq: 0 filthyseq: 0
-Buf pgno: 25465968 vdev: 8 virtpg: 2425968 stat: 0x1 bpage: 0xbabbd000 linked: ( lru)
00:00000:00001:2011/12/22 16:06:49.17 serverPage: 0x3babbd000 pageno: 28025968 objid: 1409437064 indid: 0
- nextpg: 28025958 prevpg: 27980487 pstat: 0x11 ts: (2, 621732403) nextrno: 10
- freeoff: 1503 minlen: 96 level: 0

sybman 发表于 2011-12-23 21:43

如果rebuild_log不行,建议你用 dbcc save_rebuild_log()试试看。

andkylee 发表于 2011-12-24 11:16

Eisen,采用log设备覆盖, 你这个log设备从哪里来的?
页: [1] 2 3 4
查看完整版本: 数据库日志文件丢失,怎么能读取数据