Backup to Network Drive: detected

Showing posts with label detected. Show all posts

Monday, March 19, 2012

bad page ID in MSDB DB

Hi All,
Greeting,

Sql Server 7
OS: Win NT

In the sql server logs i see the below error alerts

I/O error (bad page ID) detected during read of BUF pointer = 0x11e09e80, page ptr = 0x446b4000, pageid = (0x1:0x2c78), dbid = 4, status = 0x801, file = F:\MSSQL7\DATA\msdbdata.mdf..

Error: 823, Severity: 24, State: 1

Please help me in this.

Thanks in Advance
AdilHere's one place to look: http://support.microsoft.com/kb/q281809/

bad page ID

How i can repair database ms-sql when attach file i have:
error 823 I/O error (bad page ID) detected during read at offset 0x itd...
Robert LisHi

If you are trying to attach a DB, and during the attach process you get this
error, you can't do much but to revert to a backup as you can't attach a DB
that SQL Server finds to be suspect.

On the other hand, if the DB is online, then you can run DBCC CHECKDB.

--
----------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@.epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"Robert-SoftMAR" <robert@.softmar.com.pl> wrote in message
news:d6qu0d$ude$1@.news.lublin.pl...
> How i can repair database ms-sql when attach file i have:
> error 823 I/O error (bad page ID) detected during read at offset 0x itd...
> Robert Lis|||Robert-SoftMAR (robert@.softmar.com.pl) writes:
> How i can repair database ms-sql when attach file i have:
> error 823 I/O error (bad page ID) detected during read at offset 0x itd...

Books Online says this about eror 823:

Check the accessibility and condition of the device in question.

Run hardware diagnostics and correct problems, if possible.

Restore damaged files from the latest database backup. Restoring from a
database backup should always be considered the primary means of fixing
a damaged database.

If you don't have a backup or if the errors detected are very isolated,
the repair functionality of DBCC CHECKDB may be useful. However, using
DBCC CHECKDB can be more time consuming than restoring the damaged
files from a backup, and you may not be able to recover all your data.

Caution If running DBCC CHECKDB with one of the repair clauses does
not correct the problem or if you are unsure how this process may
affect your data, contact your primary support provider.

The way to find this information is simply to search for 823.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks
If I tray DBCC CHECKDB, I have error:
Server: Msg 911, Level 16, State 1, Line 1
Could not locate entry in sysdatabases for database 'gg_system'. No entry
found with that name. Make sure that the name is entered correctly.
This DB is not in list sysdatabases and I can't add this DB. And I don't
have any backup of DB. Maybe another repair software?
Robert Lis

Uytkownik "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> napisa w
wiadomoci news:4290ff5e$1_3@.news.bluewin.ch...
> Hi
> If you are trying to attach a DB, and during the attach process you get
> this error, you can't do much but to revert to a backup as you can't
> attach a DB that SQL Server finds to be suspect.
> On the other hand, if the DB is online, then you can run DBCC CHECKDB.
> --
> ----------
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Robert-SoftMAR" <robert@.softmar.com.pl> wrote in message
> news:d6qu0d$ude$1@.news.lublin.pl...
>> How i can repair database ms-sql when attach file i have:
>> error 823 I/O error (bad page ID) detected during read at offset 0x
>> itd...
>> Robert Lis
>>|||"Robert-SoftMAR" <robert@.softmar.com.pl> wrote in message
news:d6r1oa$1vb$1@.news.lublin.pl...
> Thanks
> If I tray DBCC CHECKDB, I have error:
> Server: Msg 911, Level 16, State 1, Line 1
> Could not locate entry in sysdatabases for database 'gg_system'. No entry
> found with that name. Make sure that the name is entered correctly.
> This DB is not in list sysdatabases and I can't add this DB. And I don't
> have any backup of DB. Maybe another repair software?

Sounds like you're pretty much up a creek w/o a paddle then.

I don't know of any tools that can read/repair off-line files for SQL
Server.|||Yes, I now this massage in Books Online but i can't do:
DBCC CHECKDB
beacouse i have error:
Could not locate entry in sysdatabases for database 'gg_system'. No entry
found with that name. Make sure that the name is entered correctly.
Robert Lis

