Author |
Topic |
Westley
Posting Yak Master
229 Posts |
Posted - 2007-04-17 : 22:14:44
|
Guys, Got an issue with an DB where it turn itself to suspect with just some normal queries. Its SQL 2000 8.00.2175 on Win2K3 sp1.From SQL log, it got the following:ex_raise2: Exception raised, major=79, minor=87, severity=22, attempting to create symptom dumpError: 7987, Severity: 22, State: 1SQL Server Assertion: File: <logscan.cpp>, line=3187 Failed Assertion = '(m_lastLSN == NullLSN) || (m_lastLSN > m_curLSN)'.Any idea on what will be causing it and what can be done to fix it? We tried rebooting the instance with no luck and we finally restore the DB from last good backup. But we would like to find out the cause of it.Thanks |
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2007-04-18 : 01:57:38
|
I always look at disk problems first.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
Westley
Posting Yak Master
229 Posts |
Posted - 2007-04-18 : 03:32:16
|
Disk doesn't have any issues as we can see the file the whole time. And there is nothing shown in the Event view about disk having issues. |
|
|
Westley
Posting Yak Master
229 Posts |
Posted - 2007-04-18 : 03:39:38
|
By the way, here is another message I found:Error while undoing logged operation in database 'dbname'. Error at log record ID (191314:8296:477)..Any other ideas? |
|
|
SatyaSKJ
Starting Member
46 Posts |
Posted - 2007-04-18 : 04:50:31
|
See this relevant KBA http://support.microsoft.com/kb/319851 for the last issue. Relevant KBA http://support.microsoft.com/kb/828337/&&DI=6243&IG=30ddc38ccdae452c82a78b7fa13c264a&POS=4&CM=WPU&CE=1&CS=AWP&SR=1 for the first issue.Satya SKJSQL Server MVPhttp://www.sqlserver-qa.net |
|
|
Westley
Posting Yak Master
229 Posts |
Posted - 2007-04-18 : 05:55:23
|
Satya, Following the link you provided, only http://support.microsoft.com/kb/319851 works. And the fixes it suggested there was already included in sp3, which I'm already on sp4 which have got that patch in. So I don't think that is the issue here? Any other ideas?Thanks |
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2007-04-18 : 09:23:41
|
Have a look at the following link: http://support.microsoft.com/kb/828337. What is the result of this in your database?dbcc checkdb() with no_infomsgs You may have some inconsistencies in the database from a while ago. |
|
|
Westley
Posting Yak Master
229 Posts |
Posted - 2007-04-18 : 22:45:36
|
Thanks for the link and info. But that doesn't really say much.Since we lost the log of the DBA and we can't do anything with it, with the backup we had, we did the dbcc checkdb without any errors reported.Any other ideas? |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-04-19 : 03:48:01
|
RAM error?I use memtest86 for RAM tests. But it needs to run for 48 hours at least - which is probably not much good if your server is 24/7!Kristen |
|
|
SatyaSKJ
Starting Member
46 Posts |
Posted - 2007-04-19 : 06:43:55
|
As you have got SP4 already its better to take up the case to CSS in this case, for the root cause.Satya SKJSQL Server MVPhttp://www.sqlserver-qa.net |
|
|
Westley
Posting Yak Master
229 Posts |
Posted - 2007-04-19 : 20:35:31
|
I don't think its the RAM, and we did take the case up to CSS, but nothing as yet, so would like to see if anyone got any ideas that can speed up the process here.... |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-04-20 : 02:27:17
|
Can you reproduce the problem on a different machine? If not I would mark the machine Suspect too!Kristen |
|
|
|