I Did a database backup from serverA and restore to
serverB using w2k. I detached the database from serverB,
and when try to attach to the restored database, I got an
error" Error 9003:The LSN(120998:148:1) passed to log
scan in database "xyz" is invalid.
How do I fix this error. Thanks.Hi
That is a Severity 20 error. Errors messages with a severity level of 20 or
higher are considered fatal errors and terminate the client connection.
There is a KB article # 328354 (FIX: A RESTORE DATABASE WITH RECOVERY
Statement Can Fail with Error 9003 or Error 9004), but that was fixed in
SP3.
If you are running SP3, you either have a corrupt DB, or you have
encountered another problem. In the latter's case, call your local Microsoft
PSS.
I would bet that the DB is corrupt. Where did you try to attach the DB
again, server B?
Can you try to restore the backup from Server A again on Server B and then
run DBCC CHECKDB and DBCC CHECKALLOC to see if you have corruption and it
came across in the backup?
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"Someone" <anonymous@.discussions.microsoft.com> wrote in message
news:1ff201c3e05c$bf1da530$a501280a@.phx.gbl...
quote:|||Thank you for your reply. I applied sp3 and reattach the
> Can someone please help me with this problem.
> I Did a database backup from serverA and restore to
> serverB using w2k. I detached the database from serverB,
> and when try to attach to the restored database, I got an
> error" Error 9003:The LSN(120998:148:1) passed to log
> scan in database "xyz" is invalid.
> How do I fix this error. Thanks.
database and I got the same error again. I am doing a new
restore as I write this and I will try to attach again.
Thanks.
quote:
>--Original Message--
>Hi
>That is a Severity 20 error. Errors messages with a
severity level of 20 or
quote:
>higher are considered fatal errors and terminate the
client connection.
quote:
>There is a KB article # 328354 (FIX: A RESTORE DATABASE
WITH RECOVERY
quote:
>Statement Can Fail with Error 9003 or Error 9004), but
that was fixed in
quote:
>SP3.
>If you are running SP3, you either have a corrupt DB, or
you have
quote:
>encountered another problem. In the latter's case, call
your local Microsoft
quote:
>PSS.
>I would bet that the DB is corrupt. Where did you try to
attach the DB
quote:
>again, server B?
>Can you try to restore the backup from Server A again on
Server B and then
quote:
>run DBCC CHECKDB and DBCC CHECKALLOC to see if you have
corruption and it
quote:
>came across in the backup?
>
>--
>--
>Mike Epprecht, Microsoft SQL Server MVP
>Epprecht Consulting (PTY) LTD
>Johannesburg, South Africa
>Mobile: +27-82-552-0268
>IM: mike@.NOSPAMepprecht.net
>Specialist SQL Server Solutions and Consulting
>"Someone" <anonymous@.discussions.microsoft.com> wrote in
message
quote:|||I just finished the restore, and got the same error when
>news:1ff201c3e05c$bf1da530$a501280a@.phx.gbl...
serverB,[QUOTE]
an[QUOTE]
>
>.
>
I tried to attach to the database again.
quote:
>--Original Message--
>Thank you for your reply. I applied sp3 and reattach the
>database and I got the same error again. I am doing a
new
quote:|||wsd
>restore as I write this and I will try to attach again.
>Thanks.
>
>severity level of 20 or
>client connection.
DATABASE[QUOTE]
>WITH RECOVERY
>that was fixed in
or[QUOTE]
>you have
>your local Microsoft
to[QUOTE]
>attach the DB
on[QUOTE]
>Server B and then
>corruption and it
in[QUOTE]
>message
>serverB,
got[QUOTE]
>an
>.
>
From http://www.google.com.tr/search?q=e...elopmentnow.com
