Saturday, February 25, 2012

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
>>
>>
>

No comments:

Post a Comment