Uzytkownik "Erland Sommarskog" <esquel@.sommarskog.se> napisal w wiadomosci
news:Xns965F261413F3Yazorman@.127.0.0.1...
> Robert-SoftMAR (robert@.softmar.com.pl) writes:
>> How i can repair database ms-sql when attach file i have:
>> error 823 I/O error (bad page ID) detected during read at offset 0x
>> itd...
> Books Online says this about eror 823:
> Check the accessibility and condition of the device in question.
> Run hardware diagnostics and correct problems, if possible.
> Restore damaged files from the latest database backup. Restoring from a
> database backup should always be considered the primary means of fixing
> a damaged database.
> If you don't have a backup or if the errors detected are very isolated,
> the repair functionality of DBCC CHECKDB may be useful. However, using
> DBCC CHECKDB can be more time consuming than restoring the damaged
> files from a backup, and you may not be able to recover all your data.
>
> Caution If running DBCC CHECKDB with one of the repair clauses does
> not correct the problem or if you are unsure how this process may
> affect your data, contact your primary support provider.
>
> The way to find this information is simply to search for 823.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||Robert-SoftMAR (robert@.softmar.com.pl) writes:
> Yes, I now this massage in Books Online but i can't do:
> DBCC CHECKDB
> beacouse i have error:
> Could not locate entry in sysdatabases for database 'gg_system'. No entry
> found with that name. Make sure that the name is entered correctly.
> Robert Lis

It appears that that .mdf files is a useless pile of bits. If that database
is important to you, by all means open a case with Microsoft. This is
nothing that can be sorted out over a newsgroup.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Bad Page error

