Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
rchiu5hk
Starting Member
7 Posts |
 Posted - 2009-07-13 : 20:56:30
|
| Dear all,My company has a short of electric in the building.After recover, I find that some programs which connect to sql server db has thrown exception. the message is as below. Do you know how to do it??* APPLICATION LOGThe VB Application identified by the event source logged this Application GMS2Sys: Thread ID: 2684 ,Logged: iES Error : in dcGMS2Sys.GetAlertMstrByKey ; -2147467259 ; Microsoft OLE DB Provider for SQL Server ; Invalid authorization specification The VB Application identified by the event source logged this Application GMS2Sys: Thread ID: 2684 ,Logged: iES Error : in .GetDBPass ; 3021 ; ADODB.Field ; Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record. The VB Application identified by the event source logged this Application GMS2Sys: Thread ID: 2676 ,Logged: iES Error : in dcGMS2Sys.GetAlertMstrByKey ; -2147467259 ; Microsoft OLE DB Provider for SQL Server ; Invalid authorization specification The VB Application identified by the event source logged this Application GMS2Sys: Thread ID: 2676 ,Logged: iES Error : in .GetDBPass ; 3021 ; ADODB.Field ; Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record. The VB Application identified by the event source logged this Application GMS2Sys: Thread ID: 2672 ,Logged: iES Error : in dcGMS2Sys.GetAlertMstrByKey ; -2147467259 ; Microsoft OLE DB Provider for SQL Server ; Invalid authorization specification Error: 8646, Severity: 21, State: 1 The index entry for row ID was not found in index ID 2, of table 1602104748, in database 'AGMS2DB'. Error: 823, Severity: 24, State: 2I/O error (torn page) detected during read at offset 0x0000000f584000 in file 'D:\GMS2DATA\AGMS2DB_Data.MDF'. |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2009-07-13 : 21:06:46
|
| you have a backup ready right? |
 |
|
|
rchiu5hk
Starting Member
7 Posts |
Posted - 2009-07-13 : 21:55:03
|
quote:
Originally posted by russell
you have a backup ready right?
Do I need to load backup and no solution??? |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2009-07-14 : 00:03:42
|
| will the database start up? if so, run a dbcc checkdb. if it reports any errors (other than perhaps on index pages) be prepared to restore a backup.if you can be certain that it is just an index, may try rebuilding it.a torn page is an imcomplete write operation that was not recoverable when the system restarted. |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-07-14 : 03:45:48
|
Please run the following on that database and post the full results here.DBCC CHECKDB (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGS Sometimes restoring from backup is the recommended way to recover from corruption, sometimes not. The error you posted in in a nonclustered index so, if it's the only error, we should be able to repair without needing to restore backup. To be sure I need to see the full output of checkDB.Take a look at this article for more info on corruption. [url]http://www.sqlservercentral.com/articles/65804/[/url]--Gail ShawSQL Server MVP |
|
|
|
|
|
|
|
|
data corrupt index??