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 |
|
Peggy
Starting Member
2 Posts |
 Posted - 2009-05-11 : 23:16:00
|
| Hello. Using MSSQL 2000\SP3 with SunSystems 5.1.5. Have received the following SQL error message: "Fatal Error 8908 occurred at May 11, 2008, 1:20PM" What does this mean? We have been having trouble with this database for about a week. This error both pre-dates and continues since the following script was run in QA, as prescribed by our Sun helpdesk: UPDATE SALFMSCSET HIGH_JRNAL= '13754' WHERE D_BASE = 'WCS' AND A_B = 'A' The script was successful in allowing us to re-access most of the database (continue our work). But some reports are still blocked by this error. Other messages include: "Communication Link Failure".Ideas |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2009-05-12 : 03:51:21
|
| The first thing I would do is run a DBCC CHECKDB()Have a look here: http://technet.microsoft.com/en-us/library/aa226351(sql.80).aspx |
 |
|
|
Peggy
Starting Member
2 Posts |
Posted - 2009-05-12 : 06:20:02
|
| Thanks. I did that, and it seems to be suggesting a REPAIR_REBUILD. Here is the bottom line of the multipage result: CHECKDB found 0 allocation errors and 8 consistency errors in database 'SUNDB'.repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (SUNDB ).But, I can't seem to get the script right (I'm a hack at SQL, sorry). It's not: DBCC CHECKDB ("SUNDB",REPAIR_REBUILD) -- so what is the script? You're help is a dream. |
|
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2009-05-12 : 07:02:10
|
| It should be: DBCC CHECKDB ('SUNDB',REPAIR_REBUILD)(single quotes, not double) |
|
|
|
|
|
|
Error 8908