|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-02-22 : 09:49:00
|
| Alex Caporicci writes "Hello,I believe our software caused a major database corruption on a client's site. Our initial theories is that a combination of an incorrect stored procedure and configuration on the SQL Server caused a stack dump and the database to be marked suspect and unavailable.Here are portions of the logs that might be usefull in helping me with my problem.From ErrorLog:* BEGIN STACK DUMP: * 02/15/02 11:54:21 spid 63 * * Input Buffer 788 bytes - * e x e c k s p _ F o r m F i n i s h F O B R e p l a c e 1 0 1 3 7 2 * 3 , 1 . 2 8 0 0 0 0 , 0 , ' 1 ' , ' 1 ' , 1 0 9 8 8 4 1 , 1 * 0 9 8 8 4 2 ; e x e c k s p _ F o r m F i n i s h F O B R e p l a c e * 1 0 1 3 7 2 2 , 1 . 2 8 0 0 0 0 , 0 , ' 1 ' , ' 1 ' , 1 0 9 * 8 8 4 3 , 1 0 9 8 8 4 4 ; e x e c k s p _ F o r m F i n i s h F O B * R e p l a c e 1 0 1 3 6 5 9 , 1 . 2 8 0 0 0 0 , 0 , ' 1 ' , ' * 1 ' , 1 0 9 8 8 4 5 , 1 0 9 8 8 4 6 ; e x e c k s p _ F o r m F i * n i s h F O B R e p l a c e 1 0 1 3 6 6 0 , 1 . 2 8 0 0 0 0 , 0 , * ' 1 ' , ' 1 ' , 1 0 9 8 8 4 7 , 1 0 9 8 8 4 8 ; e x e c k s p * _ F o r m F i n i s h F O B R e p l a c e 1 0 1 3 7 2 1 , 1 . 2 8 0 * 0 0 0 , 0 , ' 1 ' , ' 1 ' , 1 0 9 8 8 4 9 , 1 0 9 8 8 5 0 * From SQL00001.dmp: 00000168: aa5801b5 04000032 0d890059 006f0075 00720020 .X.....2...Y.o.u.r. 0000017c: 00740072 0061006e 00730061 00630074 0069006f .t.r.a.n.s.a.c.t.i.o 00000190: 006e0020 00280070 0072006f 00630065 00730073 .n. .(.p.r.o.c.e.s.s 000001a4: 00200049 00440020 00230036 00330029 00200077 . .I.D. .#.6.3.). .w 000001b8: 00610073 00200064 00650061 0064006c 006f0063 .a.s. .d.e.a.d.l.o.c 000001cc: 006b0065 00640020 00770069 00740068 00200061 .k.e.d. .w.i.t.h. .a 000001e0: 006e006f 00740068 00650072 00200070 0072006f .n.o.t.h.e.r. .p.r.o 000001f4: 00630065 00730073 00200061 006e0064 00200068 .c.e.s.s. .a.n.d. .h 00000208: 00610073 00200062 00650065 006e0020 00630068 .a.s. .b.e.e.n. .c.h 0000021c: 006f0073 0065006e 00200061 00730020 00740068 .o.s.e.n. .a.s. .t.h 00000230: 00650020 00640065 00610064 006c006f 0063006b .e. .d.e.a.d.l.o.c.k 00000244: 00200076 00690063 00740069 006d002e 00200052 . .v.i.c.t.i.m... .R 00000258: 00650072 0075006e 00200079 006f0075 00720020 .e.r.u.n. .y.o.u.r. 0000026c: 00740072 0061006e 00730061 00630074 0069006f .t.r.a.n.s.a.c.t.i.o As you can see by reading the far right column, it tells you the transaction being completed when the stack dump was created was deadlocked with another process and made the deadlock victim.From Errorlog: 2002-02-15 11:54:21.96 spid63 Error: 3624, Severity: 20, State: 1. 2002-02-15 11:54:21.98 spid63 Log space info for tran 0:1147420 in database 5 Before: LogRecs= 56 Used= 5588, Rsvd= 13204, SysUsed= 0 After: LogRecs= 78 Used= 7632, Rsvd= 11028, SysUsed= 0 Short= 0, ShortComp= -11160, TotalUsed= 7632, Short%=-146.2 2002-02-15 11:54:22.04 spid63 Error: 3314, Severity: 21, State: 4 2002-02-15 11:54:22.04 spÍ{�wÀ �$�fX àÓXÐãL °ìÆ id63 Error while undoing logged operation in database 'iPDM2001Training'. Error at log record ID (714:8154:3)..2002-02-15 11:54:22.07 spid63 Error: 9001, Severity: 21, State: 1 2002-02-15 11:54:22.07 spid63 The log for database 'iPDM2001Training' is not available.. 2002-02-15 11:54:22.14 spid63 Error: 3314, Severity: 21, State: 2 2002-02-15 11:54:22.14 spid63 Error while undoing logged operation in database 'iPDM2001Training' |
|
Stack Dump and Database Marked Suspect 