`
forlab
  • 浏览: 133957 次
  • 性别: Icon_minigender_1
  • 来自: 北京
社区版块
存档分类
最新评论

圆通快递SqlServer数据库报错

 
阅读更多 
日期,源,严重性,消息
08/02/2013 21:25:12,spid58,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24797，但实际为 0:0). It occurred during a 读取 of page (1:24797) in database ID 5 at offset 0x0000000c1ba000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:12,spid58,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:11,spid52,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24975，但实际为 0:0). It occurred during a 读取 of page (1:24975) in database ID 5 at offset 0x0000000c31e000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:11,spid52,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:10,spid58,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24797，但实际为 0:0). It occurred during a 读取 of page (1:24797) in database ID 5 at offset 0x0000000c1ba000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:10,spid58,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:10,spid52,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24975，但实际为 0:0). It occurred during a 读取 of page (1:24975) in database ID 5 at offset 0x0000000c31e000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:10,spid52,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:08,spid65,未知,AppDomain 2 (mssqlsystemresource.sys[runtime].1) created.
08/02/2013 21:25:08,spid65,未知,Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\.
08/02/2013 21:25:05,spid66,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24990，但实际为 0:0). It occurred during a 读取 of page (1:24990) in database ID 5 at offset 0x0000000c33c000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:05,spid66,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:03,spid63,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24990，但实际为 0:0). It occurred during a 读取 of page (1:24990) in database ID 5 at offset 0x0000000c33c000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:03,spid63,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:02,spid62,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24990，但实际为 0:0). It occurred during a 读取 of page (1:24990) in database ID 5 at offset 0x0000000c33c000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:02,spid62,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:02,spid61,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24990，但实际为 0:0). It occurred during a 读取 of page (1:24990) in database ID 5 at offset 0x0000000c33c000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:02,spid61,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:02,spid60,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24990，但实际为 0:0). It occurred during a 读取 of page (1:24990) in database ID 5 at offset 0x0000000c33c000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:02,spid60,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:02,spid58,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24990，但实际为 0:0). It occurred during a 读取 of page (1:24990) in database ID 5 at offset 0x0000000c33c000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:02,spid58,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:02,spid52,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24946，但实际为 0:0). It occurred during a 读取 of page (1:24946) in database ID 5 at offset 0x0000000c2e4000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:02,spid52,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:02,spid59,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24990，但实际为 0:0). It occurred during a 读取 of page (1:24990) in database ID 5 at offset 0x0000000c33c000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:02,spid59,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:02,spid64,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24772，但实际为 0:0). It occurred during a 读取 of page (1:24772) in database ID 5 at offset 0x0000000c188000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:02,spid64,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:00,spid63,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24990，但实际为 0:0). It occurred during a 读取 of page (1:24990) in database ID 5 at offset 0x0000000c33c000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:00,spid63,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:00,spid62,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24990，但实际为 0:0). It occurred during a 读取 of page (1:24990) in database ID 5 at offset 0x0000000c33c000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:00,spid62,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:00,spid60,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24990，但实际为 0:0). It occurred during a 读取 of page (1:24990) in database ID 5 at offset 0x0000000c33c000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:00,spid60,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:00,spid58,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24946，但实际为 0:0). It occurred during a 读取 of page (1:24946) in database ID 5 at offset 0x0000000c2e4000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:00,spid58,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:00,spid52,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24990，但实际为 0:0). It occurred during a 读取 of page (1:24990) in database ID 5 at offset 0x0000000c33c000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:00,spid52,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:25:00,spid61,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24990，但实际为 0:0). It occurred during a 读取 of page (1:24990) in database ID 5 at offset 0x0000000c33c000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:25:00,spid61,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:24:56,spid58,未知,SQL Server detected a logical consistency-based I/O error: pageid 不正确(应为 1:24772，但实际为 0:0). It occurred during a 读取 of page (1:24772) in database ID 5 at offset 0x0000000c188000 in file 'd:\YTOData\ytodb.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online.
08/02/2013 21:24:56,spid58,未知,错误: 824，严重性: 24，状态: 2。
08/02/2013 21:24:41,spid53,未知,Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_enumerrorlogs'. This is an informational message only; no user action is required.
08/02/2013 21:24:41,spid53,未知,Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
08/02/2013 21:24:36,spid51,未知,Recovery completed for database ytodb (database ID 5) in 67 second(s) (analysis 265 ms<c/> redo 67156 ms<c/> undo 78 ms.) This is an informational message only. No user action is required.
08/02/2013 21:24:36,spid51,未知,Recovery is writing a checkpoint in database 'ytodb' (5). This is an informational message only. No user action is required.
08/02/2013 21:24:36,spid51,未知,0 transactions rolled back in database 'ytodb' (5). This is an informational message only. No user action is required.
08/02/2013 21:24:36,spid51,未知,1857 transactions rolled forward in database 'ytodb' (5). This is an informational message only. No user action is required.
08/02/2013 21:24:35,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:35,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:34,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:24:34,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:32,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:24:32,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:30,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:24:30,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:29,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:29,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:28,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:24:28,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:27,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:27,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:26,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:24:26,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:24,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:24,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:24,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:24:24,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:22,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:22,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:21,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:24:21,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:20,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:20,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:19,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:24:19,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:18,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:18,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:16,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:16,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:14,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:14,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:12,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:12,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:09,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:09,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:07,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:24:07,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:07,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:07,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:05,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:24:05,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:05,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:05,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:03,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:03,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:03,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:24:03,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:01,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:24:01,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:24:01,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:24:01,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:59,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:59,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:58,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:58,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:57,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:57,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:56,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:56,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:54,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:54,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:54,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:54,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:54,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:54,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:52,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:52,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:52,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:52,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:50,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:50,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:50,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:50,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:48,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:48,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:48,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:48,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:45,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:45,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:45,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:45,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:43,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:43,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:43,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:43,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:41,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:41,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:41,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:41,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:39,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:39,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:39,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:39,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:37,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:37,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:36,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:36,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:35,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:35,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:34,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:34,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:33,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:33,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:32,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:32,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:30,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:30,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:30,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:30,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:28,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.105]
08/02/2013 21:23:28,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:28,spid51,未知,Recovery of database 'ytodb' (5) is 2% complete (approximately 12 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
08/02/2013 21:23:28,spid51,未知,Recovery of database 'ytodb' (5) is 0% complete (approximately 12 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
08/02/2013 21:23:27,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:27,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:25,spid51,未知,Starting up database 'ytodb'.
08/02/2013 21:23:25,spid7s,未知,Recovery is complete. This is an informational message only. No user action is required.
08/02/2013 21:23:25,spid13s,未知,Service Broker manager has started.
08/02/2013 21:23:25,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.101]
08/02/2013 21:23:25,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:25,spid13s,未知,The Database Mirroring protocol transport is disabled or not configured.
08/02/2013 21:23:25,spid13s,未知,The Service Broker protocol transport is disabled or not configured.
08/02/2013 21:23:25,spid10s,未知,Starting up database 'tempdb'.
08/02/2013 21:23:25,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:25,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:25,登录,未知,Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 192.168.1.100]
08/02/2013 21:23:25,登录,未知,错误: 18456，严重性: 14，状态: 38。
08/02/2013 21:23:25,服务器,未知,SQL Server is now ready for client connections. This is an informational message; no user action is required.
08/02/2013 21:23:25,服务器,未知,The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b<c/> state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
08/02/2013 21:23:25,服务器,未知,Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection<c/> restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
08/02/2013 21:23:25,服务器,未知,Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
08/02/2013 21:23:25,服务器,未知,Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
08/02/2013 21:23:25,服务器,未知,Server is listening on [ 'any' <ipv4> 1433].
08/02/2013 21:23:25,服务器,未知,A self-generated certificate was successfully loaded for encryption.
08/02/2013 21:23:25,spid7s,未知,Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
08/02/2013 21:23:25,spid7s,未知,0 transactions rolled back in database 'msdb' (4). This is an informational message only. No user action is required.
08/02/2013 21:23:25,spid7s,未知,373 transactions rolled forward in database 'msdb' (4). This is an informational message only. No user action is required.
08/02/2013 21:23:25,spid10s,未知,Clearing tempdb database.
08/02/2013 21:23:24,spid7s,未知,Starting up database 'msdb'.
08/02/2013 21:23:24,spid7s,未知,信息: 找不到支持全文的语言。
08/02/2013 21:23:24,spid7s,未知,Server name is 'YTO-9E0196F2E5C'. This is an informational message only. No user action is required.
08/02/2013 21:23:24,spid10s,未知,Starting up database 'model'.
08/02/2013 21:23:24,spid7s,未知,The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
08/02/2013 21:23:24,spid7s,未知,Starting up database 'mssqlsystemresource'.
08/02/2013 21:23:24,spid7s,未知,SQL Trace ID 1 was started by login "sa".
08/02/2013 21:23:24,spid7s,未知,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'MSSQLSERVER'.
08/02/2013 21:23:24,spid7s,未知,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
08/02/2013 21:23:24,spid7s,未知,0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
08/02/2013 21:23:24,spid7s,未知,4 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
08/02/2013 21:23:24,spid7s,未知,Starting up database 'master'.
08/02/2013 21:23:24,服务器,未知,Node configuration: node 0: CPU mask: 0x0000000f:0 Active CPU mask: 0x0000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
08/02/2013 21:23:24,服务器,未知,Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
08/02/2013 21:23:24,服务器,未知,Detected 4 CPUs. This is an informational message; no user action is required.
08/02/2013 21:23:24,服务器,未知,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
08/02/2013 21:23:24,Server,未知,Registry startup parameters: <nl/>	 -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf<nl/>	 -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG<nl/>	 -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
08/02/2013 21:23:24,Server,未知,This instance of SQL Server last reported using a process ID of 6788 at 2013-8-2 19:15:51 (local) 2013-8-2 11:15:51 (UTC). This is an informational message only; no user action is required.
08/02/2013 21:23:24,Server,未知,Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
08/02/2013 21:23:24,Server,未知,Authentication mode is MIXED.
08/02/2013 21:23:24,Server,未知,Server process ID is 7876.
08/02/2013 21:23:24,Server,未知,All rights reserved.
08/02/2013 21:23:24,Server,未知,(c) Microsoft Corporation.
08/02/2013 21:23:24,Server,未知,Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86) <nl/>	Apr  2 2010 15:53:02 <nl/>	Copyright (c) Microsoft Corporation<nl/>	Express Edition with Advanced Services on Windows NT 5.2 <X86> (Build 3790: Service Pack 2)

 

 

EXEC sp_renamedb 'forlab', 'guoka'

use  guoka

go

ALTER DATABASE guoka SET SINGLE_USER

DBCC CHECKDB (guoka, repair_allow_data_loss) with NO_INFOMSGS

 

alter database guoka set multi_user   with rollback immediate

(转)DBCC CHECKDB用法详解

手工修复数据库

1、快速修复
DBCC CHECKDB ('数据库名', REPAIR_FAST)    
2、重建索引并修复
DBCC CHECKDB ('数据库名', REPAIR_REBUILD)
3、如果必要允许丢失数据修复
DBCC CHECKDB ('数据库名'', REPAIR_ALLOW_DATA_LOSS)

如果出现错误：未处理修复语句。数据库需处于单用户模式下。

可以先启用单用户模式，方法如下执行存储过程：

Use master
go
sp_dboption 数据库名, single, true

--更改成单用户
     alter   database   test   set   single_user   with   rollback   immediate 

--还原数据库为多用户模式
   alter database test set multi_user   with rollback immediate

############################################################
############################################################


手工修复数据库试例

操作步骤:

----------------------------------------------------------------------------------------------
   进入SQL查询分析器,执行语句:

   --检查数据库完整性
     dbcc checkdb('ams1')

     执行结果:
---------------------------------------------------------------
     CHECKDB 发现了 0 个分配错误和 11 个一致性错误（在数据库 'test' 中）。
repair_allow_data_loss 是最低的修复级别（对于由 DBCC CHECKDB (test ) 发现的错误而言）。
DBCC 执行完毕。如果 DBCC 输出了错误信息，请与系统管理员联系。


   说明数据库确实有问题,11个错误,找到错误地方:

-------------------------------------------------------------------------------
   对象 'Tb_Archives_File_1' 有 3777 行，这些行位于 172 页中。
CHECKDB 发现了 0 个分配错误和 2 个一致性错误（在表 'Tb_Archives_File_1' 中，该表的对象 ID 为 907150277）。

     表明 'Tb_Archives_File_1' 表确实有2个错误,难怪一查询就要死机,于是运行语句进行表修复:

--------------------------------------------------------------------------------------
     --以repair_allow_data_loss级别修复表
     dbcc   checktable('Tb_Archives_File_1',repair_allow_data_loss) 
     go 

     执行结果:
     服务器: 消息 7919，级别 16，状态 3，行 2
     未处理修复语句。数据库需要处于单用户模式下。
     DBCC 执行完毕。如果 DBCC 输出了错误信息，请与系统管理员联系。

   ---------------------------------------------------------------------------------------------------

     需要将数据库改为"单用户模式",于是再执行:
     --更改成单用户
     alter   database   test  set   single_user   with   rollback   immediate 
go 
     --已repair_allow_data_loss级别修复表
     dbcc   checktable('Tb_Archives_File_1',repair_allow_data_loss) 
go 


     --若还有问题，修复索引表
   DBCC   DBREINDEX('Tb_Archives_File_1') 

   --再修复表
   DBCC   CHECKTABLE('Tb_Archives_File_1') 

   直到返回的结果没有错误!

   --查询是否正常
   select * from Tb_Archives_File_1

   再查询那张错误表,不报错,也不死机了,数据也完好无损.....哈哈....

   --还原数据库为多用户模式
   alter database test set multi_user   with rollback immediate
   
   
  相关链接 
   http://www.cnblogs.com/lyhabc/archive/2012/10/22/2733509.html
   http://msdn.microsoft.com/zh-cn/library/aa337419.aspx

 

分享到：
| Log4j使用总结
评论
发表评论

您还没有登录,请您登录后再发表评论

相关推荐

    圆通数据库本地库软件

    圆通速递本地库文件，本地库执行错误后重新安装此文件

    20121011圆通快递模板

    圆通快递模板是专门为四五打印助手设计的一款打印模板，主要用于处理与圆通速递相关的物流信息打印工作。在电子商务、零售业以及个人邮寄物品的日常运营中，正确、规范地打印快递单是确保包裹顺利投递的关键环节。...

    圆通快递小助手

    【圆通快递小助手】是一款专为用户设计的快递管理工具，主要针对圆通速递的服务，方便用户查询、跟踪和管理自己的快递包裹。这款软件的出现，旨在提高用户对快递服务的使用体验，简化查询步骤，使得快递信息查询变得...

    数据库.rar

    1. **第8章 T-SQL语言.ppt** - T-SQL（Transact-SQL）是SQL Server中扩展的SQL版本，用于执行数据库查询、更新、插入和删除操作。此章可能涵盖了T-SQL的基本语法，包括SELECT语句用于查询数据，INSERT用于添加新记录...

    圆通快递单打印软件-圆通快递单批量打印软件

    ★★程序功能如下★★ 1。支持自定义快递单模板（别的单据也支持） 2。自动填写发件人的信息。 3。自动填写收件人的信息。...支持快递单实时查询，让你的快递实时信息...圆通快递单打印软件-圆通快递单批量打印软件

    兴达圆通快递单打印软件 v3.2.zip

    因企业或店铺经营模式的不同特点和利用快递单发货方式的差异，我们推出了一系列快递单打印软件，其中包括兴达申通快递单打印软件、兴达顺丰快递单打印软件、兴达圆通快递单打印软件、兴达宅急送快递单打印软件、兴达...

    圆通速递系统分析.pdf

    圆通速递系统是一个复杂而高效的物流网络，旨在提供快速、准确的快递服务。这个系统涵盖了从收件到派送的全过程，涉及多个关键环节和要素。以下是对其主要知识点的详细分析： 一、圆通速递公司简介 圆通速递成立于...

    圆通速递上线“行者APP”.pdf

    圆通速递上线“行者APP”.pdf

    浅谈圆通速递核心竞争力.doc

    圆通速递作为中国快递行业的重要参与者，面临着日益激烈的市场竞争和行业的变革挑战。核心竞争力是企业在竞争中保持优势的关键因素，对于圆通速递而言，构建和提升自身的核心竞争力至关重要。 2. 核心竞争力的概述 ...

    圆通快递打印

    圆通快递打印软件就是专为处理这方面需求而设计的工具。这款软件能够帮助用户快速、便捷地打印圆通快递单，提高工作效率。 标题“圆通快递打印”表明这是一款专注于圆通快递业务的打印应用。它可能包含了定制化的...

    圆通快递打印模板

    圆通快递EXCEL打印模板，可以省掉很多麻烦，大家可以试试

    20191123-西部证券-圆通速递-600233-首次覆盖：砥砺前行，蓄势待发.rar

    2. **圆通速递的业务模式**：介绍圆通速递的运营模式，如网络布局、服务类型（包括标准快递、特快专递、国际快递等）、技术研发（如自动化设备、信息化系统）。 3. **财务状况**：详细解读公司的财务数据，包括营业...

    SHOPEX快递单号查询插件圆通专版 v1.0.zip

    SHOPEX快递单号查询插件圆通专版提供国内外近2000家快递物流订单单号查询服务例如圆通快递快递订单查询服务, 另有全球各国邮局邮政、国内国际小包等接口查询， 现已很好的整合在SHOPEX里，只要简单几步即可实现...

    20200207-东北-圆通速递-600233-多维改善，低估值凸显配置价值.rar

    1. **圆通速递的业务概述**：可能会介绍圆通速递的基本情况，包括其在国内快递行业的地位、市场份额、主要业务线和服务范围。 2. **多维度改善**：可能详细阐述了公司在运营效率、服务质量、成本控制、技术创新等...

    圆通快递单号生成器

    《圆通快递单号生成器》是一款专门针对圆通速递公司设计的工具软件，它主要的功能是自动生成圆通快递的运单号码。在电子商务和物流行业日益发达的今天，这种工具对于处理大量订单或者进行模拟测试时，能够极大地提高...

    圆通速递：供应链金融助攻物流业复苏.zip

    标题中的“圆通速递：供应链金融助攻物流业复苏”揭示了主要讨论的主题，即圆通速递如何利用供应链金融这一策略来推动物流行业的恢复和发展。供应链金融是现代企业管理和运营的重要工具，它通过整合供应链上的资金流...

    SHOPEX快递单号查询插件圆通V8.6版

    本SHOPEX快递物流单号跟踪插件提供国内外近2000家快递物流订单单号查询服务例如申通快递、顺丰快递、圆通快递、EMS快递、汇通快递、宅急送快递、德邦物流、百世快递、汇通快递、中通快递、天天快递等知名快递订单...

    圆通快递单打印模板

    圆通快递单打印模板，导入好用快递单打印软件进行打印。 ★★程序功能如下★★ 1。支持自定义快递单模板（别的单据也支持） 2。自动填写发件人的信息。 3。自动填写收件人的信息。 4。自动抓取淘宝需要发货的订单...

    金刚系统安装手册.pdf

    【金刚系统安装手册】主要涉及的是上海圆通速递有限公司(YTO)核心营运管理系统的软件部署过程，其中重点是数据库SQL Server 2008的安装和配置。以下是详细的安装步骤和注意事项： 1. **数据库SQL Server 2008安装**...

Magicbox
Global site tag (gtag.js) - Google Analytics