September 9, 2010 at 9:57 am
Hi all -
This is the second time this has happened to me now. I've gone to move the log file from one drive to another via detach/attach. There were no connections, no open transaction, nothing...
I took the database offline, then detached it. Then, when I went to reattach the database, I got errors.
"The log scan number (xxxx) passed to log scan in database is not valid."
What?!? Does anyone have any ideas of what could be going on?
This is a 400 GB database, so recovery isn't very fast.
September 9, 2010 at 10:01 am
There is another thread who had almost the same error. Paul Randall helped the OP out. Check this thread.
-Roy
September 9, 2010 at 11:22 am
Right. I'm not necessarily looking for a fix to the problem, just ideas about the cause.
It has happened twice to the same database on the same drive. Before the detach, the database is fine...it isn't in suspect mode. But when I go to reattach the database, it won't re-attach since the log file is corrupted.
How does a log file become corrupted?
September 9, 2010 at 12:08 pm
IO subsystem problems, same as most other corruption. If I was in your place, I'd be taking a long, hard look at that drive plus all drivers, firmware, etc in the IO path.
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 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply