April 6, 2009 at 4:17 pm
When i try to restore the backup of sql server 2000 8.00.768 and restore in sql server 2000
i get the following message
Msg 3456, Level 21, State 1, Server ' ' (11). Page: LSN = (15:29:2), type = 1. Log: OpCode = 9, context 2, PrevPageLSN: (14:503:4).
and with a short stack
Short Stack Dump
* 009BA08C Module(sqlservr+005BA08C) (GetOSErrString+00004F68)
* 009BA9B5 Module(sqlservr+005BA9B5) (GetOSErrString+00005891)
* 006EE757 Module(sqlservr+002EE757) (SQLExit+00186C60)
* 005FA686 Module(sqlservr+001FA686) (SQLExit+00092B8F)
* 009909F8 Module(sqlservr+005909F8) (CDStream::operator=+0004685B)
* 009A2060 Module(sqlservr+005A2060) (CDStream::operator=+00057EC3)
* 00A0A997 Module(sqlservr+0060A997) (CDStream::PrintDumpHeader+0004B8BB)
* 009DD80B Module(sqlservr+005DD80B) (CDStream::PrintDumpHeader+0001E72F)
* 009DE724 Module(sqlservr+005DE724) (CDStream::PrintDumpHeader+0001F648)
* 009D3A21 Module(sqlservr+005D3A21) (CDStream::PrintDumpHeader+00014945)
* 009E2CE5 Module(sqlservr+005E2CE5) (CDStream::PrintDumpHeader+00023C09)
* 00782B6F Module(sqlservr+00382B6F) (SQLExit+0021B078)
* 00415D04 Module(sqlservr+00015D04)
* 00416214 Module(sqlservr+00016214)
* 00415F28 Module(sqlservr+00015F28)
* 0049C32E Module(sqlservr+0009C32E)
* 0049C46A Module(sqlservr+0009C46A)
* 41075309 Module(ums+00005309) (ProcessWorkRequests+000002D9 Line 456+00000000)
* 41074978 Module(ums+00004978) (ThreadStartRoutine+00000098 Line 263+00000007)
* 7C34940F Module(MSVCR71+0000940F) (endthread+000000AA)
* 77E64829 Module(kernel32+00024829) (GetModuleHandleA+000000DF)
Need help
April 6, 2009 at 4:50 pm
Are you restoring a user database? And are you restoring to the RTM level?
I wouldn't expect this, but perhaps if you're restoring a system database.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
April 7, 2009 at 8:32 am
I am restoring a user DB to SQL 2000 SP3/SP4
April 7, 2009 at 8:48 am
There have been some bugs that would cause this - see http://support.microsoft.com/kb/329487 and http://support.microsoft.com/kb/831950.
PS I found these doing a Google search on the error message - always try that first to see if there's an applicable KB article.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
April 7, 2009 at 10:42 am
http://support.microsoft.com/kb/329487
--This is pre SP3 fixed
http://support.microsoft.com/kb/831950
No logshipping configured
I went through the articles. I can apply SP4 and check if it is resolved.However, as it is production, i am bit reluctant to do it.
The purpose of putting it in this forum was to get your(Paul) view on this.
April 7, 2009 at 11:15 am
Yup - I realize that. The only things I can suggest in this case are that it's either a bug or a corruption in your backup.
Unfortunately, on SQL 2000, its almost impossible to tell whether it's a backup corruption or not.
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
April 7, 2009 at 11:57 am
Thanks. Sorry , I forgot to add the information.
I was able to restore the backup in SQL 2005. So, i am not sure if it is a real corruption.
I might try with MSFT to find if it is a bug or not.
Thank you.
April 7, 2009 at 12:43 pm
ok - that screams 'bug' at me - it wouldn't work on 2005 if the backup was corrupt.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply