The error suggest that some other process is grabbing the log file and then SQL Server cannot get to
it, hence that error. That other process might be an anti-virus application or similar. Question is
why SQL Server doesn't have a lock on the file all the time? Seems almost like the autoclose
database option is set!
To find out which process is using the file, I thing that sysinternals has some tools.
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"PJ" <p.jones (AT) xsb (DOT) com> wrote
SQL Server 2000. |
This is what showed up in my Server logs before the
database became "Suspect":
LogMgr::FixupLogTail (): alignBuf 0x3c2ef000, writeSize
0xf000, filePos 0xe274ea00
blankSize 0x1e000, blkOffset 0x7a0f5, fileSeqNo 2602,
fcb status 0x3108142, handle 0x3a0, size 5841432 pages
FixupTail: Operating system error 33(The process cannot
access the file because another process has locked a
portion of the file.) encountered.
Error: 9001, Severity: 21, State: 1
and finaly this:
The log for database 'CV- 0803' is not available..
Unexpected error while commiting a ShrinkFile operation.
I have seen this before though I have no idea what these
things mean. I then take DB offline, then take it online
and that usually takes care of things. When that does not
work, I get an "Alter failed"...then I have to do a DB