I am getting an error in my DTS logs about a bad page. Here is the exact
message.
Step Error Description:I/O error (bad page ID) detected during read at
offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
We are getting this error on 2 different servers. The process has been
running like a champ for years and now we are getting this message. All that
is running when it errors out is an update statement that is joining 2
tables. I have read some about tempdb running into these issues and it
suggests that there may be hardware issues. That is not the case as we have
looked into that and we have many other processes that run on these servers.
I have also read that service pack 4 needs to be installed. Well we moved
our process to another server with exactly the same configuration and it ran
fine on there. Had anybody else ran into this? Any suggestions? All help
is appreciated.
Thankshave you run DBCC CHECKDB to see if there are any errors?
--
Jack Vamvas
__________________________________________________________________
Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
New article by Jack Vamvas - SQL and Markov Chains -
www.ciquery.com/articles/art_04.asp
"Andy" <Andy@.discussions.microsoft.com> wrote in message
news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> I am getting an error in my DTS logs about a bad page. Here is the exact
> message.
> Step Error Description:I/O error (bad page ID) detected during read at
> offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> We are getting this error on 2 different servers. The process has been
> running like a champ for years and now we are getting this message. All
that
> is running when it errors out is an update statement that is joining 2
> tables. I have read some about tempdb running into these issues and it
> suggests that there may be hardware issues. That is not the case as we
have
> looked into that and we have many other processes that run on these
servers.
> I have also read that service pack 4 needs to be installed. Well we moved
> our process to another server with exactly the same configuration and it
ran
> fine on there. Had anybody else ran into this? Any suggestions? All
help
> is appreciated.
> Thanks|||Yes, we ran that and no errors were returned. We also ran it with Allow data
loss and no errors were returned. Like I mentioned below, this is happening
on 2 servers. It is the same process, but 1 is the dev server and 1 is prod.
"Jack Vamvas" wrote:
> have you run DBCC CHECKDB to see if there are any errors?
> --
> Jack Vamvas
> __________________________________________________________________
> Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
> SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> New article by Jack Vamvas - SQL and Markov Chains -
> www.ciquery.com/articles/art_04.asp
> "Andy" <Andy@.discussions.microsoft.com> wrote in message
> news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> > I am getting an error in my DTS logs about a bad page. Here is the exact
> > message.
> >
> > Step Error Description:I/O error (bad page ID) detected during read at
> > offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> >
> > We are getting this error on 2 different servers. The process has been
> > running like a champ for years and now we are getting this message. All
> that
> > is running when it errors out is an update statement that is joining 2
> > tables. I have read some about tempdb running into these issues and it
> > suggests that there may be hardware issues. That is not the case as we
> have
> > looked into that and we have many other processes that run on these
> servers.
> > I have also read that service pack 4 needs to be installed. Well we moved
> > our process to another server with exactly the same configuration and it
> ran
> > fine on there. Had anybody else ran into this? Any suggestions? All
> help
> > is appreciated.
> >
> > Thanks
>
>|||Hi Andy,
This is usually caused by the hardware, but if it is happening on two
different hardware systems, it seems like a logical problem in the database.
You probably restored a backup of the database from server to another.
Here is the logical meaning of this error:
http://support.microsoft.com/default.aspx?scid=kb;en-us;828339
HTH
DeeJay Puar
MCDBA
(bad page ID): This message means that the pageID on the page header is not
the expected page that was read from the disk. For example, if SQL Server
2000 provides a file offset for database file 1 that is for logical page 100,
the pageID on the page header for that 8 KB page should be 1:100. If not, the
bad page ID is included in the logical I/O check failure message.
You can read more about it here:
"Andy" wrote:
> Yes, we ran that and no errors were returned. We also ran it with Allow data
> loss and no errors were returned. Like I mentioned below, this is happening
> on 2 servers. It is the same process, but 1 is the dev server and 1 is prod.
>
> "Jack Vamvas" wrote:
> > have you run DBCC CHECKDB to see if there are any errors?
> >
> > --
> > Jack Vamvas
> > __________________________________________________________________
> > Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
> > SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> > New article by Jack Vamvas - SQL and Markov Chains -
> > www.ciquery.com/articles/art_04.asp
> > "Andy" <Andy@.discussions.microsoft.com> wrote in message
> > news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> > > I am getting an error in my DTS logs about a bad page. Here is the exact
> > > message.
> > >
> > > Step Error Description:I/O error (bad page ID) detected during read at
> > > offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> > >
> > > We are getting this error on 2 different servers. The process has been
> > > running like a champ for years and now we are getting this message. All
> > that
> > > is running when it errors out is an update statement that is joining 2
> > > tables. I have read some about tempdb running into these issues and it
> > > suggests that there may be hardware issues. That is not the case as we
> > have
> > > looked into that and we have many other processes that run on these
> > servers.
> > > I have also read that service pack 4 needs to be installed. Well we moved
> > > our process to another server with exactly the same configuration and it
> > ran
> > > fine on there. Had anybody else ran into this? Any suggestions? All
> > help
> > > is appreciated.
> > >
> > > Thanks
> >
> >
> >|||I looked into that as well, as I thought I did take a backup. The 2nd server
that it is happening on I created brand new databases before I kicked off the
process and we received the same error, at the same point in the process.
"DeeJay Puar" wrote:
> Hi Andy,
> This is usually caused by the hardware, but if it is happening on two
> different hardware systems, it seems like a logical problem in the database.
> You probably restored a backup of the database from server to another.
> Here is the logical meaning of this error:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;828339
> HTH
> DeeJay Puar
> MCDBA
> (bad page ID): This message means that the pageID on the page header is not
> the expected page that was read from the disk. For example, if SQL Server
> 2000 provides a file offset for database file 1 that is for logical page 100,
> the pageID on the page header for that 8 KB page should be 1:100. If not, the
> bad page ID is included in the logical I/O check failure message.
> You can read more about it here:
>
> "Andy" wrote:
> > Yes, we ran that and no errors were returned. We also ran it with Allow data
> > loss and no errors were returned. Like I mentioned below, this is happening
> > on 2 servers. It is the same process, but 1 is the dev server and 1 is prod.
> >
> >
> > "Jack Vamvas" wrote:
> >
> > > have you run DBCC CHECKDB to see if there are any errors?
> > >
> > > --
> > > Jack Vamvas
> > > __________________________________________________________________
> > > Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
> > > SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> > > New article by Jack Vamvas - SQL and Markov Chains -
> > > www.ciquery.com/articles/art_04.asp
> > > "Andy" <Andy@.discussions.microsoft.com> wrote in message
> > > news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> > > > I am getting an error in my DTS logs about a bad page. Here is the exact
> > > > message.
> > > >
> > > > Step Error Description:I/O error (bad page ID) detected during read at
> > > > offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> > > >
> > > > We are getting this error on 2 different servers. The process has been
> > > > running like a champ for years and now we are getting this message. All
> > > that
> > > > is running when it errors out is an update statement that is joining 2
> > > > tables. I have read some about tempdb running into these issues and it
> > > > suggests that there may be hardware issues. That is not the case as we
> > > have
> > > > looked into that and we have many other processes that run on these
> > > servers.
> > > > I have also read that service pack 4 needs to be installed. Well we moved
> > > > our process to another server with exactly the same configuration and it
> > > ran
> > > > fine on there. Had anybody else ran into this? Any suggestions? All
> > > help
> > > > is appreciated.
> > > >
> > > > Thanks
> > >
> > >
> > >|||No too sure as to what is happening. I can not really duplicate it here.
On the server, did you take a backup from the old server and restore the
database on the new server? Or did you just create a shell and then ran your
dts package to load the data? Have you looked at the source tables in the DTS
package?
Have you looked into torn-page?
"Andy" wrote:
> I looked into that as well, as I thought I did take a backup. The 2nd server
> that it is happening on I created brand new databases before I kicked off the
> process and we received the same error, at the same point in the process.
> "DeeJay Puar" wrote:
> > Hi Andy,
> >
> > This is usually caused by the hardware, but if it is happening on two
> > different hardware systems, it seems like a logical problem in the database.
> > You probably restored a backup of the database from server to another.
> >
> > Here is the logical meaning of this error:
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;828339
> >
> > HTH
> >
> > DeeJay Puar
> > MCDBA
> >
> > (bad page ID): This message means that the pageID on the page header is not
> > the expected page that was read from the disk. For example, if SQL Server
> > 2000 provides a file offset for database file 1 that is for logical page 100,
> > the pageID on the page header for that 8 KB page should be 1:100. If not, the
> > bad page ID is included in the logical I/O check failure message.
> >
> > You can read more about it here:
> >
> >
> >
> > "Andy" wrote:
> >
> > > Yes, we ran that and no errors were returned. We also ran it with Allow data
> > > loss and no errors were returned. Like I mentioned below, this is happening
> > > on 2 servers. It is the same process, but 1 is the dev server and 1 is prod.
> > >
> > >
> > > "Jack Vamvas" wrote:
> > >
> > > > have you run DBCC CHECKDB to see if there are any errors?
> > > >
> > > > --
> > > > Jack Vamvas
> > > > __________________________________________________________________
> > > > Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
> > > > SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> > > > New article by Jack Vamvas - SQL and Markov Chains -
> > > > www.ciquery.com/articles/art_04.asp
> > > > "Andy" <Andy@.discussions.microsoft.com> wrote in message
> > > > news:AA513080-F72F-4386-93CA-93CEF0673F76@.microsoft.com...
> > > > > I am getting an error in my DTS logs about a bad page. Here is the exact
> > > > > message.
> > > > >
> > > > > Step Error Description:I/O error (bad page ID) detected during read at
> > > > > offset 0x0000022a040000 in file 'E:\SQLData\ALS_Stage_Data.MDF'.
> > > > >
> > > > > We are getting this error on 2 different servers. The process has been
> > > > > running like a champ for years and now we are getting this message. All
> > > > that
> > > > > is running when it errors out is an update statement that is joining 2
> > > > > tables. I have read some about tempdb running into these issues and it
> > > > > suggests that there may be hardware issues. That is not the case as we
> > > > have
> > > > > looked into that and we have many other processes that run on these
> > > > servers.
> > > > > I have also read that service pack 4 needs to be installed. Well we moved
> > > > > our process to another server with exactly the same configuration and it
> > > > ran
> > > > > fine on there. Had anybody else ran into this? Any suggestions? All
> > > > help
> > > > > is appreciated.
> > > > >
> > > > > Thanks
> > > >
> > > >
> > > >

Monday, March 19, 2012

bad page ID in MSDB DB

bad page ID

Bad Page error

Bad Page error

Bad Page error

Backup to Network Drive

Blog Archive

About Me