2,596
社区成员
发帖
与我相关
我的任务
分享数据库恢复时出错
Server message 3216, Severity 10, State 3, Line 1
Server message 602801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
提示信息：
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 304201, Severity 1, State 1, Line 0
Server message 3127, Severity 10, State 1, Line 1
Server message 3128, Severity 10, State 1, Line 1
Server message 3406, Severity 10, State 1, Line 1
Server message 3407, Severity 10, State 1, Line 1
Server message 3137, Severity 10, State 1, Line 1
Server message 602801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
提示信息：
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 405801, Severity 1, State 1, Line 0
Server message 304201, Severity 1, State 1, Line 0
Server message 3127, Severity 10, State 1, Line 1
Server message 3128, Severity 10, State 1, Line 1
Server message 3406, Severity 10, State 1, Line 1
Server message 3407, Severity 10, State 1, Line 1
Server message 3137, Severity 10, State 1, Line 1
...全文
请发表友善的回复…
发表回复
cdxzh 2003-01-27
- 打赏
- 举报
error ID和error log 在哪里看啊？
diliver 2003-01-09
- 打赏
- 举报
xixi wanghai(汪海)
我在试试看吧
我在试试看吧
wanghai 2003-01-09
- 打赏
- 举报
Error 3216
Severity 10
Message text Backup Server session id is: %ld. Use this value when executing the
'sp_volchanged' system stored procedure after fulfilling any volume
change request from the Backup Server.
Explanation Dumps and loads are performed by an Open Server program known as Backup
Server. During the backup and restore process, it may be necessary to change
tape volumes. If Backup Server detects the need to change the currently
mounted volume, it requests a volume change by sending messages to either
the client or its operator console. After mounting another volume, the operator
notifies Backup Server by executing the sp_volchanged system procedure on
Adaptive Server.
3216 is an informational message that Backup Server issues when starting a
dump or load operation. The message notifies the operator of the current
session ID; the operator needs this information if it becomes necessary to
execute sp_volchanged during the dump/load operation.
Action This is an informational message. No action is necessary.
什么都不用做，看到了吗，仅仅是通知操作系统和当前SESSION，如果你的数据库能用就不用理会他，如果不能，应该出自别的原因
Severity 10
Message text Backup Server session id is: %ld. Use this value when executing the
'sp_volchanged' system stored procedure after fulfilling any volume
change request from the Backup Server.
Explanation Dumps and loads are performed by an Open Server program known as Backup
Server. During the backup and restore process, it may be necessary to change
tape volumes. If Backup Server detects the need to change the currently
mounted volume, it requests a volume change by sending messages to either
the client or its operator console. After mounting another volume, the operator
notifies Backup Server by executing the sp_volchanged system procedure on
Adaptive Server.
3216 is an informational message that Backup Server issues when starting a
dump or load operation. The message notifies the operator of the current
session ID; the operator needs this information if it becomes necessary to
execute sp_volchanged during the dump/load operation.
Action This is an informational message. No action is necessary.
什么都不用做，看到了吗，仅仅是通知操作系统和当前SESSION，如果你的数据库能用就不用理会他，如果不能，应该出自别的原因
diliver 2003-01-09
- 打赏
- 举报
日志提示成功，可wisql32里提示上面的错误
3216的意思是：backup server session id is :%ld.use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the backup server
帮分析一下
3216的意思是：backup server session id is :%ld.use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the backup server
帮分析一下
diliver 2003-01-09
- 打赏
- 举报
Nov 23 08:57:13 2002: Backup Server: 4.41.1.1: Creating new disk file c:\dy_bak.
Nov 23 08:57:14 2002: Backup Server: 6.28.1.1: Dumpfile name 'dy0232707DE8 ' section number 0001 mounted on device 'disk file'
Nov 23 08:57:19 2002: Backup Server: 4.58.1.1: Database dy: 2674 allocated kilobytes DUMP, equal to
Nov 23 08:57:23 2002: Backup Server: 4.58.1.1: Database dy: 5428 allocated kilobytes DUMP, equal to
Nov 23 08:57:29 2002: Backup Server: 4.58.1.1: Database dy: 10488 allocated kilobytes DUMP, equal to
Nov 23 08:57:39 2002: Backup Server: 4.58.1.1: Database dy: 20784 allocated kilobytes DUMP, equal to
Nov 23 08:57:53 2002: Backup Server: 4.58.1.1: Database dy: 36822 allocated kilobytes DUMP, equal to
Nov 23 08:58:07 2002: Backup Server: 4.58.1.1: Database dy: 51248 allocated kilobytes DUMP, equal to
Nov 23 08:58:14 2002: Backup Server: 4.58.1.1: Database dy: 57120 allocated kilobytes DUMP, equal to
Nov 23 08:58:30 2002: Backup Server: 4.58.1.1: Database dy: 69744 allocated kilobytes DUMP, equal to
Nov 23 08:58:38 2002: Backup Server: 4.58.1.1: Database dy: 75608 allocated kilobytes DUMP, equal to
Nov 23 08:58:47 2002: Backup Server: 4.58.1.1: Database dy: 77726 allocated kilobytes DUMP, equal to
Nov 23 08:58:57 2002: Backup Server: 4.58.1.1: Database dy: 85462 allocated kilobytes DUMP, equal to
Nov 23 08:59:15 2002: Backup Server: 4.58.1.1: Database dy: 102332 allocated kilobytes DUMP, equal to
Nov 23 08:59:29 2002: Backup Server: 4.58.1.1: Database dy: 115232 allocated kilobytes DUMP, equal to
Nov 23 08:59:49 2002: Backup Server: 4.58.1.1: Database dy: 134728 allocated kilobytes DUMP, equal to
Nov 23 09:00:13 2002: Backup Server: 4.58.1.1: Database dy: 158396 allocated kilobytes DUMP, equal to
Nov 23 09:00:42 2002: Backup Server: 4.58.1.1: Database dy: 193088 allocated kilobytes DUMP, equal to
Nov 23 09:00:44 2002: Backup Server: 4.58.1.1: Database dy: 198316 allocated kilobytes DUMP, equal to
Nov 23 09:00:47 2002: Backup Server: 4.58.1.1: Database dy: 198658 allocated kilobytes DUMP, equal to
Nov 23 09:01:03 2002: Backup Server: 4.58.1.1: Database dy: 200710 allocated kilobytes DUMP, equal to
Nov 23 09:01:15 2002: Backup Server: 4.58.1.1: Database dy: 202762 allocated kilobytes DUMP, equal to
Nov 23 09:01:28 2002: Backup Server: 4.58.1.1: Database dy: 204858 allocated kilobytes DUMP, equal to
Nov 23 09:01:41 2002: Backup Server: 3.43.1.1: Dump phase number 1 completed.
Nov 23 09:01:41 2002: Backup Server: 3.43.1.1: Dump phase number 2 completed.
Nov 23 09:01:41 2002: Backup Server: 3.43.1.1: Dump phase number 3 completed.
Nov 23 09:01:41 2002: Backup Server: 4.58.1.1: Database dy: 206630 allocated kilobytes DUMP, equal to completed.
Nov 23 09:01:41 2002: Backup Server: 3.42.1.1: DUMP is complete (database dy).
Nov 23 08:57:14 2002: Backup Server: 6.28.1.1: Dumpfile name 'dy0232707DE8 ' section number 0001 mounted on device 'disk file'
Nov 23 08:57:19 2002: Backup Server: 4.58.1.1: Database dy: 2674 allocated kilobytes DUMP, equal to
Nov 23 08:57:23 2002: Backup Server: 4.58.1.1: Database dy: 5428 allocated kilobytes DUMP, equal to
Nov 23 08:57:29 2002: Backup Server: 4.58.1.1: Database dy: 10488 allocated kilobytes DUMP, equal to
Nov 23 08:57:39 2002: Backup Server: 4.58.1.1: Database dy: 20784 allocated kilobytes DUMP, equal to
Nov 23 08:57:53 2002: Backup Server: 4.58.1.1: Database dy: 36822 allocated kilobytes DUMP, equal to
Nov 23 08:58:07 2002: Backup Server: 4.58.1.1: Database dy: 51248 allocated kilobytes DUMP, equal to
Nov 23 08:58:14 2002: Backup Server: 4.58.1.1: Database dy: 57120 allocated kilobytes DUMP, equal to
Nov 23 08:58:30 2002: Backup Server: 4.58.1.1: Database dy: 69744 allocated kilobytes DUMP, equal to
Nov 23 08:58:38 2002: Backup Server: 4.58.1.1: Database dy: 75608 allocated kilobytes DUMP, equal to
Nov 23 08:58:47 2002: Backup Server: 4.58.1.1: Database dy: 77726 allocated kilobytes DUMP, equal to
Nov 23 08:58:57 2002: Backup Server: 4.58.1.1: Database dy: 85462 allocated kilobytes DUMP, equal to
Nov 23 08:59:15 2002: Backup Server: 4.58.1.1: Database dy: 102332 allocated kilobytes DUMP, equal to
Nov 23 08:59:29 2002: Backup Server: 4.58.1.1: Database dy: 115232 allocated kilobytes DUMP, equal to
Nov 23 08:59:49 2002: Backup Server: 4.58.1.1: Database dy: 134728 allocated kilobytes DUMP, equal to
Nov 23 09:00:13 2002: Backup Server: 4.58.1.1: Database dy: 158396 allocated kilobytes DUMP, equal to
Nov 23 09:00:42 2002: Backup Server: 4.58.1.1: Database dy: 193088 allocated kilobytes DUMP, equal to
Nov 23 09:00:44 2002: Backup Server: 4.58.1.1: Database dy: 198316 allocated kilobytes DUMP, equal to
Nov 23 09:00:47 2002: Backup Server: 4.58.1.1: Database dy: 198658 allocated kilobytes DUMP, equal to
Nov 23 09:01:03 2002: Backup Server: 4.58.1.1: Database dy: 200710 allocated kilobytes DUMP, equal to
Nov 23 09:01:15 2002: Backup Server: 4.58.1.1: Database dy: 202762 allocated kilobytes DUMP, equal to
Nov 23 09:01:28 2002: Backup Server: 4.58.1.1: Database dy: 204858 allocated kilobytes DUMP, equal to
Nov 23 09:01:41 2002: Backup Server: 3.43.1.1: Dump phase number 1 completed.
Nov 23 09:01:41 2002: Backup Server: 3.43.1.1: Dump phase number 2 completed.
Nov 23 09:01:41 2002: Backup Server: 3.43.1.1: Dump phase number 3 completed.
Nov 23 09:01:41 2002: Backup Server: 4.58.1.1: Database dy: 206630 allocated kilobytes DUMP, equal to completed.
Nov 23 09:01:41 2002: Backup Server: 3.42.1.1: DUMP is complete (database dy).
wanghai 2003-01-09
- 打赏
- 举报
你的这个日志只是启动时的日志吧，恢复时的日志呢
diliver 2003-01-09
- 打赏
- 举报
错误日志：
.
00:02/11/22 11:04:35.06 kernel Network and device connection limit is 2040.
00:02/11/22 11:04:35.25 server Number of proc buffers allocated: 738.
00:02/11/22 11:04:35.38 server Number of blocks left for proc headers: 787.
00:02/11/22 11:04:35.38 server Memory allocated for the default data cache cache: 5576 Kb
00:02/11/22 11:04:35.41 server Size of the 2K memory pool: 5576 Kb
00:02/11/22 11:04:35.41 kernel Initializing virtual device 0, 'c:\sybase\DATA\MASTER.DAT'
00:02/11/22 11:04:35.44 kernel Virtual device 0 started using asynchronous i/o.
00:02/11/22 11:04:35.92 server Opening Master Database ...
00:02/11/22 11:04:38.61 server Loading SQL Server's default sort order and character set
00:02/11/22 11:04:39.64 server Recovering database 'master'
00:02/11/22 11:04:40.24 server Recovery dbid 1 ckpt (1977,22)
00:02/11/22 11:04:40.24 server Recovery no active transactions before ckpt.
00:02/11/22 11:04:42.28 server 4 transactions rolled forward.
00:02/11/22 11:04:45.40 server Database 'master' is now online.
00:02/11/22 11:04:45.43 server The transaction log in the database 'master' will use I/O size of 2 Kb.
00:02/11/22 11:04:45.69 server server is unnamed
00:02/11/22 11:04:45.85 server Activating disk 'dy_data'.
00:02/11/22 11:04:45.85 kernel Initializing virtual device 2, 'c:\sybase\data\dydata'
00:02/11/22 11:04:50.75 kernel Virtual device 2 started using asynchronous i/o.
00:02/11/22 11:04:50.75 server Activating disk 'dy_log'.
00:02/11/22 11:04:50.75 kernel Initializing virtual device 3, 'c:\sybase\data\log'
00:02/11/22 11:04:51.36 kernel Virtual device 3 started using asynchronous i/o.
00:02/11/22 11:04:51.36 server Activating disk 'sysprocsdev'.
00:02/11/22 11:04:51.36 kernel Initializing virtual device 1, 'c:\sybase\DATA\SYBPROCS.DAT'
00:02/11/22 11:04:51.41 kernel Virtual device 1 started using asynchronous i/o.
00:02/11/22 11:04:52.24 server Recovering database 'model'.
00:02/11/22 11:04:52.25 server Recovery dbid 3 ckpt (441,6)
00:02/11/22 11:04:52.25 server Recovery no active transactions before ckpt.
00:02/11/22 11:04:52.61 server The transaction log in the database 'model' will use I/O size of 2 Kb.
00:02/11/22 11:04:52.64 server Database 'model' is now online.
00:02/11/22 11:04:52.67 server Clearing temp db
00:02/11/22 11:04:57.61 server Recovering database 'sybsystemprocs'.
00:02/11/22 11:04:57.62 server Recovery dbid 4 ckpt (6907,22)
00:02/11/22 11:04:57.62 server Recovery no active transactions before ckpt.
00:02/11/22 11:04:58.78 server The transaction log in the database 'sybsystemprocs' will use I/O size of 2 Kb.
00:02/11/22 11:04:58.80 server Database 'sybsystemprocs' is now online.
00:02/11/22 11:04:58.96 server Recovering database 'dy'.
00:02/11/22 11:04:58.99 server Recovery dbid 5 ckpt (921603,2) oldest tran=(921603,1)
00:02/11/22 11:04:59.12 server 1 transactions rolled forward.
00:02/11/22 11:05:11.35 server The transaction log in the database 'dy' will use I/O size of 2 Kb.
00:02/11/22 11:05:11.40 server Database 'dy' is now online.
00:02/11/22 11:05:11.40 server Recovery complete.
00:02/11/22 11:05:11.40 server SQL Server's default sort order is:
00:02/11/22 11:05:11.40 server 'bin_cp850' (ID = 50)
00:02/11/22 11:05:11.40 server on top of default character set:
00:02/11/22 11:05:11.40 server 'cp850' (ID = 2).
00:02/11/22 11:07:55.25 kernel Initializing virtual device 4, 'c:\sybase\data\dy_data1'
00:02/11/22 11:07:55.25 kernel Virtual device 4 started using asynchronous i/o.
00:02/11/22 11:08:40.94 kernel Initializing virtual device 5, 'c:\sybase\data\dy_log1'
00:02/11/22 11:08:40.94 kernel Virtual device 5 started using asynchronous i/o.
00:02/11/22 11:18:03.47 server Recovery dbid 5 ckpt (822842,2)
00:02/11/22 11:18:03.47 server Recovery no active transactions before ckpt.
00:02/11/22 11:41:53.38 server Recovery dbid 5 ckpt (822842,2)
00:02/11/22 11:41:53.38 server Recovery no active transactions before ckpt.
00:02/11/22 11:57:22.79 server Recovery dbid 5 ckpt (822842,2)
00:02/11/22 11:57:22.79 server Recovery no active transactions before ckpt.
00:02/11/22 12:33:50.16 server Recovery dbid 5 ckpt (822842,2)
00:02/11/22 12:33:50.47 server Recovery no active transactions before ckpt.
.
00:02/11/22 11:04:35.06 kernel Network and device connection limit is 2040.
00:02/11/22 11:04:35.25 server Number of proc buffers allocated: 738.
00:02/11/22 11:04:35.38 server Number of blocks left for proc headers: 787.
00:02/11/22 11:04:35.38 server Memory allocated for the default data cache cache: 5576 Kb
00:02/11/22 11:04:35.41 server Size of the 2K memory pool: 5576 Kb
00:02/11/22 11:04:35.41 kernel Initializing virtual device 0, 'c:\sybase\DATA\MASTER.DAT'
00:02/11/22 11:04:35.44 kernel Virtual device 0 started using asynchronous i/o.
00:02/11/22 11:04:35.92 server Opening Master Database ...
00:02/11/22 11:04:38.61 server Loading SQL Server's default sort order and character set
00:02/11/22 11:04:39.64 server Recovering database 'master'
00:02/11/22 11:04:40.24 server Recovery dbid 1 ckpt (1977,22)
00:02/11/22 11:04:40.24 server Recovery no active transactions before ckpt.
00:02/11/22 11:04:42.28 server 4 transactions rolled forward.
00:02/11/22 11:04:45.40 server Database 'master' is now online.
00:02/11/22 11:04:45.43 server The transaction log in the database 'master' will use I/O size of 2 Kb.
00:02/11/22 11:04:45.69 server server is unnamed
00:02/11/22 11:04:45.85 server Activating disk 'dy_data'.
00:02/11/22 11:04:45.85 kernel Initializing virtual device 2, 'c:\sybase\data\dydata'
00:02/11/22 11:04:50.75 kernel Virtual device 2 started using asynchronous i/o.
00:02/11/22 11:04:50.75 server Activating disk 'dy_log'.
00:02/11/22 11:04:50.75 kernel Initializing virtual device 3, 'c:\sybase\data\log'
00:02/11/22 11:04:51.36 kernel Virtual device 3 started using asynchronous i/o.
00:02/11/22 11:04:51.36 server Activating disk 'sysprocsdev'.
00:02/11/22 11:04:51.36 kernel Initializing virtual device 1, 'c:\sybase\DATA\SYBPROCS.DAT'
00:02/11/22 11:04:51.41 kernel Virtual device 1 started using asynchronous i/o.
00:02/11/22 11:04:52.24 server Recovering database 'model'.
00:02/11/22 11:04:52.25 server Recovery dbid 3 ckpt (441,6)
00:02/11/22 11:04:52.25 server Recovery no active transactions before ckpt.
00:02/11/22 11:04:52.61 server The transaction log in the database 'model' will use I/O size of 2 Kb.
00:02/11/22 11:04:52.64 server Database 'model' is now online.
00:02/11/22 11:04:52.67 server Clearing temp db
00:02/11/22 11:04:57.61 server Recovering database 'sybsystemprocs'.
00:02/11/22 11:04:57.62 server Recovery dbid 4 ckpt (6907,22)
00:02/11/22 11:04:57.62 server Recovery no active transactions before ckpt.
00:02/11/22 11:04:58.78 server The transaction log in the database 'sybsystemprocs' will use I/O size of 2 Kb.
00:02/11/22 11:04:58.80 server Database 'sybsystemprocs' is now online.
00:02/11/22 11:04:58.96 server Recovering database 'dy'.
00:02/11/22 11:04:58.99 server Recovery dbid 5 ckpt (921603,2) oldest tran=(921603,1)
00:02/11/22 11:04:59.12 server 1 transactions rolled forward.
00:02/11/22 11:05:11.35 server The transaction log in the database 'dy' will use I/O size of 2 Kb.
00:02/11/22 11:05:11.40 server Database 'dy' is now online.
00:02/11/22 11:05:11.40 server Recovery complete.
00:02/11/22 11:05:11.40 server SQL Server's default sort order is:
00:02/11/22 11:05:11.40 server 'bin_cp850' (ID = 50)
00:02/11/22 11:05:11.40 server on top of default character set:
00:02/11/22 11:05:11.40 server 'cp850' (ID = 2).
00:02/11/22 11:07:55.25 kernel Initializing virtual device 4, 'c:\sybase\data\dy_data1'
00:02/11/22 11:07:55.25 kernel Virtual device 4 started using asynchronous i/o.
00:02/11/22 11:08:40.94 kernel Initializing virtual device 5, 'c:\sybase\data\dy_log1'
00:02/11/22 11:08:40.94 kernel Virtual device 5 started using asynchronous i/o.
00:02/11/22 11:18:03.47 server Recovery dbid 5 ckpt (822842,2)
00:02/11/22 11:18:03.47 server Recovery no active transactions before ckpt.
00:02/11/22 11:41:53.38 server Recovery dbid 5 ckpt (822842,2)
00:02/11/22 11:41:53.38 server Recovery no active transactions before ckpt.
00:02/11/22 11:57:22.79 server Recovery dbid 5 ckpt (822842,2)
00:02/11/22 11:57:22.79 server Recovery no active transactions before ckpt.
00:02/11/22 12:33:50.16 server Recovery dbid 5 ckpt (822842,2)
00:02/11/22 12:33:50.47 server Recovery no active transactions before ckpt.
ice2water 2003-01-08
- 打赏
- 举报
up
wanghai 2003-01-08
- 打赏
- 举报
贴这些出来谁看的懂：（，贴个日志看看
