March 5, 2010 at 7:04 am
I have backed up and copied a database from my old SQL 2000 box to my brand new SQL 2008 box (Server 2008 R2 / SQL 2008)
When I go to restore my main application database, I get the following log...
10 percent processed.
20 percent processed.
…
90 percent processed.
100 percent processed.
Processed 1236512 pages for database 'Sage_App', file 'sage_App_Data' on file 1.
Processed 31304 pages for database 'Sage_App', file 'sage_App_Log' on file 1.
Converting database 'Sage_App' from version 539 to the current version 655.
Database 'Sage_App' running the upgrade step from version 539 to version 551.
Database 'Sage_App' running the upgrade step from version 551 to version 552.
Database 'Sage_App' running the upgrade step from version 552 to version 611.
…
Database 'Sage_App' running the upgrade step from version 646 to version 647.
Database 'Sage_App' running the upgrade step from version 647 to version 648.
Database 'Sage_App' running the upgrade step from version 648 to version 649.
Msg 3167, Level 16, State 1, Line 1
RESTORE could not start database 'Sage_App'.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
In the event viewer I am getting 1 error, Event ID: 928,
"During upgrade, database raised exception 474, severity 25, state 0, address 000000000233EF67. Use the exception number to determine the cause."
The "help" link brings me to the "Not further information on this error" page at Microsoft
I have run DBCC CHECKDB on all the databases I am having problems with on the old box, no errors (They are the same basic database, just different points in time)
March 5, 2010 at 7:50 am
Couple of questions...
1. Did you run the upgrade adviser?
2. Do you have computed columns in any of your tables?
-Roy
March 5, 2010 at 7:52 am
I did not run upgrade advisor, but I will against the old database system to see what it shows; and there were no computerd columns that I know of... it was a SQL 2000 database, I thought computed columns didnt come out until 2005, could be wrong though... I will advise.
March 5, 2010 at 8:30 am
Advisor resulted in minor warnings only... All of these are correctable after the fact.
March 5, 2010 at 8:48 am
Severity level 19 and higher always writes the actual error in the SQL Server error log. Can you check what it is showing in the SQL Server error log?
19 and higher are fatal errors that can be caused by hardware issues as well.
-Roy
March 5, 2010 at 8:57 am
there are a couple of warnings I hadn't noticed before... could that cause this issue?
03/04/2010 21:51:50,spid58,Unknown,During upgrade<c/> database raised exception 474<c/> severity 25<c/> state 0<c/> address 000000000233EF67. Use the exception number to determine the cause.
03/04/2010 21:51:50,spid58,Unknown,Error: 928<c/> Severity: 20<c/> State: 1.
03/04/2010 21:51:36,spid58,Unknown,Warning: A column nullability inconsistency was detected in the metadata of index "IX_prtrxp" (index_id = 1) on object ID 1431676148 in database "Sage_App". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.
03/04/2010 21:51:31,spid58,Unknown,Warning: A column nullability inconsistency was detected in the metadata of index "PK_ExtSystemTransLog" (index_id = 2) on object ID 127808013 in database "Sage_App". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.
03/04/2010 21:50:46,spid58,Unknown,Recovery completed for database Sage_App (database ID 12) in 2 second(s) (analysis 80 ms<c/> redo 2547 ms<c/> undo 80 ms.) This is an informational message only. No user action is required.
03/04/2010 21:50:46,spid58,Unknown,Recovery is writing a checkpoint in database 'Sage_App' (12). This is an informational message only. No user action is required.
03/04/2010 21:50:43,spid58,Unknown,Starting up database 'Sage_App'.
03/04/2010 21:50:29,spid58,Unknown,The database 'Sage_App' is marked RESTORING and is in a state that does not allow recovery to be run.
03/04/2010 21:50:29,spid58,Unknown,Starting up database 'Sage_App'.
March 5, 2010 at 10:48 am
You have a corrupted index. I am not an expert in corruption. Please do not do anything to fix it right now. I will try to get some better help than me on this case...
-Roy
March 5, 2010 at 11:03 am
Please run DBCC CheckCatalog on the original database (on SQL 2000).
On SQL 2000, checkDB does not run checkcatalog, hence schema corruption (as this appears to be) can go unnoticed for long periods of time.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply