Thursday, March 22, 2012

Error: 5105 on MSDB database

Every couple of weeks it appears that my MSDB database is getting
corrupt. Here is my situation.
Everyday at 4 am I take a backup off all the instances, then at 5 am
the computer reboots. Once the computer is up all the instances try to
start up except MSDB will have a problem. When I log into Enterprise
Manager the instance is listed as Suspect. I have to restore the
database from the backup taken at 4 am and everything is fine.
Here is the error from the log file the last time it happened.
2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
error. The physical file name 'C:\Program Files\Microsoft SQL Server
\MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
But I have also received this error:
2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
process cannot access the file because it is being used by another
process.) during the creation/opening of physical device C:\Program
Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
for virtual device number (VDN) 1.
I have no idea what this other process would be.
Any ideas?
Thanks,
JeffSome anti-virus software perhaps?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message news:1179174709.370501.139320@.h2g2000hsg.googlegroup
s.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>|||On May 14, 1:31 pm, "jeffchi...@.gmail.com" <jeffchi...@.gmail.com>
wrote:
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
> Any ideas?
> Thanks,
> Jeff
I actually get both of the errors each time, one is from the sql
agent. I am new to sql server.
Thanks.|||On May 14, 1:41 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> Some anti-virus software perhaps?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph
ttp://sqlblog.com/blogs/tibor_karaszi
> <jeffchi...@.gmail.com> wrote in messagenews:1179174709.370501.139320@.h2g20
00hsg.googlegroups.com...
>
>
>
>
It might be possible but why always the same database each time?|||Try excluding msdb from the backup and see if you get the same error
post-reboot. Also if you skip the reboot, does sql continue indefinitely
without a problem?
Someone mentioned antivirus. Not sure that would cause your particular
issue, but you do have the AV set to exclude .mdf and .ldf file types,
right?
TheSQLGuru
President
Indicium Resources, Inc.
<jeffchirco@.gmail.com> wrote in message
news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>|||On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:[vbcol=seagreen]
> Try excluding msdb from the backup and see if you get the same error
> post-reboot. Also if you skip the reboot, does sql continue indefinitely
> without a problem?
> Someone mentioned antivirus. Not sure that would cause your particular
> issue, but you do have the AV set to exclude .mdf and .ldf file types,
> right?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> <jeffchi...@.gmail.com> wrote in message
> news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
>
>
>
>
>
It's hard cause it doesn't happen every day. But yes it does appear
there if we skip the reboot then the problem goes away. But for some
reason this computer requires a reboot. A very small sql database is
on it.
No mdf and ldf files are not excluded from the antivirus. They should
be?|||> No mdf and ldf files are not excluded from the antivirus. They should
> be?
Well, unless you appreciate the exact type of error you have, you want to ex
clude them... :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message
news:1179241236.636144.163400@.u30g2000hsc.googlegroups.com...
> On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
> It's hard cause it doesn't happen every day. But yes it does appear
> there if we skip the reboot then the problem goes away. But for some
> reason this computer requires a reboot. A very small sql database is
> on it.
> No mdf and ldf files are not excluded from the antivirus. They should
> be?
>

No comments:

Post a Comment