Re: 9003 The LSN %S_LSN passed to log scan in database '%.*ls' is inva
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Sat, 26 Aug 2006 10:15:16 +0000 (UTC)
Cathy Soloway (CathySoloway@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
I recently tried to move 12 databases containing metadata for an
application from a dev db farm (64-bit SP4) of SQL Server 2000. When I
detached everything I got this error listed above. Luckily I could
recover from backup, but I'm trying to figure out why this occurred so I
can take steps to keep it from happening again. My question lies in the
parity setting on the LUNS....what should it be on a 64-bit Itanium
system (HP)? If this is not the issue, can someone direct me of other
possible root causes for this error?
You really got this error when you detached the databases? If you had
gotten this error when you tried to attach them, I would have suspected
that you did not detach the databases properly. (For instance, just copied
the files when the server was stopped.)
Parity settings on LUNs is completely beyond my realm, so I cannot address
that part.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- Prev by Date: Re: Customizing maintenance plan reporting in SQL2005
- Next by Date: Re: Management Studio & Views containing unions
- Previous by thread: Anyway to automatical generate script to populated DB from Access
- Next by thread: Re: Import Data
- Index(es):
Relevant Pages
|
