My Sql server msdb database demaged.
I did not backuped it before.
I copy the msdbdata.mdf and msdblog.ldf from other SQL database.
But not working.
How can I fix it
ThankHi Chen,
Search for << msdb database marked as "suspect" >> in this forum. And you
should be able to get the answer.
Also check this out: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=33914
Thanks
GYK
Showing posts with label suspect. Show all posts
Showing posts with label suspect. Show all posts
Wednesday, March 7, 2012
msdb(Suspect)
My Sql server msdb database demaged.
I did not backuped it before.
I copy the msdbdata.mdf and msdblog.ldf from other SQL database.
But not working.
How can I fix it
Thank
Hi Chen,
Search for << msdb database marked as "suspect" >> in this forum. And you
should be able to get the answer.
Also check this out: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=33914
Thanks
GYK
I did not backuped it before.
I copy the msdbdata.mdf and msdblog.ldf from other SQL database.
But not working.
How can I fix it
Thank
Hi Chen,
Search for << msdb database marked as "suspect" >> in this forum. And you
should be able to get the answer.
Also check this out: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=33914
Thanks
GYK
msdb(Suspect)
My Sql server msdb database demaged.
I did not backuped it before.
I copy the msdbdata.mdf and msdblog.ldf from other SQL database.
But not working.
How can I fix it
ThankHi Chen,
Search for << msdb database marked as "suspect" >> in this forum. And you
should be able to get the answer.
Also check this out: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=33914
--
Thanks
GYK
I did not backuped it before.
I copy the msdbdata.mdf and msdblog.ldf from other SQL database.
But not working.
How can I fix it
ThankHi Chen,
Search for << msdb database marked as "suspect" >> in this forum. And you
should be able to get the answer.
Also check this out: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=33914
--
Thanks
GYK
Saturday, February 25, 2012
MSDB suspect
Hi,
What are the steps I should execute if MSDB database is showing suspect.
The conditions is we dont have a backup but the sqlserver is running.Look at the sql server logs and see what might have caused this. Look in bol for sp_resetstatus. Worst case scenario, you will have to detach the msdb and run instmsdb.sql to recreate (however, you will lose all information stored in the msdb - DTS packages, scheduled tasks, backup/restore history, replication).
Oh yes - One last step - BACKUP ... :-)
What are the steps I should execute if MSDB database is showing suspect.
The conditions is we dont have a backup but the sqlserver is running.Look at the sql server logs and see what might have caused this. Look in bol for sp_resetstatus. Worst case scenario, you will have to detach the msdb and run instmsdb.sql to recreate (however, you will lose all information stored in the msdb - DTS packages, scheduled tasks, backup/restore history, replication).
Oh yes - One last step - BACKUP ... :-)
msdb suspect
After move the whole sql server databases to a new box, msdb shows suspect,
the other databases all work fine.
A select statement shows that the staus of msdb is 280.
After I change the status to 24, it still does not work. I can't start
SQLServerAgent now.
Please help!!!
thanks, FeiCheck out the SQL Server errorlog why it became suspect. Perhaps you don't h
ave the files for msdb
in the same directory as the original SQL Server, for instance.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
> After move the whole sql server databases to a new box, msdb shows suspect
,
> the other databases all work fine.
> A select statement shows that the staus of msdb is 280.
> After I change the status to 24, it still does not work. I can't start
> SQLServerAgent now.
> Please help!!!
> thanks, Fei|||Tibor,
Thanks for your quick response.
I checked the errorlog and there is no related error msg found in the log.
The msdb files are on a different location (e:drive) from the original
installation (c: drive)because we wanted to seperate the datafiles from the
software files. The other system database files such as master, model are al
l
in the same location as the msdb and the other system databases are just
fine.
Any suggestions?
Fei
"Tibor Karaszi" wrote:
> Check out the SQL Server errorlog why it became suspect. Perhaps you don't
have the files for msdb
> in the same directory as the original SQL Server, for instance.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>|||Since the path for msdb is in the master database, it is expected that msdb
becomes suspect if you
move the files to some different location. I suggest you move the files back
and then follow
instructions in either KB 224071 if on 2000 or Books Online of on 2005 on ho
w to move files for
msdb.
Also, there *are* error messages for msdb to be found in the errorlog file,
you just need to find
the right errorlog file (first startup when it became suspect).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...[vbcol=seagreen]
> Tibor,
> Thanks for your quick response.
> I checked the errorlog and there is no related error msg found in the log.
> The msdb files are on a different location (e:drive) from the original
> installation (c: drive)because we wanted to seperate the datafiles from th
e
> software files. The other system database files such as master, model are
all
> in the same location as the msdb and the other system databases are just
> fine.
> Any suggestions?
>
> Fei
> "Tibor Karaszi" wrote:
>|||Hi Tibor
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location.
In KB 224071 they mention in how to move MSDB database the different
location to be moved the MSDB database
4. Move the Msdbdata.mdf and Msdblog.ldf files from the current
location (D:\Mssql8\Data) to the new location (E:\Mssql8\Data).
However the new master's path is dE:\SQLDATA\master.mdf
and -lE:\SQLDATA\mastlog.ldf. So should msdb database be attach to the same
path?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location. I
> suggest you move the files back and then follow instructions in either KB
> 224071 if on 2000 or Books Online of on 2005 on how to move files for
> msdb.
> Also, there *are* error messages for msdb to be found in the errorlog
> file, you just need to find the right errorlog file (first startup when it
> became suspect).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>|||No msdb doesn't have to be in the same path as master. But the path to msdb
is *in* master, so you
can't just move the files to some other location (which is true for any data
base).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Uri Dimant" <urid@.iscar.co.il> wrote in message news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl.
.
> Hi Tibor
> In KB 224071 they mention in how to move MSDB database the different loc
ation to be moved the
> MSDB database
> 4. Move the Msdbdata.mdf and Msdblog.ldf files from the current locat
ion (D:\Mssql8\Data) to
> the new location (E:\Mssql8\Data).
>
> However the new master's path is dE:\SQLDATA\master.mdf and -lE:\SQLDATA\m
astlog.ldf. So should
> msdb database be attach to the same path?
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n message
> news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
>|||Tibor
Ah, yes. I just misunderstood your comments.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uh84O8ZvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> No msdb doesn't have to be in the same path as master. But the path to
> msdb is *in* master, so you can't just move the files to some other
> location (which is true for any database).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
>
the other databases all work fine.
A select statement shows that the staus of msdb is 280.
After I change the status to 24, it still does not work. I can't start
SQLServerAgent now.
Please help!!!
thanks, FeiCheck out the SQL Server errorlog why it became suspect. Perhaps you don't h
ave the files for msdb
in the same directory as the original SQL Server, for instance.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
> After move the whole sql server databases to a new box, msdb shows suspect
,
> the other databases all work fine.
> A select statement shows that the staus of msdb is 280.
> After I change the status to 24, it still does not work. I can't start
> SQLServerAgent now.
> Please help!!!
> thanks, Fei|||Tibor,
Thanks for your quick response.
I checked the errorlog and there is no related error msg found in the log.
The msdb files are on a different location (e:drive) from the original
installation (c: drive)because we wanted to seperate the datafiles from the
software files. The other system database files such as master, model are al
l
in the same location as the msdb and the other system databases are just
fine.
Any suggestions?
Fei
"Tibor Karaszi" wrote:
> Check out the SQL Server errorlog why it became suspect. Perhaps you don't
have the files for msdb
> in the same directory as the original SQL Server, for instance.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>|||Since the path for msdb is in the master database, it is expected that msdb
becomes suspect if you
move the files to some different location. I suggest you move the files back
and then follow
instructions in either KB 224071 if on 2000 or Books Online of on 2005 on ho
w to move files for
msdb.
Also, there *are* error messages for msdb to be found in the errorlog file,
you just need to find
the right errorlog file (first startup when it became suspect).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...[vbcol=seagreen]
> Tibor,
> Thanks for your quick response.
> I checked the errorlog and there is no related error msg found in the log.
> The msdb files are on a different location (e:drive) from the original
> installation (c: drive)because we wanted to seperate the datafiles from th
e
> software files. The other system database files such as master, model are
all
> in the same location as the msdb and the other system databases are just
> fine.
> Any suggestions?
>
> Fei
> "Tibor Karaszi" wrote:
>|||Hi Tibor
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location.
In KB 224071 they mention in how to move MSDB database the different
location to be moved the MSDB database
4. Move the Msdbdata.mdf and Msdblog.ldf files from the current
location (D:\Mssql8\Data) to the new location (E:\Mssql8\Data).
However the new master's path is dE:\SQLDATA\master.mdf
and -lE:\SQLDATA\mastlog.ldf. So should msdb database be attach to the same
path?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location. I
> suggest you move the files back and then follow instructions in either KB
> 224071 if on 2000 or Books Online of on 2005 on how to move files for
> msdb.
> Also, there *are* error messages for msdb to be found in the errorlog
> file, you just need to find the right errorlog file (first startup when it
> became suspect).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>|||No msdb doesn't have to be in the same path as master. But the path to msdb
is *in* master, so you
can't just move the files to some other location (which is true for any data
base).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Uri Dimant" <urid@.iscar.co.il> wrote in message news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl.
.
> Hi Tibor
> In KB 224071 they mention in how to move MSDB database the different loc
ation to be moved the
> MSDB database
> 4. Move the Msdbdata.mdf and Msdblog.ldf files from the current locat
ion (D:\Mssql8\Data) to
> the new location (E:\Mssql8\Data).
>
> However the new master's path is dE:\SQLDATA\master.mdf and -lE:\SQLDATA\m
astlog.ldf. So should
> msdb database be attach to the same path?
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n message
> news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
>|||Tibor
Ah, yes. I just misunderstood your comments.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uh84O8ZvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> No msdb doesn't have to be in the same path as master. But the path to
> msdb is *in* master, so you can't just move the files to some other
> location (which is true for any database).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
>
msdb suspect
After move the whole sql server databases to a new box, msdb shows suspect,
the other databases all work fine.
A select statement shows that the staus of msdb is 280.
After I change the status to 24, it still does not work. I can't start
SQLServerAgent now.
Please help!!!
thanks, Fei
Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for msdb
in the same directory as the original SQL Server, for instance.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
> After move the whole sql server databases to a new box, msdb shows suspect,
> the other databases all work fine.
> A select statement shows that the staus of msdb is 280.
> After I change the status to 24, it still does not work. I can't start
> SQLServerAgent now.
> Please help!!!
> thanks, Fei
|||Tibor,
Thanks for your quick response.
I checked the errorlog and there is no related error msg found in the log.
The msdb files are on a different location (e:drive) from the original
installation (c: drive)because we wanted to seperate the datafiles from the
software files. The other system database files such as master, model are all
in the same location as the msdb and the other system databases are just
fine.
Any suggestions?
Fei
"Tibor Karaszi" wrote:
> Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for msdb
> in the same directory as the original SQL Server, for instance.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>
|||Since the path for msdb is in the master database, it is expected that msdb becomes suspect if you
move the files to some different location. I suggest you move the files back and then follow
instructions in either KB 224071 if on 2000 or Books Online of on 2005 on how to move files for
msdb.
Also, there *are* error messages for msdb to be found in the errorlog file, you just need to find
the right errorlog file (first startup when it became suspect).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...[vbcol=seagreen]
> Tibor,
> Thanks for your quick response.
> I checked the errorlog and there is no related error msg found in the log.
> The msdb files are on a different location (e:drive) from the original
> installation (c: drive)because we wanted to seperate the datafiles from the
> software files. The other system database files such as master, model are all
> in the same location as the msdb and the other system databases are just
> fine.
> Any suggestions?
>
> Fei
> "Tibor Karaszi" wrote:
|||Hi Tibor
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location.
In KB 224071 they mention in how to move MSDB database the different
location to be moved the MSDB database
4. Move the Msdbdata.mdf and Msdblog.ldf files from the current
location (D:\Mssql8\Data) to the new location (E:\Mssql8\Data).
However the new master's path is dE:\SQLDATA\master.mdf
and -lE:\SQLDATA\mastlog.ldf. So should msdb database be attach to the same
path?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location. I
> suggest you move the files back and then follow instructions in either KB
> 224071 if on 2000 or Books Online of on 2005 on how to move files for
> msdb.
> Also, there *are* error messages for msdb to be found in the errorlog
> file, you just need to find the right errorlog file (first startup when it
> became suspect).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>
|||No msdb doesn't have to be in the same path as master. But the path to msdb is *in* master, so you
can't just move the files to some other location (which is true for any database).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Uri Dimant" <urid@.iscar.co.il> wrote in message news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> Hi Tibor
> In KB 224071 they mention in how to move MSDB database the different location to be moved the
> MSDB database
> 4. Move the Msdbdata.mdf and Msdblog.ldf files from the current location (D:\Mssql8\Data) to
> the new location (E:\Mssql8\Data).
>
> However the new master's path is dE:\SQLDATA\master.mdf and -lE:\SQLDATA\mastlog.ldf. So should
> msdb database be attach to the same path?
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
>
|||Tibor
Ah, yes. I just misunderstood your comments.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uh84O8ZvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> No msdb doesn't have to be in the same path as master. But the path to
> msdb is *in* master, so you can't just move the files to some other
> location (which is true for any database).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
>
the other databases all work fine.
A select statement shows that the staus of msdb is 280.
After I change the status to 24, it still does not work. I can't start
SQLServerAgent now.
Please help!!!
thanks, Fei
Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for msdb
in the same directory as the original SQL Server, for instance.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
> After move the whole sql server databases to a new box, msdb shows suspect,
> the other databases all work fine.
> A select statement shows that the staus of msdb is 280.
> After I change the status to 24, it still does not work. I can't start
> SQLServerAgent now.
> Please help!!!
> thanks, Fei
|||Tibor,
Thanks for your quick response.
I checked the errorlog and there is no related error msg found in the log.
The msdb files are on a different location (e:drive) from the original
installation (c: drive)because we wanted to seperate the datafiles from the
software files. The other system database files such as master, model are all
in the same location as the msdb and the other system databases are just
fine.
Any suggestions?
Fei
"Tibor Karaszi" wrote:
> Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for msdb
> in the same directory as the original SQL Server, for instance.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>
|||Since the path for msdb is in the master database, it is expected that msdb becomes suspect if you
move the files to some different location. I suggest you move the files back and then follow
instructions in either KB 224071 if on 2000 or Books Online of on 2005 on how to move files for
msdb.
Also, there *are* error messages for msdb to be found in the errorlog file, you just need to find
the right errorlog file (first startup when it became suspect).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...[vbcol=seagreen]
> Tibor,
> Thanks for your quick response.
> I checked the errorlog and there is no related error msg found in the log.
> The msdb files are on a different location (e:drive) from the original
> installation (c: drive)because we wanted to seperate the datafiles from the
> software files. The other system database files such as master, model are all
> in the same location as the msdb and the other system databases are just
> fine.
> Any suggestions?
>
> Fei
> "Tibor Karaszi" wrote:
|||Hi Tibor
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location.
In KB 224071 they mention in how to move MSDB database the different
location to be moved the MSDB database
4. Move the Msdbdata.mdf and Msdblog.ldf files from the current
location (D:\Mssql8\Data) to the new location (E:\Mssql8\Data).
However the new master's path is dE:\SQLDATA\master.mdf
and -lE:\SQLDATA\mastlog.ldf. So should msdb database be attach to the same
path?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location. I
> suggest you move the files back and then follow instructions in either KB
> 224071 if on 2000 or Books Online of on 2005 on how to move files for
> msdb.
> Also, there *are* error messages for msdb to be found in the errorlog
> file, you just need to find the right errorlog file (first startup when it
> became suspect).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>
|||No msdb doesn't have to be in the same path as master. But the path to msdb is *in* master, so you
can't just move the files to some other location (which is true for any database).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Uri Dimant" <urid@.iscar.co.il> wrote in message news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> Hi Tibor
> In KB 224071 they mention in how to move MSDB database the different location to be moved the
> MSDB database
> 4. Move the Msdbdata.mdf and Msdblog.ldf files from the current location (D:\Mssql8\Data) to
> the new location (E:\Mssql8\Data).
>
> However the new master's path is dE:\SQLDATA\master.mdf and -lE:\SQLDATA\mastlog.ldf. So should
> msdb database be attach to the same path?
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
>
|||Tibor
Ah, yes. I just misunderstood your comments.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uh84O8ZvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> No msdb doesn't have to be in the same path as master. But the path to
> msdb is *in* master, so you can't just move the files to some other
> location (which is true for any database).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
>
msdb suspect
After move the whole sql server databases to a new box, msdb shows suspect,
the other databases all work fine.
A select statement shows that the staus of msdb is 280.
After I change the status to 24, it still does not work. I can't start
SQLServerAgent now.
Please help!!!
thanks, FeiCheck out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for msdb
in the same directory as the original SQL Server, for instance.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
> After move the whole sql server databases to a new box, msdb shows suspect,
> the other databases all work fine.
> A select statement shows that the staus of msdb is 280.
> After I change the status to 24, it still does not work. I can't start
> SQLServerAgent now.
> Please help!!!
> thanks, Fei|||Tibor,
Thanks for your quick response.
I checked the errorlog and there is no related error msg found in the log.
The msdb files are on a different location (e:drive) from the original
installation (c: drive)because we wanted to seperate the datafiles from the
software files. The other system database files such as master, model are all
in the same location as the msdb and the other system databases are just
fine.
Any suggestions?
Fei
"Tibor Karaszi" wrote:
> Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for msdb
> in the same directory as the original SQL Server, for instance.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
> > After move the whole sql server databases to a new box, msdb shows suspect,
> > the other databases all work fine.
> >
> > A select statement shows that the staus of msdb is 280.
> >
> > After I change the status to 24, it still does not work. I can't start
> > SQLServerAgent now.
> >
> > Please help!!!
> >
> > thanks, Fei
>|||Since the path for msdb is in the master database, it is expected that msdb becomes suspect if you
move the files to some different location. I suggest you move the files back and then follow
instructions in either KB 224071 if on 2000 or Books Online of on 2005 on how to move files for
msdb.
Also, there *are* error messages for msdb to be found in the errorlog file, you just need to find
the right errorlog file (first startup when it became suspect).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
> Tibor,
> Thanks for your quick response.
> I checked the errorlog and there is no related error msg found in the log.
> The msdb files are on a different location (e:drive) from the original
> installation (c: drive)because we wanted to seperate the datafiles from the
> software files. The other system database files such as master, model are all
> in the same location as the msdb and the other system databases are just
> fine.
> Any suggestions?
>
> Fei
> "Tibor Karaszi" wrote:
>> Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for
>> msdb
>> in the same directory as the original SQL Server, for instance.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>> > After move the whole sql server databases to a new box, msdb shows suspect,
>> > the other databases all work fine.
>> >
>> > A select statement shows that the staus of msdb is 280.
>> >
>> > After I change the status to 24, it still does not work. I can't start
>> > SQLServerAgent now.
>> >
>> > Please help!!!
>> >
>> > thanks, Fei|||Hi Tibor
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location.
In KB 224071 they mention in how to move MSDB database the different
location to be moved the MSDB database
4. Move the Msdbdata.mdf and Msdblog.ldf files from the current
location (D:\Mssql8\Data) to the new location (E:\Mssql8\Data).
However the new master's path is dE:\SQLDATA\master.mdf
and -lE:\SQLDATA\mastlog.ldf. So should msdb database be attach to the same
path?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location. I
> suggest you move the files back and then follow instructions in either KB
> 224071 if on 2000 or Books Online of on 2005 on how to move files for
> msdb.
> Also, there *are* error messages for msdb to be found in the errorlog
> file, you just need to find the right errorlog file (first startup when it
> became suspect).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>> Tibor,
>> Thanks for your quick response.
>> I checked the errorlog and there is no related error msg found in the
>> log.
>> The msdb files are on a different location (e:drive) from the original
>> installation (c: drive)because we wanted to seperate the datafiles from
>> the
>> software files. The other system database files such as master, model are
>> all
>> in the same location as the msdb and the other system databases are just
>> fine.
>> Any suggestions?
>>
>> Fei
>> "Tibor Karaszi" wrote:
>> Check out the SQL Server errorlog why it became suspect. Perhaps you
>> don't have the files for msdb
>> in the same directory as the original SQL Server, for instance.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>> > After move the whole sql server databases to a new box, msdb shows
>> > suspect,
>> > the other databases all work fine.
>> >
>> > A select statement shows that the staus of msdb is 280.
>> >
>> > After I change the status to 24, it still does not work. I can't
>> > start
>> > SQLServerAgent now.
>> >
>> > Please help!!!
>> >
>> > thanks, Fei
>|||No msdb doesn't have to be in the same path as master. But the path to msdb is *in* master, so you
can't just move the files to some other location (which is true for any database).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Uri Dimant" <urid@.iscar.co.il> wrote in message news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> Hi Tibor
>> Since the path for msdb is in the master database, it is expected that msdb becomes suspect if
>> you move the files to some different location.
> In KB 224071 they mention in how to move MSDB database the different location to be moved the
> MSDB database
> 4. Move the Msdbdata.mdf and Msdblog.ldf files from the current location (D:\Mssql8\Data) to
> the new location (E:\Mssql8\Data).
>
> However the new master's path is dE:\SQLDATA\master.mdf and -lE:\SQLDATA\mastlog.ldf. So should
> msdb database be attach to the same path?
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
>> Since the path for msdb is in the master database, it is expected that msdb becomes suspect if
>> you move the files to some different location. I suggest you move the files back and then follow
>> instructions in either KB 224071 if on 2000 or Books Online of on 2005 on how to move files for
>> msdb.
>> Also, there *are* error messages for msdb to be found in the errorlog file, you just need to find
>> the right errorlog file (first startup when it became suspect).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>> Tibor,
>> Thanks for your quick response.
>> I checked the errorlog and there is no related error msg found in the log.
>> The msdb files are on a different location (e:drive) from the original
>> installation (c: drive)because we wanted to seperate the datafiles from the
>> software files. The other system database files such as master, model are all
>> in the same location as the msdb and the other system databases are just
>> fine.
>> Any suggestions?
>>
>> Fei
>> "Tibor Karaszi" wrote:
>> Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for
>> msdb
>> in the same directory as the original SQL Server, for instance.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>> > After move the whole sql server databases to a new box, msdb shows suspect,
>> > the other databases all work fine.
>> >
>> > A select statement shows that the staus of msdb is 280.
>> >
>> > After I change the status to 24, it still does not work. I can't start
>> > SQLServerAgent now.
>> >
>> > Please help!!!
>> >
>> > thanks, Fei
>>
>|||Tibor
Ah, yes. I just misunderstood your comments.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uh84O8ZvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> No msdb doesn't have to be in the same path as master. But the path to
> msdb is *in* master, so you can't just move the files to some other
> location (which is true for any database).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
>> Hi Tibor
>> Since the path for msdb is in the master database, it is expected that
>> msdb becomes suspect if you move the files to some different location.
>> In KB 224071 they mention in how to move MSDB database the different
>> location to be moved the MSDB database
>> 4. Move the Msdbdata.mdf and Msdblog.ldf files from the current
>> location (D:\Mssql8\Data) to the new location (E:\Mssql8\Data).
>>
>> However the new master's path is dE:\SQLDATA\master.mdf
>> and -lE:\SQLDATA\mastlog.ldf. So should msdb database be attach to the
>> same path?
>>
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
>> Since the path for msdb is in the master database, it is expected that
>> msdb becomes suspect if you move the files to some different location. I
>> suggest you move the files back and then follow instructions in either
>> KB 224071 if on 2000 or Books Online of on 2005 on how to move files for
>> msdb.
>> Also, there *are* error messages for msdb to be found in the errorlog
>> file, you just need to find the right errorlog file (first startup when
>> it became suspect).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>> Tibor,
>> Thanks for your quick response.
>> I checked the errorlog and there is no related error msg found in the
>> log.
>> The msdb files are on a different location (e:drive) from the original
>> installation (c: drive)because we wanted to seperate the datafiles from
>> the
>> software files. The other system database files such as master, model
>> are all
>> in the same location as the msdb and the other system databases are
>> just
>> fine.
>> Any suggestions?
>>
>> Fei
>> "Tibor Karaszi" wrote:
>> Check out the SQL Server errorlog why it became suspect. Perhaps you
>> don't have the files for msdb
>> in the same directory as the original SQL Server, for instance.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>> > After move the whole sql server databases to a new box, msdb shows
>> > suspect,
>> > the other databases all work fine.
>> >
>> > A select statement shows that the staus of msdb is 280.
>> >
>> > After I change the status to 24, it still does not work. I can't
>> > start
>> > SQLServerAgent now.
>> >
>> > Please help!!!
>> >
>> > thanks, Fei
>>
>>
>
the other databases all work fine.
A select statement shows that the staus of msdb is 280.
After I change the status to 24, it still does not work. I can't start
SQLServerAgent now.
Please help!!!
thanks, FeiCheck out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for msdb
in the same directory as the original SQL Server, for instance.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
> After move the whole sql server databases to a new box, msdb shows suspect,
> the other databases all work fine.
> A select statement shows that the staus of msdb is 280.
> After I change the status to 24, it still does not work. I can't start
> SQLServerAgent now.
> Please help!!!
> thanks, Fei|||Tibor,
Thanks for your quick response.
I checked the errorlog and there is no related error msg found in the log.
The msdb files are on a different location (e:drive) from the original
installation (c: drive)because we wanted to seperate the datafiles from the
software files. The other system database files such as master, model are all
in the same location as the msdb and the other system databases are just
fine.
Any suggestions?
Fei
"Tibor Karaszi" wrote:
> Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for msdb
> in the same directory as the original SQL Server, for instance.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
> > After move the whole sql server databases to a new box, msdb shows suspect,
> > the other databases all work fine.
> >
> > A select statement shows that the staus of msdb is 280.
> >
> > After I change the status to 24, it still does not work. I can't start
> > SQLServerAgent now.
> >
> > Please help!!!
> >
> > thanks, Fei
>|||Since the path for msdb is in the master database, it is expected that msdb becomes suspect if you
move the files to some different location. I suggest you move the files back and then follow
instructions in either KB 224071 if on 2000 or Books Online of on 2005 on how to move files for
msdb.
Also, there *are* error messages for msdb to be found in the errorlog file, you just need to find
the right errorlog file (first startup when it became suspect).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Fei" <Fei@.discussions.microsoft.com> wrote in message
news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
> Tibor,
> Thanks for your quick response.
> I checked the errorlog and there is no related error msg found in the log.
> The msdb files are on a different location (e:drive) from the original
> installation (c: drive)because we wanted to seperate the datafiles from the
> software files. The other system database files such as master, model are all
> in the same location as the msdb and the other system databases are just
> fine.
> Any suggestions?
>
> Fei
> "Tibor Karaszi" wrote:
>> Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for
>> msdb
>> in the same directory as the original SQL Server, for instance.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>> > After move the whole sql server databases to a new box, msdb shows suspect,
>> > the other databases all work fine.
>> >
>> > A select statement shows that the staus of msdb is 280.
>> >
>> > After I change the status to 24, it still does not work. I can't start
>> > SQLServerAgent now.
>> >
>> > Please help!!!
>> >
>> > thanks, Fei|||Hi Tibor
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location.
In KB 224071 they mention in how to move MSDB database the different
location to be moved the MSDB database
4. Move the Msdbdata.mdf and Msdblog.ldf files from the current
location (D:\Mssql8\Data) to the new location (E:\Mssql8\Data).
However the new master's path is dE:\SQLDATA\master.mdf
and -lE:\SQLDATA\mastlog.ldf. So should msdb database be attach to the same
path?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
> Since the path for msdb is in the master database, it is expected that
> msdb becomes suspect if you move the files to some different location. I
> suggest you move the files back and then follow instructions in either KB
> 224071 if on 2000 or Books Online of on 2005 on how to move files for
> msdb.
> Also, there *are* error messages for msdb to be found in the errorlog
> file, you just need to find the right errorlog file (first startup when it
> became suspect).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Fei" <Fei@.discussions.microsoft.com> wrote in message
> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>> Tibor,
>> Thanks for your quick response.
>> I checked the errorlog and there is no related error msg found in the
>> log.
>> The msdb files are on a different location (e:drive) from the original
>> installation (c: drive)because we wanted to seperate the datafiles from
>> the
>> software files. The other system database files such as master, model are
>> all
>> in the same location as the msdb and the other system databases are just
>> fine.
>> Any suggestions?
>>
>> Fei
>> "Tibor Karaszi" wrote:
>> Check out the SQL Server errorlog why it became suspect. Perhaps you
>> don't have the files for msdb
>> in the same directory as the original SQL Server, for instance.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>> > After move the whole sql server databases to a new box, msdb shows
>> > suspect,
>> > the other databases all work fine.
>> >
>> > A select statement shows that the staus of msdb is 280.
>> >
>> > After I change the status to 24, it still does not work. I can't
>> > start
>> > SQLServerAgent now.
>> >
>> > Please help!!!
>> >
>> > thanks, Fei
>|||No msdb doesn't have to be in the same path as master. But the path to msdb is *in* master, so you
can't just move the files to some other location (which is true for any database).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Uri Dimant" <urid@.iscar.co.il> wrote in message news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> Hi Tibor
>> Since the path for msdb is in the master database, it is expected that msdb becomes suspect if
>> you move the files to some different location.
> In KB 224071 they mention in how to move MSDB database the different location to be moved the
> MSDB database
> 4. Move the Msdbdata.mdf and Msdblog.ldf files from the current location (D:\Mssql8\Data) to
> the new location (E:\Mssql8\Data).
>
> However the new master's path is dE:\SQLDATA\master.mdf and -lE:\SQLDATA\mastlog.ldf. So should
> msdb database be attach to the same path?
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
>> Since the path for msdb is in the master database, it is expected that msdb becomes suspect if
>> you move the files to some different location. I suggest you move the files back and then follow
>> instructions in either KB 224071 if on 2000 or Books Online of on 2005 on how to move files for
>> msdb.
>> Also, there *are* error messages for msdb to be found in the errorlog file, you just need to find
>> the right errorlog file (first startup when it became suspect).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>> Tibor,
>> Thanks for your quick response.
>> I checked the errorlog and there is no related error msg found in the log.
>> The msdb files are on a different location (e:drive) from the original
>> installation (c: drive)because we wanted to seperate the datafiles from the
>> software files. The other system database files such as master, model are all
>> in the same location as the msdb and the other system databases are just
>> fine.
>> Any suggestions?
>>
>> Fei
>> "Tibor Karaszi" wrote:
>> Check out the SQL Server errorlog why it became suspect. Perhaps you don't have the files for
>> msdb
>> in the same directory as the original SQL Server, for instance.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>> > After move the whole sql server databases to a new box, msdb shows suspect,
>> > the other databases all work fine.
>> >
>> > A select statement shows that the staus of msdb is 280.
>> >
>> > After I change the status to 24, it still does not work. I can't start
>> > SQLServerAgent now.
>> >
>> > Please help!!!
>> >
>> > thanks, Fei
>>
>|||Tibor
Ah, yes. I just misunderstood your comments.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uh84O8ZvHHA.4540@.TK2MSFTNGP05.phx.gbl...
> No msdb doesn't have to be in the same path as master. But the path to
> msdb is *in* master, so you can't just move the files to some other
> location (which is true for any database).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OhPtlBTvHHA.4540@.TK2MSFTNGP05.phx.gbl...
>> Hi Tibor
>> Since the path for msdb is in the master database, it is expected that
>> msdb becomes suspect if you move the files to some different location.
>> In KB 224071 they mention in how to move MSDB database the different
>> location to be moved the MSDB database
>> 4. Move the Msdbdata.mdf and Msdblog.ldf files from the current
>> location (D:\Mssql8\Data) to the new location (E:\Mssql8\Data).
>>
>> However the new master's path is dE:\SQLDATA\master.mdf
>> and -lE:\SQLDATA\mastlog.ldf. So should msdb database be attach to the
>> same path?
>>
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:C6840BE3-DB95-4C18-A44E-7630B5A67734@.microsoft.com...
>> Since the path for msdb is in the master database, it is expected that
>> msdb becomes suspect if you move the files to some different location. I
>> suggest you move the files back and then follow instructions in either
>> KB 224071 if on 2000 or Books Online of on 2005 on how to move files for
>> msdb.
>> Also, there *are* error messages for msdb to be found in the errorlog
>> file, you just need to find the right errorlog file (first startup when
>> it became suspect).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:36CB5CBE-2373-4261-97C0-1AA615E564E4@.microsoft.com...
>> Tibor,
>> Thanks for your quick response.
>> I checked the errorlog and there is no related error msg found in the
>> log.
>> The msdb files are on a different location (e:drive) from the original
>> installation (c: drive)because we wanted to seperate the datafiles from
>> the
>> software files. The other system database files such as master, model
>> are all
>> in the same location as the msdb and the other system databases are
>> just
>> fine.
>> Any suggestions?
>>
>> Fei
>> "Tibor Karaszi" wrote:
>> Check out the SQL Server errorlog why it became suspect. Perhaps you
>> don't have the files for msdb
>> in the same directory as the original SQL Server, for instance.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Fei" <Fei@.discussions.microsoft.com> wrote in message
>> news:81056E87-078C-4E54-91EA-D2A7273B4554@.microsoft.com...
>> > After move the whole sql server databases to a new box, msdb shows
>> > suspect,
>> > the other databases all work fine.
>> >
>> > A select statement shows that the staus of msdb is 280.
>> >
>> > After I change the status to 24, it still does not work. I can't
>> > start
>> > SQLServerAgent now.
>> >
>> > Please help!!!
>> >
>> > thanks, Fei
>>
>>
>
MSDB of SQL marked Suspect
Hi guys, can anybody assist on how to resolve the issue of marked suspect database. Most especially MSDB?I have had this problem before, and I was able to solve it by restoring from a backup.
However, I would be interested to see other suggestions on how to approach this situation.
However, I would be interested to see other suggestions on how to approach this situation.
msdb marked as suspect
Hi All,
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,
Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,
Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
msdb marked as suspect
Hi All,
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
msdb marked as suspect
Hi All,
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
Following error message is displayed whenever i open the Sql Server
Management Studio
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information. (.Net SqlClient Data
Provider)
I am using Sql Server 2005 with single instance
-Regards,Seems you are in for a restore of your msdb database:
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Kallu" <Kallu@.discussions.microsoft.com> wrote in message
news:75BDFAB6-C334-475E-B60F-6327C32C4E8D@.microsoft.com...
> Hi All,
> Following error message is displayed whenever i open the Sql Server
> Management Studio
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information. (.Net SqlClient Data
> Provider)
> I am using Sql Server 2005 with single instance
> -Regards,
>
Monday, February 20, 2012
msdb is Suspect
Is am running SQL 2000 SP3 on a Win 2000 box.
My msdb is marked suspet. I ran sp_resetstatus and restarted SQL and
the dB is still suspect.
I found an article that recommends...
One approach would be to drop & recreate the msdb databases (see
instmsdb.sql and instserv.sql in the c:\mssql\install directory of your
sqlserver install). You would lose backup/restore histories, all
operators, scheduled tasks, etc. but would get it back up and running.
Is this the only solution? Is there a way to do this without loosing
my backup history?
TIA,
Larry...
Paul,
You are the man!!! This did the trick.
As always, thanks for your help!!!!
Larry...
My msdb is marked suspet. I ran sp_resetstatus and restarted SQL and
the dB is still suspect.
I found an article that recommends...
One approach would be to drop & recreate the msdb databases (see
instmsdb.sql and instserv.sql in the c:\mssql\install directory of your
sqlserver install). You would lose backup/restore histories, all
operators, scheduled tasks, etc. but would get it back up and running.
Is this the only solution? Is there a way to do this without loosing
my backup history?
TIA,
Larry...
Paul,
You are the man!!! This did the trick.
As always, thanks for your help!!!!
Larry...
msdb is corrupt
I have a user that corrupted msdb by trying to rebuild the indexes on the
backupfile table. I have removed the suspect flag so that the database is
available. And I have the scripts to completely rebuild msdb.
In the hopes of this problem being an allocation problem, I've tried
DBCC CHECKDB
DBCC CHECKALLOC
DBCC CHECKTABLE
DBCC REINDEX
all with the same result:
Server: Msg 823, Level 24, State 1, Line 1
I/O error (bad page ID) detected during read of BUF pointer = 0x1427de00,
page ptr = 0x448b0000, pageid = (0x1:0xf5f8), dbid = 4, status = 0x801, file
= E:\MSSQL7\DATA\msdbdata.mdf.
I also tried using bcp to get at the sysjobs table.
Besides restoring the database from a backup, which they don't have, is
there another way to get at the jobs and dts packages?I'd say its stuffed - maybe next time they'll back it up!
"Jo" <Jo@.discussions.microsoft.com> wrote in message
news:610925D1-F51F-486B-A056-F54CF4F088C8@.microsoft.com...
> I have a user that corrupted msdb by trying to rebuild the indexes on the
> backupfile table. I have removed the suspect flag so that the database is
> available. And I have the scripts to completely rebuild msdb.
> In the hopes of this problem being an allocation problem, I've tried
> DBCC CHECKDB
> DBCC CHECKALLOC
> DBCC CHECKTABLE
> DBCC REINDEX
> all with the same result:
> Server: Msg 823, Level 24, State 1, Line 1
> I/O error (bad page ID) detected during read of BUF pointer = 0x1427de00,
> page ptr = 0x448b0000, pageid = (0x1:0xf5f8), dbid = 4, status = 0x801,
file
> = E:\MSSQL7\DATA\msdbdata.mdf.
> I also tried using bcp to get at the sysjobs table.
> Besides restoring the database from a backup, which they don't have, is
> there another way to get at the jobs and dts packages?
>|||I tend to aggree. But before I give up, I was just trying to see if there wa
s
a solution. I remember in 6.5, the contents of pages could be changed with a
dbcc command. I understand that there's huge differences between 6.5 and 7.0
.
But since the database is basicly toast, I thought it would be worth a try.
"Mary Bray" wrote:
> I'd say its stuffed - maybe next time they'll back it up!
> "Jo" <Jo@.discussions.microsoft.com> wrote in message
> news:610925D1-F51F-486B-A056-F54CF4F088C8@.microsoft.com...
> file
>
>
backupfile table. I have removed the suspect flag so that the database is
available. And I have the scripts to completely rebuild msdb.
In the hopes of this problem being an allocation problem, I've tried
DBCC CHECKDB
DBCC CHECKALLOC
DBCC CHECKTABLE
DBCC REINDEX
all with the same result:
Server: Msg 823, Level 24, State 1, Line 1
I/O error (bad page ID) detected during read of BUF pointer = 0x1427de00,
page ptr = 0x448b0000, pageid = (0x1:0xf5f8), dbid = 4, status = 0x801, file
= E:\MSSQL7\DATA\msdbdata.mdf.
I also tried using bcp to get at the sysjobs table.
Besides restoring the database from a backup, which they don't have, is
there another way to get at the jobs and dts packages?I'd say its stuffed - maybe next time they'll back it up!
"Jo" <Jo@.discussions.microsoft.com> wrote in message
news:610925D1-F51F-486B-A056-F54CF4F088C8@.microsoft.com...
> I have a user that corrupted msdb by trying to rebuild the indexes on the
> backupfile table. I have removed the suspect flag so that the database is
> available. And I have the scripts to completely rebuild msdb.
> In the hopes of this problem being an allocation problem, I've tried
> DBCC CHECKDB
> DBCC CHECKALLOC
> DBCC CHECKTABLE
> DBCC REINDEX
> all with the same result:
> Server: Msg 823, Level 24, State 1, Line 1
> I/O error (bad page ID) detected during read of BUF pointer = 0x1427de00,
> page ptr = 0x448b0000, pageid = (0x1:0xf5f8), dbid = 4, status = 0x801,
file
> = E:\MSSQL7\DATA\msdbdata.mdf.
> I also tried using bcp to get at the sysjobs table.
> Besides restoring the database from a backup, which they don't have, is
> there another way to get at the jobs and dts packages?
>|||I tend to aggree. But before I give up, I was just trying to see if there wa
s
a solution. I remember in 6.5, the contents of pages could be changed with a
dbcc command. I understand that there's huge differences between 6.5 and 7.0
.
But since the database is basicly toast, I thought it would be worth a try.
"Mary Bray" wrote:
> I'd say its stuffed - maybe next time they'll back it up!
> "Jo" <Jo@.discussions.microsoft.com> wrote in message
> news:610925D1-F51F-486B-A056-F54CF4F088C8@.microsoft.com...
> file
>
>
msdb is corrupt
I have a user that corrupted msdb by trying to rebuild the indexes on the
backupfile table. I have removed the suspect flag so that the database is
available. And I have the scripts to completely rebuild msdb.
In the hopes of this problem being an allocation problem, I've tried
DBCC CHECKDB
DBCC CHECKALLOC
DBCC CHECKTABLE
DBCC REINDEX
all with the same result:
Server: Msg 823, Level 24, State 1, Line 1
I/O error (bad page ID) detected during read of BUF pointer = 0x1427de00,
page ptr = 0x448b0000, pageid = (0x1:0xf5f8), dbid = 4, status = 0x801, file
= E:\MSSQL7\DATA\msdbdata.mdf.
I also tried using bcp to get at the sysjobs table.
Besides restoring the database from a backup, which they don't have, is
there another way to get at the jobs and dts packages?
I'd say its stuffed - maybe next time they'll back it up!
"Jo" <Jo@.discussions.microsoft.com> wrote in message
news:610925D1-F51F-486B-A056-F54CF4F088C8@.microsoft.com...
> I have a user that corrupted msdb by trying to rebuild the indexes on the
> backupfile table. I have removed the suspect flag so that the database is
> available. And I have the scripts to completely rebuild msdb.
> In the hopes of this problem being an allocation problem, I've tried
> DBCC CHECKDB
> DBCC CHECKALLOC
> DBCC CHECKTABLE
> DBCC REINDEX
> all with the same result:
> Server: Msg 823, Level 24, State 1, Line 1
> I/O error (bad page ID) detected during read of BUF pointer = 0x1427de00,
> page ptr = 0x448b0000, pageid = (0x1:0xf5f8), dbid = 4, status = 0x801,
file
> = E:\MSSQL7\DATA\msdbdata.mdf.
> I also tried using bcp to get at the sysjobs table.
> Besides restoring the database from a backup, which they don't have, is
> there another way to get at the jobs and dts packages?
>
|||I tend to aggree. But before I give up, I was just trying to see if there was
a solution. I remember in 6.5, the contents of pages could be changed with a
dbcc command. I understand that there's huge differences between 6.5 and 7.0.
But since the database is basicly toast, I thought it would be worth a try.
"Mary Bray" wrote:
> I'd say its stuffed - maybe next time they'll back it up!
> "Jo" <Jo@.discussions.microsoft.com> wrote in message
> news:610925D1-F51F-486B-A056-F54CF4F088C8@.microsoft.com...
> file
>
>
backupfile table. I have removed the suspect flag so that the database is
available. And I have the scripts to completely rebuild msdb.
In the hopes of this problem being an allocation problem, I've tried
DBCC CHECKDB
DBCC CHECKALLOC
DBCC CHECKTABLE
DBCC REINDEX
all with the same result:
Server: Msg 823, Level 24, State 1, Line 1
I/O error (bad page ID) detected during read of BUF pointer = 0x1427de00,
page ptr = 0x448b0000, pageid = (0x1:0xf5f8), dbid = 4, status = 0x801, file
= E:\MSSQL7\DATA\msdbdata.mdf.
I also tried using bcp to get at the sysjobs table.
Besides restoring the database from a backup, which they don't have, is
there another way to get at the jobs and dts packages?
I'd say its stuffed - maybe next time they'll back it up!
"Jo" <Jo@.discussions.microsoft.com> wrote in message
news:610925D1-F51F-486B-A056-F54CF4F088C8@.microsoft.com...
> I have a user that corrupted msdb by trying to rebuild the indexes on the
> backupfile table. I have removed the suspect flag so that the database is
> available. And I have the scripts to completely rebuild msdb.
> In the hopes of this problem being an allocation problem, I've tried
> DBCC CHECKDB
> DBCC CHECKALLOC
> DBCC CHECKTABLE
> DBCC REINDEX
> all with the same result:
> Server: Msg 823, Level 24, State 1, Line 1
> I/O error (bad page ID) detected during read of BUF pointer = 0x1427de00,
> page ptr = 0x448b0000, pageid = (0x1:0xf5f8), dbid = 4, status = 0x801,
file
> = E:\MSSQL7\DATA\msdbdata.mdf.
> I also tried using bcp to get at the sysjobs table.
> Besides restoring the database from a backup, which they don't have, is
> there another way to get at the jobs and dts packages?
>
|||I tend to aggree. But before I give up, I was just trying to see if there was
a solution. I remember in 6.5, the contents of pages could be changed with a
dbcc command. I understand that there's huge differences between 6.5 and 7.0.
But since the database is basicly toast, I thought it would be worth a try.
"Mary Bray" wrote:
> I'd say its stuffed - maybe next time they'll back it up!
> "Jo" <Jo@.discussions.microsoft.com> wrote in message
> news:610925D1-F51F-486B-A056-F54CF4F088C8@.microsoft.com...
> file
>
>
MSDB in suspect mode.
Hi,
As the DB was in the suspect mode it didn't gave me scope to detach the DB. Now the DB is out of suspect mode after succesfully completing the 3rd step of your blog.
However the another issue I found while going through the script (in your blog), instmsdb.sql while going to create msdb database uses the same path of master db. while actual path in the sysdatabase for msdb database is different than master db.
I have mssql 2005 installed and i see that MSDB database is marked as suspect. I almost tried all the steps which are submitted in the forums.
1) I shut down the server, navigating to the directory 'd:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn' and doing the following: start sqlservr.exe -c -T3608
2) renamed the damaged msdb files (msdbdata.mdf and msdblog.ldf in the 'd:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data' directory)
3) Run the instmsdb.sql script in the 'd:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install' directory
--x
When I executed third step it returned me below error:
Msg 926, Level 14, State 1, Line 63
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
Please advice me.
It sounds like you didn't detach msdb - see my post at http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/06/619304.aspx for the complete sequence of operations.
Let us know how it goes.
|||Hi,As the DB was in the suspect mode it didn't gave me scope to detach the DB. Now the DB is out of suspect mode after succesfully completing the 3rd step of your blog.
However the another issue I found while going through the script (in your blog), instmsdb.sql while going to create msdb database uses the same path of master db. while actual path in the sysdatabase for msdb database is different than master db.
Also 3rd steps is completed succesfully but it doesn't create database anywhere due to this msdb is out of suspect mode but as it doesn't see physical file as per the path specified in sysdatabase it doesn't work and gives below error while accessing properties of any database:
Database 'msdb' cannot be opened due to inaccessible files or insufficient memory or disk space|||
I'm confused - you say msdb is out of suspect mode and then later you say that a new msdb wasn't created. Do you have a working msdb at this point?
[Edit] One thing I didn't ask is how did msdb get suspect in the first place? I take it you don't have a backup of msdb given that you're trying to rebuild it?
|||Hi,
The database came out of suspect mode after replacing the good one msdb. However when I fire the query select * from sysdatabases the path of master db and msdb differs. My concern was when we run the query for instmsdb.sql which recreates msdb. My concern is it doesn't create the msdb file. So wanted to know whether it creates file or just repairs the existing one.
This was actually one of client's system so we do not know how it went to suspect mode. Unfortunately we do not have backups for the same.
Now when I right click on DB it gives me following error:
Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "Danish_Norwegian_CI_AS" in the equal to operation. (Microsoft SQL Server, Error: 468)
MSDB in suspect mode.
Hi,
As the DB was in the suspect mode it didn't gave me scope to detach the DB. Now the DB is out of suspect mode after succesfully completing the 3rd step of your blog.
However the another issue I found while going through the script (in your blog), instmsdb.sql while going to create msdb database uses the same path of master db. while actual path in the sysdatabase for msdb database is different than master db.
I have mssql 2005 installed and i see that MSDB database is marked as suspect. I almost tried all the steps which are submitted in the forums.
1) I shut down the server, navigating to the directory 'd:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn' and doing the following: start sqlservr.exe -c -T3608
2) renamed the damaged msdb files (msdbdata.mdf and msdblog.ldf in the 'd:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data' directory)
3) Run the instmsdb.sql script in the 'd:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install' directory
--x
When I executed third step it returned me below error:
Msg 926, Level 14, State 1, Line 63
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
Please advice me.
It sounds like you didn't detach msdb - see my post at http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/06/619304.aspx for the complete sequence of operations.
Let us know how it goes.
|||Hi,As the DB was in the suspect mode it didn't gave me scope to detach the DB. Now the DB is out of suspect mode after succesfully completing the 3rd step of your blog.
However the another issue I found while going through the script (in your blog), instmsdb.sql while going to create msdb database uses the same path of master db. while actual path in the sysdatabase for msdb database is different than master db.
Also 3rd steps is completed succesfully but it doesn't create database anywhere due to this msdb is out of suspect mode but as it doesn't see physical file as per the path specified in sysdatabase it doesn't work and gives below error while accessing properties of any database:
Database 'msdb' cannot be opened due to inaccessible files or insufficient memory or disk space|||
I'm confused - you say msdb is out of suspect mode and then later you say that a new msdb wasn't created. Do you have a working msdb at this point?
[Edit] One thing I didn't ask is how did msdb get suspect in the first place? I take it you don't have a backup of msdb given that you're trying to rebuild it?
|||Hi,
The database came out of suspect mode after replacing the good one msdb. However when I fire the query select * from sysdatabases the path of master db and msdb differs. My concern was when we run the query for instmsdb.sql which recreates msdb. My concern is it doesn't create the msdb file. So wanted to know whether it creates file or just repairs the existing one.
This was actually one of client's system so we do not know how it went to suspect mode. Unfortunately we do not have backups for the same.
Now when I right click on DB it gives me following error:
Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "Danish_Norwegian_CI_AS" in the equal to operation. (Microsoft SQL Server, Error: 468)
MSDB Database SUSPECT - RESET PROCEDURE ?
I have a regional server running SQL2000 and Merge replication, the MSDB, NORTHWIND and 2 User DB's have been marked suspect. I cannot get into query analyzer etc to run the necessary scripts as it is all suspect.
Any ideas on how I can reset the status on the MSDB database??
Unfortunately there is no backup of either of the 2 system databases :(
** ANY ASSISTANCE WOULD BE GREATLY APPRECIATED **
JReset database with "suspect" status:
Do the following steps from the Query Analyzer:
1) Use Master
GO
EXEC sp_resetstatus <dbname>
2) Stop & Start the SQL Server
3) Run DBCC CHECKDB
4) Do the Full database backup (Master DB included)
If the above steps didn't resolve the problem, run the query below:
Use Master
GO
EXEC sp_configure 'allow updates', 1
GO
Reconfigure with override
GO
Do the step 1 ~ 4 above, then:
Use Master
GO
EXEC sp_configure 'allow updates', 0 -- to turn off
GO
Reconfigure with override
GO
NOTE: If the database become "suspect" because it ran out of disk space, you have to do the step #1 above, then use the "ALTER DATABASE ..." to add more data file (or log file), Stop & start the SQL Server and finish with step #3 & #4 as above.
Good luck.|||Valid reponse by SVT and make sure to have regular backups for SYSTEM Databases too in future.
Any ideas on how I can reset the status on the MSDB database??
Unfortunately there is no backup of either of the 2 system databases :(
** ANY ASSISTANCE WOULD BE GREATLY APPRECIATED **
JReset database with "suspect" status:
Do the following steps from the Query Analyzer:
1) Use Master
GO
EXEC sp_resetstatus <dbname>
2) Stop & Start the SQL Server
3) Run DBCC CHECKDB
4) Do the Full database backup (Master DB included)
If the above steps didn't resolve the problem, run the query below:
Use Master
GO
EXEC sp_configure 'allow updates', 1
GO
Reconfigure with override
GO
Do the step 1 ~ 4 above, then:
Use Master
GO
EXEC sp_configure 'allow updates', 0 -- to turn off
GO
Reconfigure with override
GO
NOTE: If the database become "suspect" because it ran out of disk space, you have to do the step #1 above, then use the "ALTER DATABASE ..." to add more data file (or log file), Stop & start the SQL Server and finish with step #3 & #4 as above.
Good luck.|||Valid reponse by SVT and make sure to have regular backups for SYSTEM Databases too in future.
msdb database marked as "suspect"
In my SQL server installation the msdb database has been marked "suspect"
and also the SQL agent cannot be started. Also I can not define any backups
in database management plans (there was on but now it is not working).
The rest database seems to work fine for more than 2 weeks now.
Any ideas?
Thanks"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl61o2$be0$1@.usenet.otenet.gr...
> In my SQL server installation the msdb database has been marked "suspect"
> and also the SQL agent cannot be started. Also I can not define any
backups
> in database management plans (there was on but now it is not working).
> The rest database seems to work fine for more than 2 weeks now.
> Any ideas?
> Thanks
>
Find out what is wrong with your msdb database. The SQL Server Agent uses
the msdb database to store jobs, maintenance plans, replication information
as well as alerts and operators.
Have you tried to restore the msdb from a valid backup?
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||I'd restore the last clean backup of msdb, quite simply.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message news:cl61o2$be0$1@.usenet.otene
t.gr...
> In my SQL server installation the msdb database has been marked "suspect"
> and also the SQL agent cannot be started. Also I can not define any backup
s
> in database management plans (there was on but now it is not working).
> The rest database seems to work fine for more than 2 weeks now.
> Any ideas?
> Thanks
>|||I don't have a backup of msdb.
I had only one maintenance plan that I can easily recreate it.
Thank you.
"Rick Sawtell" <r_sawtell@.hotmail.com>
news:e3r4qBstEHA.2808@.TK2MSFTNGP14.phx.gbl...
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
> news:cl61o2$be0$1@.usenet.otenet.gr...
"suspect"[vbcol=seagreen]
> backups
> Find out what is wrong with your msdb database. The SQL Server Agent uses
> the msdb database to store jobs, maintenance plans, replication
information
> as well as alerts and operators.
> Have you tried to restore the msdb from a valid backup?
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||I don't have a backup of msdb.
I had only one maintenance plan that I can easily recreate it.
Thank you.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I'd restore the last clean backup of msdb, quite simply.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl61o2$be0$1@.usenet.otenet.gr...
"suspect"[vbcol=seagreen]
backups[vbcol=seagreen]
>|||Search Google and KB for suitable phrases such as "rebuild" and "msdb", and
you should find articles
covering this. In general, you run instmsdb.sql to get a new fresh msdb data
base. But SQL Server
might not be so keen to let you do this without setting some trace flag etc,
hence my recommendation
to do a search first...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message news:cl64mf$nuh$1@.usenet.otene
t.gr...
>I don't have a backup of msdb.
> I had only one maintenance plan that I can easily recreate it.
> Thank you.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
> news:cl61o2$be0$1@.usenet.otenet.gr...
> "suspect"
> backups
>|||Thanks a lot
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
news:e0JjtTstEHA.2596@.TK2MSFTNGP10.phx.gbl...
> Search Google and KB for suitable phrases such as "rebuild" and "msdb",
and you should find articles
> covering this. In general, you run instmsdb.sql to get a new fresh msdb
database. But SQL Server
> might not be so keen to let you do this without setting some trace flag
etc, hence my recommendation
> to do a search first...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl64mf$nuh$1@.usenet.otenet.gr...
[vbcol=seagreen]
working).[vbcol=seagreen]
>
and also the SQL agent cannot be started. Also I can not define any backups
in database management plans (there was on but now it is not working).
The rest database seems to work fine for more than 2 weeks now.
Any ideas?
Thanks"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl61o2$be0$1@.usenet.otenet.gr...
> In my SQL server installation the msdb database has been marked "suspect"
> and also the SQL agent cannot be started. Also I can not define any
backups
> in database management plans (there was on but now it is not working).
> The rest database seems to work fine for more than 2 weeks now.
> Any ideas?
> Thanks
>
Find out what is wrong with your msdb database. The SQL Server Agent uses
the msdb database to store jobs, maintenance plans, replication information
as well as alerts and operators.
Have you tried to restore the msdb from a valid backup?
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||I'd restore the last clean backup of msdb, quite simply.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message news:cl61o2$be0$1@.usenet.otene
t.gr...
> In my SQL server installation the msdb database has been marked "suspect"
> and also the SQL agent cannot be started. Also I can not define any backup
s
> in database management plans (there was on but now it is not working).
> The rest database seems to work fine for more than 2 weeks now.
> Any ideas?
> Thanks
>|||I don't have a backup of msdb.
I had only one maintenance plan that I can easily recreate it.
Thank you.
"Rick Sawtell" <r_sawtell@.hotmail.com>
news:e3r4qBstEHA.2808@.TK2MSFTNGP14.phx.gbl...
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
> news:cl61o2$be0$1@.usenet.otenet.gr...
"suspect"[vbcol=seagreen]
> backups
> Find out what is wrong with your msdb database. The SQL Server Agent uses
> the msdb database to store jobs, maintenance plans, replication
information
> as well as alerts and operators.
> Have you tried to restore the msdb from a valid backup?
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||I don't have a backup of msdb.
I had only one maintenance plan that I can easily recreate it.
Thank you.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I'd restore the last clean backup of msdb, quite simply.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl61o2$be0$1@.usenet.otenet.gr...
"suspect"[vbcol=seagreen]
backups[vbcol=seagreen]
>|||Search Google and KB for suitable phrases such as "rebuild" and "msdb", and
you should find articles
covering this. In general, you run instmsdb.sql to get a new fresh msdb data
base. But SQL Server
might not be so keen to let you do this without setting some trace flag etc,
hence my recommendation
to do a search first...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message news:cl64mf$nuh$1@.usenet.otene
t.gr...
>I don't have a backup of msdb.
> I had only one maintenance plan that I can easily recreate it.
> Thank you.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
> news:cl61o2$be0$1@.usenet.otenet.gr...
> "suspect"
> backups
>|||Thanks a lot
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
news:e0JjtTstEHA.2596@.TK2MSFTNGP10.phx.gbl...
> Search Google and KB for suitable phrases such as "rebuild" and "msdb",
and you should find articles
> covering this. In general, you run instmsdb.sql to get a new fresh msdb
database. But SQL Server
> might not be so keen to let you do this without setting some trace flag
etc, hence my recommendation
> to do a search first...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl64mf$nuh$1@.usenet.otenet.gr...
[vbcol=seagreen]
working).[vbcol=seagreen]
>
msdb database marked as "suspect"
In my SQL server installation the msdb database has been marked "suspect"
and also the SQL agent cannot be started. Also I can not define any backups
in database management plans (there was on but now it is not working).
The rest database seems to work fine for more than 2 weeks now.
Any ideas?
Thanks
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl61o2$be0$1@.usenet.otenet.gr...
> In my SQL server installation the msdb database has been marked "suspect"
> and also the SQL agent cannot be started. Also I can not define any
backups
> in database management plans (there was on but now it is not working).
> The rest database seems to work fine for more than 2 weeks now.
> Any ideas?
> Thanks
>
Find out what is wrong with your msdb database. The SQL Server Agent uses
the msdb database to store jobs, maintenance plans, replication information
as well as alerts and operators.
Have you tried to restore the msdb from a valid backup?
HTH
Rick Sawtell
MCT, MCSD, MCDBA
|||I'd restore the last clean backup of msdb, quite simply.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message news:cl61o2$be0$1@.usenet.otenet.gr...
> In my SQL server installation the msdb database has been marked "suspect"
> and also the SQL agent cannot be started. Also I can not define any backups
> in database management plans (there was on but now it is not working).
> The rest database seems to work fine for more than 2 weeks now.
> Any ideas?
> Thanks
>
|||I don't have a backup of msdb.
I had only one maintenance plan that I can easily recreate it.
Thank you.
"Rick Sawtell" <r_sawtell@.hotmail.com>
news:e3r4qBstEHA.2808@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
> news:cl61o2$be0$1@.usenet.otenet.gr...
"suspect"
> backups
> Find out what is wrong with your msdb database. The SQL Server Agent uses
> the msdb database to store jobs, maintenance plans, replication
information
> as well as alerts and operators.
> Have you tried to restore the msdb from a valid backup?
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||I don't have a backup of msdb.
I had only one maintenance plan that I can easily recreate it.
Thank you.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I'd restore the last clean backup of msdb, quite simply.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl61o2$be0$1@.usenet.otenet.gr...[vbcol=seagreen]
"suspect"[vbcol=seagreen]
backups
>
|||Search Google and KB for suitable phrases such as "rebuild" and "msdb", and you should find articles
covering this. In general, you run instmsdb.sql to get a new fresh msdb database. But SQL Server
might not be so keen to let you do this without setting some trace flag etc, hence my recommendation
to do a search first...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message news:cl64mf$nuh$1@.usenet.otenet.gr...
>I don't have a backup of msdb.
> I had only one maintenance plan that I can easily recreate it.
> Thank you.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
> news:cl61o2$be0$1@.usenet.otenet.gr...
> "suspect"
> backups
>
|||Thanks a lot
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
news:e0JjtTstEHA.2596@.TK2MSFTNGP10.phx.gbl...
> Search Google and KB for suitable phrases such as "rebuild" and "msdb",
and you should find articles
> covering this. In general, you run instmsdb.sql to get a new fresh msdb
database. But SQL Server
> might not be so keen to let you do this without setting some trace flag
etc, hence my recommendation
> to do a search first...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl64mf$nuh$1@.usenet.otenet.gr...[vbcol=seagreen]
[vbcol=seagreen]
working).
>
and also the SQL agent cannot be started. Also I can not define any backups
in database management plans (there was on but now it is not working).
The rest database seems to work fine for more than 2 weeks now.
Any ideas?
Thanks
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl61o2$be0$1@.usenet.otenet.gr...
> In my SQL server installation the msdb database has been marked "suspect"
> and also the SQL agent cannot be started. Also I can not define any
backups
> in database management plans (there was on but now it is not working).
> The rest database seems to work fine for more than 2 weeks now.
> Any ideas?
> Thanks
>
Find out what is wrong with your msdb database. The SQL Server Agent uses
the msdb database to store jobs, maintenance plans, replication information
as well as alerts and operators.
Have you tried to restore the msdb from a valid backup?
HTH
Rick Sawtell
MCT, MCSD, MCDBA
|||I'd restore the last clean backup of msdb, quite simply.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message news:cl61o2$be0$1@.usenet.otenet.gr...
> In my SQL server installation the msdb database has been marked "suspect"
> and also the SQL agent cannot be started. Also I can not define any backups
> in database management plans (there was on but now it is not working).
> The rest database seems to work fine for more than 2 weeks now.
> Any ideas?
> Thanks
>
|||I don't have a backup of msdb.
I had only one maintenance plan that I can easily recreate it.
Thank you.
"Rick Sawtell" <r_sawtell@.hotmail.com>
news:e3r4qBstEHA.2808@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
> news:cl61o2$be0$1@.usenet.otenet.gr...
"suspect"
> backups
> Find out what is wrong with your msdb database. The SQL Server Agent uses
> the msdb database to store jobs, maintenance plans, replication
information
> as well as alerts and operators.
> Have you tried to restore the msdb from a valid backup?
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||I don't have a backup of msdb.
I had only one maintenance plan that I can easily recreate it.
Thank you.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I'd restore the last clean backup of msdb, quite simply.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl61o2$be0$1@.usenet.otenet.gr...[vbcol=seagreen]
"suspect"[vbcol=seagreen]
backups
>
|||Search Google and KB for suitable phrases such as "rebuild" and "msdb", and you should find articles
covering this. In general, you run instmsdb.sql to get a new fresh msdb database. But SQL Server
might not be so keen to let you do this without setting some trace flag etc, hence my recommendation
to do a search first...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message news:cl64mf$nuh$1@.usenet.otenet.gr...
>I don't have a backup of msdb.
> I had only one maintenance plan that I can easily recreate it.
> Thank you.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
> news:cl61o2$be0$1@.usenet.otenet.gr...
> "suspect"
> backups
>
|||Thanks a lot
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
news:e0JjtTstEHA.2596@.TK2MSFTNGP10.phx.gbl...
> Search Google and KB for suitable phrases such as "rebuild" and "msdb",
and you should find articles
> covering this. In general, you run instmsdb.sql to get a new fresh msdb
database. But SQL Server
> might not be so keen to let you do this without setting some trace flag
etc, hence my recommendation
> to do a search first...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl64mf$nuh$1@.usenet.otenet.gr...[vbcol=seagreen]
[vbcol=seagreen]
working).
>
msdb database marked as "suspect"
In my SQL server installation the msdb database has been marked "suspect"
and also the SQL agent cannot be started. Also I can not define any backups
in database management plans (there was on but now it is not working).
The rest database seems to work fine for more than 2 weeks now.
Any ideas?
Thanks"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl61o2$be0$1@.usenet.otenet.gr...
> In my SQL server installation the msdb database has been marked "suspect"
> and also the SQL agent cannot be started. Also I can not define any
backups
> in database management plans (there was on but now it is not working).
> The rest database seems to work fine for more than 2 weeks now.
> Any ideas?
> Thanks
>
Find out what is wrong with your msdb database. The SQL Server Agent uses
the msdb database to store jobs, maintenance plans, replication information
as well as alerts and operators.
Have you tried to restore the msdb from a valid backup?
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||I'd restore the last clean backup of msdb, quite simply.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message news:cl61o2$be0$1@.usenet.otenet.gr...
> In my SQL server installation the msdb database has been marked "suspect"
> and also the SQL agent cannot be started. Also I can not define any backups
> in database management plans (there was on but now it is not working).
> The rest database seems to work fine for more than 2 weeks now.
> Any ideas?
> Thanks
>|||I don't have a backup of msdb.
I had only one maintenance plan that I can easily recreate it.
Thank you.
Ï "Rick Sawtell" <r_sawtell@.hotmail.com> Ýãñáøå óôï ìÞíõìá
news:e3r4qBstEHA.2808@.TK2MSFTNGP14.phx.gbl...
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
> news:cl61o2$be0$1@.usenet.otenet.gr...
> > In my SQL server installation the msdb database has been marked
"suspect"
> > and also the SQL agent cannot be started. Also I can not define any
> backups
> > in database management plans (there was on but now it is not working).
> >
> > The rest database seems to work fine for more than 2 weeks now.
> >
> > Any ideas?
> >
> > Thanks
> >
> >
> Find out what is wrong with your msdb database. The SQL Server Agent uses
> the msdb database to store jobs, maintenance plans, replication
information
> as well as alerts and operators.
> Have you tried to restore the msdb from a valid backup?
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||I don't have a backup of msdb.
I had only one maintenance plan that I can easily recreate it.
Thank you.
Ï "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> Ýãñáøå
óôï ìÞíõìá news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I'd restore the last clean backup of msdb, quite simply.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl61o2$be0$1@.usenet.otenet.gr...
> > In my SQL server installation the msdb database has been marked
"suspect"
> > and also the SQL agent cannot be started. Also I can not define any
backups
> > in database management plans (there was on but now it is not working).
> >
> > The rest database seems to work fine for more than 2 weeks now.
> >
> > Any ideas?
> >
> > Thanks
> >
> >
>|||Search Google and KB for suitable phrases such as "rebuild" and "msdb", and you should find articles
covering this. In general, you run instmsdb.sql to get a new fresh msdb database. But SQL Server
might not be so keen to let you do this without setting some trace flag etc, hence my recommendation
to do a search first...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message news:cl64mf$nuh$1@.usenet.otenet.gr...
>I don't have a backup of msdb.
> I had only one maintenance plan that I can easily recreate it.
> Thank you.
> Ï "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> Ýãñáøå
> óôï ìÞíõìá news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
>> I'd restore the last clean backup of msdb, quite simply.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
> news:cl61o2$be0$1@.usenet.otenet.gr...
>> > In my SQL server installation the msdb database has been marked
> "suspect"
>> > and also the SQL agent cannot be started. Also I can not define any
> backups
>> > in database management plans (there was on but now it is not working).
>> >
>> > The rest database seems to work fine for more than 2 weeks now.
>> >
>> > Any ideas?
>> >
>> > Thanks
>> >
>> >
>>
>|||Thanks a lot
Ï "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> Ýãñáøå
óôï ìÞíõìá news:e0JjtTstEHA.2596@.TK2MSFTNGP10.phx.gbl...
> Search Google and KB for suitable phrases such as "rebuild" and "msdb",
and you should find articles
> covering this. In general, you run instmsdb.sql to get a new fresh msdb
database. But SQL Server
> might not be so keen to let you do this without setting some trace flag
etc, hence my recommendation
> to do a search first...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl64mf$nuh$1@.usenet.otenet.gr...
> >I don't have a backup of msdb.
> >
> > I had only one maintenance plan that I can easily recreate it.
> >
> > Thank you.
> >
> > Ï "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
Ýãñáøå
> > óôï ìÞíõìá news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
> >> I'd restore the last clean backup of msdb, quite simply.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
> > news:cl61o2$be0$1@.usenet.otenet.gr...
> >> > In my SQL server installation the msdb database has been marked
> > "suspect"
> >> > and also the SQL agent cannot be started. Also I can not define any
> > backups
> >> > in database management plans (there was on but now it is not
working).
> >> >
> >> > The rest database seems to work fine for more than 2 weeks now.
> >> >
> >> > Any ideas?
> >> >
> >> > Thanks
> >> >
> >> >
> >>
> >>
> >
> >
>
and also the SQL agent cannot be started. Also I can not define any backups
in database management plans (there was on but now it is not working).
The rest database seems to work fine for more than 2 weeks now.
Any ideas?
Thanks"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl61o2$be0$1@.usenet.otenet.gr...
> In my SQL server installation the msdb database has been marked "suspect"
> and also the SQL agent cannot be started. Also I can not define any
backups
> in database management plans (there was on but now it is not working).
> The rest database seems to work fine for more than 2 weeks now.
> Any ideas?
> Thanks
>
Find out what is wrong with your msdb database. The SQL Server Agent uses
the msdb database to store jobs, maintenance plans, replication information
as well as alerts and operators.
Have you tried to restore the msdb from a valid backup?
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||I'd restore the last clean backup of msdb, quite simply.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message news:cl61o2$be0$1@.usenet.otenet.gr...
> In my SQL server installation the msdb database has been marked "suspect"
> and also the SQL agent cannot be started. Also I can not define any backups
> in database management plans (there was on but now it is not working).
> The rest database seems to work fine for more than 2 weeks now.
> Any ideas?
> Thanks
>|||I don't have a backup of msdb.
I had only one maintenance plan that I can easily recreate it.
Thank you.
Ï "Rick Sawtell" <r_sawtell@.hotmail.com> Ýãñáøå óôï ìÞíõìá
news:e3r4qBstEHA.2808@.TK2MSFTNGP14.phx.gbl...
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
> news:cl61o2$be0$1@.usenet.otenet.gr...
> > In my SQL server installation the msdb database has been marked
"suspect"
> > and also the SQL agent cannot be started. Also I can not define any
> backups
> > in database management plans (there was on but now it is not working).
> >
> > The rest database seems to work fine for more than 2 weeks now.
> >
> > Any ideas?
> >
> > Thanks
> >
> >
> Find out what is wrong with your msdb database. The SQL Server Agent uses
> the msdb database to store jobs, maintenance plans, replication
information
> as well as alerts and operators.
> Have you tried to restore the msdb from a valid backup?
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||I don't have a backup of msdb.
I had only one maintenance plan that I can easily recreate it.
Thank you.
Ï "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> Ýãñáøå
óôï ìÞíõìá news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I'd restore the last clean backup of msdb, quite simply.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl61o2$be0$1@.usenet.otenet.gr...
> > In my SQL server installation the msdb database has been marked
"suspect"
> > and also the SQL agent cannot be started. Also I can not define any
backups
> > in database management plans (there was on but now it is not working).
> >
> > The rest database seems to work fine for more than 2 weeks now.
> >
> > Any ideas?
> >
> > Thanks
> >
> >
>|||Search Google and KB for suitable phrases such as "rebuild" and "msdb", and you should find articles
covering this. In general, you run instmsdb.sql to get a new fresh msdb database. But SQL Server
might not be so keen to let you do this without setting some trace flag etc, hence my recommendation
to do a search first...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message news:cl64mf$nuh$1@.usenet.otenet.gr...
>I don't have a backup of msdb.
> I had only one maintenance plan that I can easily recreate it.
> Thank you.
> Ï "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> Ýãñáøå
> óôï ìÞíõìá news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
>> I'd restore the last clean backup of msdb, quite simply.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
> news:cl61o2$be0$1@.usenet.otenet.gr...
>> > In my SQL server installation the msdb database has been marked
> "suspect"
>> > and also the SQL agent cannot be started. Also I can not define any
> backups
>> > in database management plans (there was on but now it is not working).
>> >
>> > The rest database seems to work fine for more than 2 weeks now.
>> >
>> > Any ideas?
>> >
>> > Thanks
>> >
>> >
>>
>|||Thanks a lot
Ï "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> Ýãñáøå
óôï ìÞíõìá news:e0JjtTstEHA.2596@.TK2MSFTNGP10.phx.gbl...
> Search Google and KB for suitable phrases such as "rebuild" and "msdb",
and you should find articles
> covering this. In general, you run instmsdb.sql to get a new fresh msdb
database. But SQL Server
> might not be so keen to let you do this without setting some trace flag
etc, hence my recommendation
> to do a search first...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
news:cl64mf$nuh$1@.usenet.otenet.gr...
> >I don't have a backup of msdb.
> >
> > I had only one maintenance plan that I can easily recreate it.
> >
> > Thank you.
> >
> > Ï "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
Ýãñáøå
> > óôï ìÞíõìá news:OklHrDstEHA.1292@.TK2MSFTNGP10.phx.gbl...
> >> I'd restore the last clean backup of msdb, quite simply.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "Trifon Triantafillidis" <trifont@.otenet.gr> wrote in message
> > news:cl61o2$be0$1@.usenet.otenet.gr...
> >> > In my SQL server installation the msdb database has been marked
> > "suspect"
> >> > and also the SQL agent cannot be started. Also I can not define any
> > backups
> >> > in database management plans (there was on but now it is not
working).
> >> >
> >> > The rest database seems to work fine for more than 2 weeks now.
> >> >
> >> > Any ideas?
> >> >
> >> > Thanks
> >> >
> >> >
> >>
> >>
> >
> >
>
Subscribe to:
Posts (Atom)