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

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

msdb corrupted in sql 2005 sp2, how to start with a new one?

Hi,
I get many errors about SSIS and SQL Agent.
msdb should be corrupted.
is there some way to start with a brand new msdb?
I'm going to
-install a new sql 2005 instance
-upgrade it with sp2
-copy the new msdb from the second instance to the first instance
is that correct?
ThanksI dont think reinstallation is necessary. Totally new msdb database can be
created by executing the script located at your install directory under path
Driveletter\Program files\Microsoft SQL Server\MSSQL\Install
File name is instmsdb.sql.
Lets see what experts recommend......
Manu
"Federico Caselli" wrote:

> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>|||How do you know msdb is corrupt? Is there any important information that you
may be losing by replacing msdb? What about a recent backup?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Federico Caselli" wrote:

> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>

msdb corrupted in sql 2005 sp2, how to start with a new one?

Hi,
I get many errors about SSIS and SQL Agent.
msdb should be corrupted.
is there some way to start with a brand new msdb?
I'm going to
-install a new sql 2005 instance
-upgrade it with sp2
-copy the new msdb from the second instance to the first instance
is that correct?
Thanks
I dont think reinstallation is necessary. Totally new msdb database can be
created by executing the script located at your install directory under path
Driveletter\Program files\Microsoft SQL Server\MSSQL\Install
File name is instmsdb.sql.
Lets see what experts recommend......
Manu
"Federico Caselli" wrote:

> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>
|||How do you know msdb is corrupt? Is there any important information that you
may be losing by replacing msdb? What about a recent backup?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Federico Caselli" wrote:

> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>

msdb corrupted in sql 2005 sp2, how to start with a new one?

Hi,
I get many errors about SSIS and SQL Agent.
msdb should be corrupted.
is there some way to start with a brand new msdb?
I'm going to
-install a new sql 2005 instance
-upgrade it with sp2
-copy the new msdb from the second instance to the first instance
is that correct?
ThanksI dont think reinstallation is necessary. Totally new msdb database can be
created by executing the script located at your install directory under path
Driveletter\Program files\Microsoft SQL Server\MSSQL\Install
File name is instmsdb.sql.
Lets see what experts recommend......
Manu
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>|||How do you know msdb is corrupt? Is there any important information that you
may be losing by replacing msdb? What about a recent backup?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Federico Caselli" wrote:
> Hi,
> I get many errors about SSIS and SQL Agent.
> msdb should be corrupted.
> is there some way to start with a brand new msdb?
> I'm going to
> -install a new sql 2005 instance
> -upgrade it with sp2
> -copy the new msdb from the second instance to the first instance
> is that correct?
> Thanks
>