Error 845 running backup of one database

I have one database that I keep getting an error 845: Time out ocurred while
waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
569352192, Index ID 0..
This only started happening last week. The database has not changed (other
than normal data entry) in over a year. Does anyone have any ideas of what
should be checked?
Thanks in advanceDid you see the specific recommendations in Books Online for this?
Error 845
Severity Level 17
Message Text
Time-out occurred while waiting for buffer latch type %d for page %S_PGID, d
atabase ID %d.
Explanation
When under a heavy stress load or high I/O conditions, your system may produ
ce this message.
Action
This message can usually be ignored; however, if you receive repeated messag
es where the wait time
increases, it may indicate an internal server problem. Contact your system a
dministrator. The system
administrator should check the waittype, waittime, lastwaittype, and the wai
tresource columns of
sysprocesses to see what activities each SPIDs is performing.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Connie" <cfelt@.ga.wa.gov> wrote in message news:OcwIz0TWEHA.1144@.TK2MSFTNGP10.phx.gbl...[vb
col=seagreen]
> I have one database that I keep getting an error 845: Time out ocurred whi
le
> waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
> 569352192, Index ID 0..
> This only started happening last week. The database has not changed (othe
r
> than normal data entry) in over a year. Does anyone have any ideas of wha
t
> should be checked?
> Thanks in advance
>[/vbcol]

Error 845 running backup of one database

I have one database that I keep getting an error 845: Time out ocurred while
waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
569352192, Index ID 0..
This only started happening last week. The database has not changed (other
than normal data entry) in over a year. Does anyone have any ideas of what
should be checked?
Thanks in advance
Did you see the specific recommendations in Books Online for this?
Error 845
Severity Level 17
Message Text
Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
Explanation
When under a heavy stress load or high I/O conditions, your system may produce this message.
Action
This message can usually be ignored; however, if you receive repeated messages where the wait time
increases, it may indicate an internal server problem. Contact your system administrator. The system
administrator should check the waittype, waittime, lastwaittype, and the waitresource columns of
sysprocesses to see what activities each SPIDs is performing.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Connie" <cfelt@.ga.wa.gov> wrote in message news:OcwIz0TWEHA.1144@.TK2MSFTNGP10.phx.gbl...
> I have one database that I keep getting an error 845: Time out ocurred while
> waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
> 569352192, Index ID 0..
> This only started happening last week. The database has not changed (other
> than normal data entry) in over a year. Does anyone have any ideas of what
> should be checked?
> Thanks in advance
>
sql

Error 845 running backup of one database

I have one database that I keep getting an error 845: Time out ocurred while
waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
569352192, Index ID 0..
This only started happening last week. The database has not changed (other
than normal data entry) in over a year. Does anyone have any ideas of what
should be checked?
Thanks in advanceDid you see the specific recommendations in Books Online for this?
Error 845
Severity Level 17
Message Text
Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
Explanation
When under a heavy stress load or high I/O conditions, your system may produce this message.
Action
This message can usually be ignored; however, if you receive repeated messages where the wait time
increases, it may indicate an internal server problem. Contact your system administrator. The system
administrator should check the waittype, waittime, lastwaittype, and the waitresource columns of
sysprocesses to see what activities each SPIDs is performing.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Connie" <cfelt@.ga.wa.gov> wrote in message news:OcwIz0TWEHA.1144@.TK2MSFTNGP10.phx.gbl...
> I have one database that I keep getting an error 845: Time out ocurred while
> waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
> 569352192, Index ID 0..
> This only started happening last week. The database has not changed (other
> than normal data entry) in over a year. Does anyone have any ideas of what
> should be checked?
> Thanks in advance
>

Error 823: I/O error (torn page) detected during read at offset...

Hi,
HDD failure caused to move the data to a new disk. We are no longer able to
attach the MDF file. I searched a lot but all of solutions work only when
the database is running under SQL Server and is suspected, not for me
(detached database).
I get this error when trying to attach the MDF file:
Error 823: I/O error (torn page) detected during read at offset
(0x0000036cba0000 in file 'D:\Data\Data_file)
Unfortunately the backup is 2 hours behind from the failure!
Any help would be greatly appreciated.
LeilaLeila (Leilas@.hotpop.com) writes:
> Date: Sun, 23 Apr 2006 20:49:51 +0430
Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.

> HDD failure caused to move the data to a new disk. We are no longer able
> to attach the MDF file. I searched a lot but all of solutions work only
> when the database is running under SQL Server and is suspected, not for
> me (detached database).
> I get this error when trying to attach the MDF file:
> Error 823: I/O error (torn page) detected during read at offset
> (0x0000036cba0000 in file 'D:\Data\Data_file)
> Unfortunately the backup is 2 hours behind from the failure!
> Any help would be greatly appreciated.
Well, at least there is a backup!
I have no idea how to handle the situation, and the only advice would
be to open a case with Microsoft, but I realise that this may not be
easy where you are located.
I'll inquire with Microsoft, but I would have too much hope.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||> Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.
I really don't know what's wrong with my clock :-(

> I'll inquire with Microsoft, but I would have too much hope.
Thanks indeed!
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns97AE9408A75F1Yazorman@.127.0.0.1...
> Leila (Leilas@.hotpop.com) writes:
> Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.
>
> Well, at least there is a backup!
> I have no idea how to handle the situation, and the only advice would
> be to open a case with Microsoft, but I realise that this may not be
> easy where you are located.
> I'll inquire with Microsoft, but I would have too much hope.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||Leila (Leilas@.hotpop.com) writes:
> I really don't know what's wrong with my clock :-(
As we say up here "Time goes fast, when you're having fun!". :-)
[vbcol=seagreen]
One suggestion I got from a fellow MVP was:
How about stopping SS, renaming the corrupted database files, starting
SS, create new database with same filenames as corrupted db had
originally, stopping SS, removing new database files and then renaming
corrupted db backup to the original names? SQL Server will possibly
recover the database fine...
If I were to do this operation, I would make sure that I have a copy of
the bad database files, to keep a starting point.
I'm a little skeptic that the above actually works. I guess that whar
you are really after is the transaction log, so you can back it up, and
apply it to the backup, so you don't lose those two hours of work.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Leila,
If you can read Russian, or fill in the gaps with
some online translation, this might help:
http://www.sql.ru/faq/faq_topic.aspx?fid=123
Steve Kass
Drew University
Leila wrote:

>I really don't know what's wrong with my clock :-(
>
>
>Thanks indeed!
>
>
>"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
>news:Xns97AE9408A75F1Yazorman@.127.0.0.1...
>
>
>|||> As we say up here "Time goes fast, when you're having fun!". :-)
lol! We say exactly the same thing here! But it seems my notebook is having
fun, not me!

> How about stopping SS, renaming the corrupted database files, starting...
oops! Really tricky! I must try it...
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns97AECB33EE3F0Yazorman@.127.0.0.1...
> Leila (Leilas@.hotpop.com) writes:
> As we say up here "Time goes fast, when you're having fun!". :-)
>
> One suggestion I got from a fellow MVP was:
> How about stopping SS, renaming the corrupted database files, starting
> SS, create new database with same filenames as corrupted db had
> originally, stopping SS, removing new database files and then renaming
> corrupted db backup to the original names? SQL Server will possibly
> recover the database fine...
> If I were to do this operation, I would make sure that I have a copy of
> the bad database files, to keep a starting point.
> I'm a little skeptic that the above actually works. I guess that whar
> you are really after is the transaction log, so you can back it up, and
> apply it to the backup, so you don't lose those two hours of work.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||Thanks Steve!
Unfortunately I cannot read Russian but the TSQL seems that you must at
least
have your database attached to SQL Server before using that instruction?
"Steve Kass" <skass@.drew.edu> wrote in message
news:%23dKWuUwZGHA.3532@.TK2MSFTNGP05.phx.gbl...[vbcol=seagreen]
> Leila,
> If you can read Russian, or fill in the gaps with
> some online translation, this might help:
> http://www.sql.ru/faq/faq_topic.aspx?fid=123
> Steve Kass
> Drew University
> Leila wrote:
>|||Leila (Leilas@.hotpop.com) writes:
> Unfortunately I cannot read Russian but the TSQL seems that you must at
> least
> have your database attached to SQL Server before using that instruction?
Which can be solved by creating a database, and the throwing the files
for that away, and then slapping the files for the broken database in
place.
However, I doubt that this is the solution to your problem. That script
seems to create an empty log file, and if I understand correctly, the
log file is what you want to be able to access?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Leila (Leilas@.hotpop.com) writes:
> HDD failure caused to move the data to a new disk. We are no longer able
> to attach the MDF file. I searched a lot but all of solutions work only
> when the database is running under SQL Server and is suspected, not for
> me (detached database). I get this error when trying to attach the MDF
> file: Error 823: I/O error (torn page) detected during read at offset
> (0x0000036cba0000 in file 'D:\Data\Data_file)
> Unfortunately the backup is 2 hours behind from the failure!
> Any help would be greatly appreciated.
I guess that you by now already have restored that two-hour old backup.
Unfortunately, it took some time to find out the correct procedure.
It is described on
http://www.sqljunkies.com/HowTo/F5B...8DDB08B0C1.scuk
With quite some help of some MVP colleagues I developed the demo script
below, to illustrate the procedure.
It assumes that you know the name and location of your log files, but
with a full backup available, it should not be difficult to work out.
-- See also
-- http://www.sqljunkies.com/HowTo/F5B...8DDB08B0C1.scuk
-- First take a copy of Northwind that we can mess up a bit.
BACKUP DATABASE Northwind to disk = 'c:\temp\Northwind.bak'
go
RESTORE DATABASE northbreeze from disk = 'c:\temp\Northwind.bak'
WITH MOVE 'Northwind' TO 'C:\temp\northbreeze.mdf',
MOVE 'Northwind_log' TO 'C:\temp\northbreeze.ldf',
REPLACE
go
-- And make sure that it has full recovery.
ALTER DATABASE northbreeze SET RECOVERY FULL
go
USE northbreeze
go
-- Let's add a new customer to northbreeze.
INSERT Customers (CustomerID, CompanyName, ContactName,
ContactTitle, Address, City, Region, PostalCode,
Country, Phone, Fax)
VALUES ('GARBO', 'Greta Garbos Deliktatesshandel', 'Frk. Gustafsson',
'Frken', 'Mosebacke Torg 12', 'Stockholm', NULL, '11223',
'Sweden', '+46-8-90510', NULL)
go
-- Make sure that this database is backed up on its own. Backup the log
-- as well.
BACKUP DATABASE northbreeze to disk = 'c:\temp\Northbreeze.bak'
BACKUP LOG northbreeze to disk = 'c:\temp\Northbreeze.logbak'
go
-- Perform further updates in the database.
DELETE Customers
FROM Customers C
WHERE NOT EXISTS (SELECT *
FROM Orders O
WHERE O.CustomerID = C.CustomerID)
AND C.CustomerID <> 'GARBO'
go
-- Go to master
USE master
go
-- And detach database
EXEC sp_detach_db northbreeze
go
-- Assume that something bad happens to the MDF file while it is detached.
-- First step is to rename the files. (Although we could toss the bsd MDF
-- file.)
EXEC xp_cmdshell 'MOVE c:\temp\northbreeze.mdf c:\temp\northbreeze-
crashed.mdf'
EXEC xp_cmdshell 'MOVE c:\temp\northbreeze.ldf c:\temp\northbreeze-
crashed.ldf'
go
-- Create a new empty database were we want the real thing to be. Make sure
-- that we have full recovery-
CREATE DATABASE northbreeze
ON (NAME = 'Northwind', FILENAME = 'C:\temp\northbreeze.mdf')
LOG ON (NAME = 'Northwind.log', FILENAME = 'C:\temp\northbreeze.ldf')
ALTER DATABASE northbreeze SET RECOVERY FULL
go
-- Shut down SQL Server.
SHUTDOWN
go
-- In file system do this:
-- 1) move northbreeze.mdf to northbreeze-dummy.mdf (or delete it)
-- 1) move northbreeze.ldf to northbreeze-dummy.ldf (or delete it)
-- 2) move northbreeze-crashed.ldf to northbreeze.ldf
-- Start server again
go
-- The northbreeze database does at this point consist of the log file only!
-- (Or SQL Server created a new MDF; I did not check.)
-- We can now back up the tail of the log. Note NO_TRUNCATE!
BACKUP LOG northbreeze TO DISK = 'C:\temp\northbreeze-tail.logbak'
WITH NO_TRUNCATE
go
-- Drop the database
DROP DATABASE northbreeze
go
-- The log file may still be there, just move it out of the way.
EXEC xp_cmdshell
'MOVE c:\temp\northbreeze.ldf c:\temp\northbreeze-crashed.ldf'
go
-- Restore the database, use no NORECOVER, as we will apply logs as well.
RESTORE DATABASE northbreeze from disk = 'c:\temp\Northbreeze.bak'
WITH NORECOVERY
-- Restore the fist log dump.
RESTORE LOG northbreeze from disk = 'C:\temp\northbreeze.logbak'
WITH NORECOVERY
-- Apply the tail log.
RESTORE LOG northbreeze from disk = 'C:\temp\northbreeze-tail.logbak'
go
-- Verify that northbreeze != Northwind.
SELECT a.CustomerID, b.CustomerID
FROM Northwind..Customers a
FULL JOIN northbreeze..Customers b ON a.CustomerID = b.CustomerID
WHERE a.CustomerID IS NULL OR
b.CustomerID IS NULL
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Error 823: I/O error (torn page) detected during read at offset...

Hi,
HDD failure caused to move the data to a new disk. We are no longer able to
attach the MDF file. I searched a lot but all of solutions work only when
the database is running under SQL Server and is suspected, not for me
(detached database).
I get this error when trying to attach the MDF file:
Error 823: I/O error (torn page) detected during read at offset
(0x0000036cba0000 in file 'D:\Data\Data_file)
Unfortunately the backup is 2 hours behind from the failure!
Any help would be greatly appreciated.
LeilaLeila (Leilas@.hotpop.com) writes:
> Date: Sun, 23 Apr 2006 20:49:51 +0430
Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.

> HDD failure caused to move the data to a new disk. We are no longer able
> to attach the MDF file. I searched a lot but all of solutions work only
> when the database is running under SQL Server and is suspected, not for
> me (detached database).
> I get this error when trying to attach the MDF file:
> Error 823: I/O error (torn page) detected during read at offset
> (0x0000036cba0000 in file 'D:\Data\Data_file)
> Unfortunately the backup is 2 hours behind from the failure!
> Any help would be greatly appreciated.
Well, at least there is a backup!
I have no idea how to handle the situation, and the only advice would
be to open a case with Microsoft, but I realise that this may not be
easy where you are located.
I'll inquire with Microsoft, but I would have too much hope.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||> Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.
I really don't know what's wrong with my clock :-(

> I'll inquire with Microsoft, but I would have too much hope.
Thanks indeed!
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns97AE9408A75F1Yazorman@.127.0.0.1...
> Leila (Leilas@.hotpop.com) writes:
> Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.
>
> Well, at least there is a backup!
> I have no idea how to handle the situation, and the only advice would
> be to open a case with Microsoft, but I realise that this may not be
> easy where you are located.
> I'll inquire with Microsoft, but I would have too much hope.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||Leila (Leilas@.hotpop.com) writes:
> I really don't know what's wrong with my clock :-(
As we say up here "Time goes fast, when you're having fun!". :-)
One suggestion I got from a fellow MVP was:
How about stopping SS, renaming the corrupted database files, starting
SS, create new database with same filenames as corrupted db had
originally, stopping SS, removing new database files and then renaming
corrupted db backup to the original names? SQL Server will possibly
recover the database fine...
If I were to do this operation, I would make sure that I have a copy of
the bad database files, to keep a starting point.
I'm a little skeptic that the above actually works. I guess that whar
you are really after is the transaction log, so you can back it up, and
apply it to the backup, so you don't lose those two hours of work.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Leila,
If you can read Russian, or fill in the gaps with
some online translation, this might help:
http://www.sql.ru/faq/faq_topic.aspx?fid=123
Steve Kass
Drew University
Leila wrote:

>I really don't know what's wrong with my clock :-(
>
>
>Thanks indeed!
>
>
>"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
>news:Xns97AE9408A75F1Yazorman@.127.0.0.1...
>
>
>|||> As we say up here "Time goes fast, when you're having fun!". :-)
lol! We say exactly the same thing here! But it seems my notebook is having
fun, not me!

> How about stopping SS, renaming the corrupted database files, starting...
oops! Really tricky! I must try it...
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns97AECB33EE3F0Yazorman@.127.0.0.1...
> Leila (Leilas@.hotpop.com) writes:
> As we say up here "Time goes fast, when you're having fun!". :-)
>
> One suggestion I got from a fellow MVP was:
> How about stopping SS, renaming the corrupted database files, starting
> SS, create new database with same filenames as corrupted db had
> originally, stopping SS, removing new database files and then renaming
> corrupted db backup to the original names? SQL Server will possibly
> recover the database fine...
> If I were to do this operation, I would make sure that I have a copy of
> the bad database files, to keep a starting point.
> I'm a little skeptic that the above actually works. I guess that whar
> you are really after is the transaction log, so you can back it up, and
> apply it to the backup, so you don't lose those two hours of work.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||Thanks Steve!
Unfortunately I cannot read Russian but the TSQL seems that you must at
least
have your database attached to SQL Server before using that instruction?
"Steve Kass" <skass@.drew.edu> wrote in message
news:%23dKWuUwZGHA.3532@.TK2MSFTNGP05.phx.gbl...
> Leila,
> If you can read Russian, or fill in the gaps with
> some online translation, this might help:
> http://www.sql.ru/faq/faq_topic.aspx?fid=123
> Steve Kass
> Drew University
> Leila wrote:
>|||Leila (Leilas@.hotpop.com) writes:
> Unfortunately I cannot read Russian but the TSQL seems that you must at
> least
> have your database attached to SQL Server before using that instruction?
Which can be solved by creating a database, and the throwing the files
for that away, and then slapping the files for the broken database in
place.
However, I doubt that this is the solution to your problem. That script
seems to create an empty log file, and if I understand correctly, the
log file is what you want to be able to access?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Leila (Leilas@.hotpop.com) writes:
> HDD failure caused to move the data to a new disk. We are no longer able
> to attach the MDF file. I searched a lot but all of solutions work only
> when the database is running under SQL Server and is suspected, not for
> me (detached database). I get this error when trying to attach the MDF
> file: Error 823: I/O error (torn page) detected during read at offset
> (0x0000036cba0000 in file 'D:\Data\Data_file)
> Unfortunately the backup is 2 hours behind from the failure!
> Any help would be greatly appreciated.
I guess that you by now already have restored that two-hour old backup.
Unfortunately, it took some time to find out the correct procedure.
It is described on
http://www.sqljunkies.com/HowTo/F5B...8DDB08B0C1.scuk
With quite some help of some MVP colleagues I developed the demo script
below, to illustrate the procedure.
It assumes that you know the name and location of your log files, but
with a full backup available, it should not be difficult to work out.
-- See also
-- http://www.sqljunkies.com/HowTo/F5B...8DDB08B0C1.scuk
-- First take a copy of Northwind that we can mess up a bit.
BACKUP DATABASE Northwind to disk = 'c:\temp\Northwind.bak'
go
RESTORE DATABASE northbreeze from disk = 'c:\temp\Northwind.bak'
WITH MOVE 'Northwind' TO 'C:\temp\northbreeze.mdf',
MOVE 'Northwind_log' TO 'C:\temp\northbreeze.ldf',
REPLACE
go
-- And make sure that it has full recovery.
ALTER DATABASE northbreeze SET RECOVERY FULL
go
USE northbreeze
go
-- Let's add a new customer to northbreeze.
INSERT Customers (CustomerID, CompanyName, ContactName,
ContactTitle, Address, City, Region, PostalCode,
Country, Phone, Fax)
VALUES ('GARBO', 'Greta Garbos Deliktatesshandel', 'Frk. Gustafsson',
'Frken', 'Mosebacke Torg 12', 'Stockholm', NULL, '11223',
'Sweden', '+46-8-90510', NULL)
go
-- Make sure that this database is backed up on its own. Backup the log
-- as well.
BACKUP DATABASE northbreeze to disk = 'c:\temp\Northbreeze.bak'
BACKUP LOG northbreeze to disk = 'c:\temp\Northbreeze.logbak'
go
-- Perform further updates in the database.
DELETE Customers
FROM Customers C
WHERE NOT EXISTS (SELECT *
FROM Orders O
WHERE O.CustomerID = C.CustomerID)
AND C.CustomerID <> 'GARBO'
go
-- Go to master
USE master
go
-- And detach database
EXEC sp_detach_db northbreeze
go
-- Assume that something bad happens to the MDF file while it is detached.
-- First step is to rename the files. (Although we could toss the bsd MDF
-- file.)
EXEC xp_cmdshell 'MOVE c:\temp\northbreeze.mdf c:\temp\northbreeze-
crashed.mdf'
EXEC xp_cmdshell 'MOVE c:\temp\northbreeze.ldf c:\temp\northbreeze-
crashed.ldf'
go
-- Create a new empty database were we want the real thing to be. Make sure
-- that we have full recovery-
CREATE DATABASE northbreeze
ON (NAME = 'Northwind', FILENAME = 'C:\temp\northbreeze.mdf')
LOG ON (NAME = 'Northwind.log', FILENAME = 'C:\temp\northbreeze.ldf')
ALTER DATABASE northbreeze SET RECOVERY FULL
go
-- Shut down SQL Server.
SHUTDOWN
go
-- In file system do this:
-- 1) move northbreeze.mdf to northbreeze-dummy.mdf (or delete it)
-- 1) move northbreeze.ldf to northbreeze-dummy.ldf (or delete it)
-- 2) move northbreeze-crashed.ldf to northbreeze.ldf
-- Start server again
go
-- The northbreeze database does at this point consist of the log file only!
-- (Or SQL Server created a new MDF; I did not check.)
-- We can now back up the tail of the log. Note NO_TRUNCATE!
BACKUP LOG northbreeze TO DISK = 'C:\temp\northbreeze-tail.logbak'
WITH NO_TRUNCATE
go
-- Drop the database
DROP DATABASE northbreeze
go
-- The log file may still be there, just move it out of the way.
EXEC xp_cmdshell
'MOVE c:\temp\northbreeze.ldf c:\temp\northbreeze-crashed.ldf'
go
-- Restore the database, use no NORECOVER, as we will apply logs as well.
RESTORE DATABASE northbreeze from disk = 'c:\temp\Northbreeze.bak'
WITH NORECOVERY
-- Restore the fist log dump.
RESTORE LOG northbreeze from disk = 'C:\temp\northbreeze.logbak'
WITH NORECOVERY
-- Apply the tail log.
RESTORE LOG northbreeze from disk = 'C:\temp\northbreeze-tail.logbak'
go
-- Verify that northbreeze != Northwind.
SELECT a.CustomerID, b.CustomerID
FROM Northwind..Customers a
FULL JOIN northbreeze..Customers b ON a.CustomerID = b.CustomerID
WHERE a.CustomerID IS NULL OR
b.CustomerID IS NULL
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspxsql

Error 823: I/O error (torn page) detected during read at offset...

Hi,
HDD failure caused to move the data to a new disk. We are no longer able to
attach the MDF file. I searched a lot but all of solutions work only when
the database is running under SQL Server and is suspected, not for me
(detached database).
I get this error when trying to attach the MDF file:
Error 823: I/O error (torn page) detected during read at offset
(0x0000036cba0000 in file 'D:\Data\Data_file)
Unfortunately the backup is 2 hours behind from the failure!
Any help would be greatly appreciated.
LeilaLeila (Leilas@.hotpop.com) writes:
> Date: Sun, 23 Apr 2006 20:49:51 +0430
Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.
> HDD failure caused to move the data to a new disk. We are no longer able
> to attach the MDF file. I searched a lot but all of solutions work only
> when the database is running under SQL Server and is suspected, not for
> me (detached database).
> I get this error when trying to attach the MDF file:
> Error 823: I/O error (torn page) detected during read at offset
> (0x0000036cba0000 in file 'D:\Data\Data_file)
> Unfortunately the backup is 2 hours behind from the failure!
> Any help would be greatly appreciated.
Well, at least there is a backup!
I have no idea how to handle the situation, and the only advice would
be to open a case with Microsoft, but I realise that this may not be
easy where you are located.
I'll inquire with Microsoft, but I would have too much hope.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||> Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.
I really don't know what's wrong with my clock :-(
> I'll inquire with Microsoft, but I would have too much hope.
Thanks indeed!
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns97AE9408A75F1Yazorman@.127.0.0.1...
> Leila (Leilas@.hotpop.com) writes:
>> Date: Sun, 23 Apr 2006 20:49:51 +0430
> Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.
>> HDD failure caused to move the data to a new disk. We are no longer able
>> to attach the MDF file. I searched a lot but all of solutions work only
>> when the database is running under SQL Server and is suspected, not for
>> me (detached database).
>> I get this error when trying to attach the MDF file:
>> Error 823: I/O error (torn page) detected during read at offset
>> (0x0000036cba0000 in file 'D:\Data\Data_file)
>> Unfortunately the backup is 2 hours behind from the failure!
>> Any help would be greatly appreciated.
> Well, at least there is a backup!
> I have no idea how to handle the situation, and the only advice would
> be to open a case with Microsoft, but I realise that this may not be
> easy where you are located.
> I'll inquire with Microsoft, but I would have too much hope.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Leila (Leilas@.hotpop.com) writes:
>> Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.
> I really don't know what's wrong with my clock :-(
As we say up here "Time goes fast, when you're having fun!". :-)
>> I'll inquire with Microsoft, but I would have too much hope.
One suggestion I got from a fellow MVP was:
How about stopping SS, renaming the corrupted database files, starting
SS, create new database with same filenames as corrupted db had
originally, stopping SS, removing new database files and then renaming
corrupted db backup to the original names? SQL Server will possibly
recover the database fine...
If I were to do this operation, I would make sure that I have a copy of
the bad database files, to keep a starting point.
I'm a little skeptic that the above actually works. I guess that whar
you are really after is the transaction log, so you can back it up, and
apply it to the backup, so you don't lose those two hours of work.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Leila,
If you can read Russian, or fill in the gaps with
some online translation, this might help:
http://www.sql.ru/faq/faq_topic.aspx?fid=123
Steve Kass
Drew University
Leila wrote:
>>Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.
>>
>I really don't know what's wrong with my clock :-(
>
>>I'll inquire with Microsoft, but I would have too much hope.
>>
>Thanks indeed!
>
>
>"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
>news:Xns97AE9408A75F1Yazorman@.127.0.0.1...
>
>>Leila (Leilas@.hotpop.com) writes:
>>
>>Date: Sun, 23 Apr 2006 20:49:51 +0430
>>
>>Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.
>>
>>HDD failure caused to move the data to a new disk. We are no longer able
>>to attach the MDF file. I searched a lot but all of solutions work only
>>when the database is running under SQL Server and is suspected, not for
>>me (detached database).
>>I get this error when trying to attach the MDF file:
>>Error 823: I/O error (torn page) detected during read at offset
>>(0x0000036cba0000 in file 'D:\Data\Data_file)
>>Unfortunately the backup is 2 hours behind from the failure!
>>Any help would be greatly appreciated.
>>
>>Well, at least there is a backup!
>>I have no idea how to handle the situation, and the only advice would
>>be to open a case with Microsoft, but I realise that this may not be
>>easy where you are located.
>>I'll inquire with Microsoft, but I would have too much hope.
>>
>>--
>>Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>>Books Online for SQL Server 2005 at
>>http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
>>Books Online for SQL Server 2000 at
>>http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>>
>
>|||> As we say up here "Time goes fast, when you're having fun!". :-)
lol! We say exactly the same thing here! But it seems my notebook is having
fun, not me!
> How about stopping SS, renaming the corrupted database files, starting...
oops! Really tricky! I must try it...
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns97AECB33EE3F0Yazorman@.127.0.0.1...
> Leila (Leilas@.hotpop.com) writes:
>> Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.
>> I really don't know what's wrong with my clock :-(
> As we say up here "Time goes fast, when you're having fun!". :-)
>
>> I'll inquire with Microsoft, but I would have too much hope.
> One suggestion I got from a fellow MVP was:
> How about stopping SS, renaming the corrupted database files, starting
> SS, create new database with same filenames as corrupted db had
> originally, stopping SS, removing new database files and then renaming
> corrupted db backup to the original names? SQL Server will possibly
> recover the database fine...
> If I were to do this operation, I would make sure that I have a copy of
> the bad database files, to keep a starting point.
> I'm a little skeptic that the above actually works. I guess that whar
> you are really after is the transaction log, so you can back it up, and
> apply it to the backup, so you don't lose those two hours of work.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Thanks Steve!
Unfortunately I cannot read Russian but the TSQL seems that you must at
least
have your database attached to SQL Server before using that instruction?
"Steve Kass" <skass@.drew.edu> wrote in message
news:%23dKWuUwZGHA.3532@.TK2MSFTNGP05.phx.gbl...
> Leila,
> If you can read Russian, or fill in the gaps with
> some online translation, this might help:
> http://www.sql.ru/faq/faq_topic.aspx?fid=123
> Steve Kass
> Drew University
> Leila wrote:
>>Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.
>>I really don't know what's wrong with my clock :-(
>>
>>I'll inquire with Microsoft, but I would have too much hope.
>>Thanks indeed!
>>
>>
>>"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
>>news:Xns97AE9408A75F1Yazorman@.127.0.0.1...
>>Leila (Leilas@.hotpop.com) writes:
>>Date: Sun, 23 Apr 2006 20:49:51 +0430
>>Your clock is ahead ahain! It's 14:30 over here, and I'm on +0200.
>>
>>HDD failure caused to move the data to a new disk. We are no longer able
>>to attach the MDF file. I searched a lot but all of solutions work only
>>when the database is running under SQL Server and is suspected, not for
>>me (detached database).
>>I get this error when trying to attach the MDF file:
>>Error 823: I/O error (torn page) detected during read at offset
>>(0x0000036cba0000 in file 'D:\Data\Data_file)
>>Unfortunately the backup is 2 hours behind from the failure!
>>Any help would be greatly appreciated.
>>Well, at least there is a backup!
>>I have no idea how to handle the situation, and the only advice would
>>be to open a case with Microsoft, but I realise that this may not be
>>easy where you are located.
>>I'll inquire with Microsoft, but I would have too much hope.
>>
>>--
>>Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>>Books Online for SQL Server 2005 at
>>http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
>>Books Online for SQL Server 2000 at
>>http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>>|||Leila (Leilas@.hotpop.com) writes:
> Unfortunately I cannot read Russian but the TSQL seems that you must at
> least
> have your database attached to SQL Server before using that instruction?
Which can be solved by creating a database, and the throwing the files
for that away, and then slapping the files for the broken database in
place.
However, I doubt that this is the solution to your problem. That script
seems to create an empty log file, and if I understand correctly, the
log file is what you want to be able to access?
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Leila (Leilas@.hotpop.com) writes:
> HDD failure caused to move the data to a new disk. We are no longer able
> to attach the MDF file. I searched a lot but all of solutions work only
> when the database is running under SQL Server and is suspected, not for
> me (detached database). I get this error when trying to attach the MDF
> file: Error 823: I/O error (torn page) detected during read at offset
> (0x0000036cba0000 in file 'D:\Data\Data_file)
> Unfortunately the backup is 2 hours behind from the failure!
> Any help would be greatly appreciated.
I guess that you by now already have restored that two-hour old backup.
Unfortunately, it took some time to find out the correct procedure.
It is described on
http://www.sqljunkies.com/HowTo/F5B99949-4D67-4B27-B752-AA8DDB08B0C1.scuk
With quite some help of some MVP colleagues I developed the demo script
below, to illustrate the procedure.
It assumes that you know the name and location of your log files, but
with a full backup available, it should not be difficult to work out.
-- See also
-- http://www.sqljunkies.com/HowTo/F5B99949-4D67-4B27-B752-AA8DDB08B0C1.scuk
-- First take a copy of Northwind that we can mess up a bit.
BACKUP DATABASE Northwind to disk = 'c:\temp\Northwind.bak'
go
RESTORE DATABASE northbreeze from disk = 'c:\temp\Northwind.bak'
WITH MOVE 'Northwind' TO 'C:\temp\northbreeze.mdf',
MOVE 'Northwind_log' TO 'C:\temp\northbreeze.ldf',
REPLACE
go
-- And make sure that it has full recovery.
ALTER DATABASE northbreeze SET RECOVERY FULL
go
USE northbreeze
go
-- Let's add a new customer to northbreeze.
INSERT Customers (CustomerID, CompanyName, ContactName,
ContactTitle, Address, City, Region, PostalCode,
Country, Phone, Fax)
VALUES ('GARBO', 'Greta Garbos Deliktatesshandel', 'Frk. Gustafsson',
'Fröken', 'Mosebacke Torg 12', 'Stockholm', NULL, '11223',
'Sweden', '+46-8-90510', NULL)
go
-- Make sure that this database is backed up on its own. Backup the log
-- as well.
BACKUP DATABASE northbreeze to disk = 'c:\temp\Northbreeze.bak'
BACKUP LOG northbreeze to disk = 'c:\temp\Northbreeze.logbak'
go
-- Perform further updates in the database.
DELETE Customers
FROM Customers C
WHERE NOT EXISTS (SELECT *
FROM Orders O
WHERE O.CustomerID = C.CustomerID)
AND C.CustomerID <> 'GARBO'
go
-- Go to master
USE master
go
-- And detach database
EXEC sp_detach_db northbreeze
go
-- Assume that something bad happens to the MDF file while it is detached.
-- First step is to rename the files. (Although we could toss the bsd MDF
-- file.)
EXEC xp_cmdshell 'MOVE c:\temp\northbreeze.mdf c:\temp\northbreeze-
crashed.mdf'
EXEC xp_cmdshell 'MOVE c:\temp\northbreeze.ldf c:\temp\northbreeze-
crashed.ldf'
go
-- Create a new empty database were we want the real thing to be. Make sure
-- that we have full recovery-
CREATE DATABASE northbreeze
ON (NAME = 'Northwind', FILENAME = 'C:\temp\northbreeze.mdf')
LOG ON (NAME = 'Northwind.log', FILENAME = 'C:\temp\northbreeze.ldf')
ALTER DATABASE northbreeze SET RECOVERY FULL
go
-- Shut down SQL Server.
SHUTDOWN
go
-- In file system do this:
-- 1) move northbreeze.mdf to northbreeze-dummy.mdf (or delete it)
-- 1) move northbreeze.ldf to northbreeze-dummy.ldf (or delete it)
-- 2) move northbreeze-crashed.ldf to northbreeze.ldf
-- Start server again
go
-- The northbreeze database does at this point consist of the log file only!
-- (Or SQL Server created a new MDF; I did not check.)
-- We can now back up the tail of the log. Note NO_TRUNCATE!
BACKUP LOG northbreeze TO DISK = 'C:\temp\northbreeze-tail.logbak'
WITH NO_TRUNCATE
go
-- Drop the database
DROP DATABASE northbreeze
go
-- The log file may still be there, just move it out of the way.
EXEC xp_cmdshell
'MOVE c:\temp\northbreeze.ldf c:\temp\northbreeze-crashed.ldf'
go
-- Restore the database, use no NORECOVER, as we will apply logs as well.
RESTORE DATABASE northbreeze from disk = 'c:\temp\Northbreeze.bak'
WITH NORECOVERY
-- Restore the fist log dump.
RESTORE LOG northbreeze from disk = 'C:\temp\northbreeze.logbak'
WITH NORECOVERY
-- Apply the tail log.
RESTORE LOG northbreeze from disk = 'C:\temp\northbreeze-tail.logbak'
go
-- Verify that northbreeze != Northwind.
SELECT a.CustomerID, b.CustomerID
FROM Northwind..Customers a
FULL JOIN northbreeze..Customers b ON a.CustomerID = b.CustomerID
WHERE a.CustomerID IS NULL OR
b.CustomerID IS NULL
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Error 823

I'm running W2000 server with SQL 7.0 SP2. we get the following error

Error 823, severity 24, state 1 , i/o error (bad page 10) detected
during read of BUF pointer= 0x11959fc80, page ptr=0x45724000, page id=
(0x3:0x777f), dbid=7, status= 0x 801, file=D:\masdata\monitordb.ndf

We continued restoring a backup, but after a few day, the database crash again.Microsoft has reported to fix this error in service pack 3,

FIX: Error 823 or 8966 Reported by SQL Server with Insufficient System Resources

Knowledge base article Q274310sql

Error 823

Hello,
I have lost my volume D and E but when i recover it by Restorer 2000
professionnel. I get this error:
input/Output Error (BAD page ID) detected during read at of set .. in the
file: base.mdf.
I have no backup and i am desperate.
is there any chance?
thanks for your replay
Did you restore sql server files to exactly the same location and with the
same name? If so, you could be SOL.
This may be an unfortunate occurrence of what gets a LOT of people when the
sh-t hits the fan - they have NEVER tested a full restore of a backup.
Hopefully you won't lose as much and have as much heartache as the State of
Alaska had last year when they wiped two drive systems and THEIR backups
didn't work either!
Best of luck.
TheSQLGuru
President
Indicium Resources, Inc.
"doudoune" <doudoune@.discussions.microsoft.com> wrote in message
news:ED4AAEA3-E515-4BBA-9DBA-ABCA63CFFA83@.microsoft.com...
> Hello,
> I have lost my volume D and E but when i recover it by Restorer 2000
> professionnel. I get this error:
> input/Output Error (BAD page ID) detected during read at of set .. in the
> file: base.mdf.
> I have no backup and i am desperate.
> is there any chance?
> thanks for your replay
>
>
>
|||Thanks for replay.
My log is intact. can we have a chance?
"TheSQLGuru" wrote:

> Did you restore sql server files to exactly the same location and with the
> same name? If so, you could be SOL.
> This may be an unfortunate occurrence of what gets a LOT of people when the
> sh-t hits the fan - they have NEVER tested a full restore of a backup.
> Hopefully you won't lose as much and have as much heartache as the State of
> Alaska had last year when they wiped two drive systems and THEIR backups
> didn't work either!
> Best of luck.
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "doudoune" <doudoune@.discussions.microsoft.com> wrote in message
> news:ED4AAEA3-E515-4BBA-9DBA-ABCA63CFFA83@.microsoft.com...
>
>
|||Did you restore sql server files to exactly the same location and with the
same name? If so, you could be SOL.
This may be an unfortunate occurrence of what gets a LOT of people when the
sh-t hits the fan - they have NEVER tested a full restore of a backup.
Hopefully you won't lose as much and have as much heartache as the State of
Alaska had last year when they wiped two drive systems and THEIR backups
didn't work either!
Best of luck.
TheSQLGuru
President
Indicium Resources, Inc.
"doudoune" <doudoune@.discussions.microsoft.com> wrote in message
news:ED4AAEA3-E515-4BBA-9DBA-ABCA63CFFA83@.microsoft.com...
> Hello,
> I have lost my volume D and E but when i recover it by Restorer 2000
> professionnel. I get this error:
> input/Output Error (BAD page ID) detected during read at of set .. in the
> file: base.mdf.
> I have no backup and i am desperate.
> is there any chance?
> thanks for your replay
>
>
>

error 823

hi!!!
i have this error 823, when i choise tables in a database, the description is input output error bad page id was detected during ...
if you have any sugections to recovery database, i'm great for them
thanks
manuel ralha
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/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:66C39796-BD18-4E6C-AED0-DB07AF001973@.microsoft.com...
> hi!!!
> i have this error 823, when i choise tables in a database, the description is input output error bad page id
was detected during ...
> if you have any sugections to recovery database, i'm great for them
> thanks
> manuel ralha
|||hi, thanks
thats a good idea, but when i execute de dbcc checkdb , the error ocurs again
thanks
manuel ralha
|||You didn't say which advice you followed.
Are you saying that you restore the latest clean db backup and all subsequent log backups and one of the log
backups re-introduced the corruption?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:371F4671-4653-4A3A-923C-22790C47AD7E@.microsoft.com...
> hi, thanks
> thats a good idea, but when i execute de dbcc checkdb , the error ocurs again
> thanks
> manuel ralha
|||hi:
the error is this in query analiser or in osql:
I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in file 'D:\cedile\cedile_data.mdf'
manuel ralha
|||What I'm trying to communicate is (as is the article on the web site I suggested) that your best option is
probably to use your backups to restore a clean database, If you feel uncertain about the actions to take, I
suggest you let MS Support help you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:8A7D909A-E787-419A-B926-CA0323CF1600@.microsoft.com...
> hi:
> the error is this in query analiser or in osql:
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in file 'D:\cedile\cedile_data.mdf'
> manuel ralha
>
|||hi
thanks for your help, i'm read your web page, and, i follow all steps. but unhappyly, thoesn't work in this database, i have the same errors.
thanks for your collaboration and help.
manuel ralha

Error 823

When I try to attach a database I get the SQL 823: I/O
error (torn page) detected during 0x000000000... in
the ... .mdf file.
I tried to attach it using single (i.e. .mdf file) but
still the same error.
Could anyone tell me how can I attach this database?
The only thing I know about is when you get a torn page detected, the best
you can do to resolve is restore from backups...
<anonymous@.discussions.microsoft.com> wrote in message
news:03c501c49791$493e0570$a401280a@.phx.gbl...
> When I try to attach a database I get the SQL 823: I/O
> error (torn page) detected during 0x000000000... in
> the ... .mdf file.
> I tried to attach it using single (i.e. .mdf file) but
> still the same error.
> Could anyone tell me how can I attach this database?
|||that's the problem... unfortunately we have a very old
backup.

>--Original Message--
>The only thing I know about is when you get a torn page
detected, the best
>you can do to resolve is restore from backups...
><anonymous@.discussions.microsoft.com> wrote in message
>news:03c501c49791$493e0570$a401280a@.phx.gbl...
>
>.
>
|||Open a case with MS. They *might* have some way to get the db back...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<anonymous@.discussions.microsoft.com> wrote in message
news:03ab01c497bf$9e02ae20$a501280a@.phx.gbl...[vbcol=seagreen]
> that's the problem... unfortunately we have a very old
> backup.
> detected, the best
sql

error 823

hi!!
i have this error 823, when i choise tables in a database, the description is input output error bad page id was detected during ..
if you have any sugections to recovery database, i'm great for the
thank
manuel ralhahttp://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/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:66C39796-BD18-4E6C-AED0-DB07AF001973@.microsoft.com...
> hi!!!
> i have this error 823, when i choise tables in a database, the description is input output error bad page id
was detected during ...
> if you have any sugections to recovery database, i'm great for them
> thanks
> manuel ralha|||hi, thank
thats a good idea, but when i execute de dbcc checkdb , the error ocurs agai
thank
manuel ralha|||You didn't say which advice you followed.
Are you saying that you restore the latest clean db backup and all subsequent log backups and one of the log
backups re-introduced the corruption?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:371F4671-4653-4A3A-923C-22790C47AD7E@.microsoft.com...
> hi, thanks
> thats a good idea, but when i execute de dbcc checkdb , the error ocurs again
> thanks
> manuel ralha|||What I'm trying to communicate is (as is the article on the web site I suggested) that your best option is
probably to use your backups to restore a clean database, If you feel uncertain about the actions to take, I
suggest you let MS Support help you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:8A7D909A-E787-419A-B926-CA0323CF1600@.microsoft.com...
> hi:
> the error is this in query analiser or in osql:
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in file 'D:\cedile\cedile_data.mdf'
> manuel ralha
>|||hi
thanks for your help, i'm read your web page, and, i follow all steps. but unhappyly, thoesn't work in this database, i have the same errors
thanks for your collaboration and help
manuel ralha

Error 823

When I try to attach a database I get the SQL 823: I/O
error (torn page) detected during 0x000000000... in
the ... .mdf file.
I tried to attach it using single (i.e. .mdf file) but
still the same error.
Could anyone tell me how can I attach this database?The only thing I know about is when you get a torn page detected, the best
you can do to resolve is restore from backups...
<anonymous@.discussions.microsoft.com> wrote in message
news:03c501c49791$493e0570$a401280a@.phx.gbl...
> When I try to attach a database I get the SQL 823: I/O
> error (torn page) detected during 0x000000000... in
> the ... .mdf file.
> I tried to attach it using single (i.e. .mdf file) but
> still the same error.
> Could anyone tell me how can I attach this database?|||that's the problem... unfortunately we have a very old
backup.
>--Original Message--
>The only thing I know about is when you get a torn page
detected, the best
>you can do to resolve is restore from backups...
><anonymous@.discussions.microsoft.com> wrote in message
>news:03c501c49791$493e0570$a401280a@.phx.gbl...
>> When I try to attach a database I get the SQL 823: I/O
>> error (torn page) detected during 0x000000000... in
>> the ... .mdf file.
>> I tried to attach it using single (i.e. .mdf file) but
>> still the same error.
>> Could anyone tell me how can I attach this database?
>
>.
>|||Open a case with MS. They *might* have some way to get the db back...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<anonymous@.discussions.microsoft.com> wrote in message
news:03ab01c497bf$9e02ae20$a501280a@.phx.gbl...
> that's the problem... unfortunately we have a very old
> backup.
>>--Original Message--
>>The only thing I know about is when you get a torn page
> detected, the best
>>you can do to resolve is restore from backups...
>><anonymous@.discussions.microsoft.com> wrote in message
>>news:03c501c49791$493e0570$a401280a@.phx.gbl...
>> When I try to attach a database I get the SQL 823: I/O
>> error (torn page) detected during 0x000000000... in
>> the ... .mdf file.
>> I tried to attach it using single (i.e. .mdf file) but
>> still the same error.
>> Could anyone tell me how can I attach this database?
>>
>>.

Error 823

Hello,
I have lost my volume D and E but when i recover it by Restorer 2000
professionnel. I get this error:
input/Output Error (BAD page ID) detected during read at of set .. in the
file: base.mdf.
I have no backup and i am desperate.
is there any chance?
thanks for your replayDid you restore sql server files to exactly the same location and with the
same name' If so, you could be SOL.
This may be an unfortunate occurrence of what gets a LOT of people when the
sh-t hits the fan - they have NEVER tested a full restore of a backup.
Hopefully you won't lose as much and have as much heartache as the State of
Alaska had last year when they wiped two drive systems and THEIR backups
didn't work either!
Best of luck.
--
TheSQLGuru
President
Indicium Resources, Inc.
"doudoune" <doudoune@.discussions.microsoft.com> wrote in message
news:ED4AAEA3-E515-4BBA-9DBA-ABCA63CFFA83@.microsoft.com...
> Hello,
> I have lost my volume D and E but when i recover it by Restorer 2000
> professionnel. I get this error:
> input/Output Error (BAD page ID) detected during read at of set .. in the
> file: base.mdf.
> I have no backup and i am desperate.
> is there any chance?
> thanks for your replay
>
>
>|||Thanks for replay.
My log is intact. can we have a chance?
"TheSQLGuru" wrote:
> Did you restore sql server files to exactly the same location and with the
> same name' If so, you could be SOL.
> This may be an unfortunate occurrence of what gets a LOT of people when the
> sh-t hits the fan - they have NEVER tested a full restore of a backup.
> Hopefully you won't lose as much and have as much heartache as the State of
> Alaska had last year when they wiped two drive systems and THEIR backups
> didn't work either!
> Best of luck.
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "doudoune" <doudoune@.discussions.microsoft.com> wrote in message
> news:ED4AAEA3-E515-4BBA-9DBA-ABCA63CFFA83@.microsoft.com...
> > Hello,
> > I have lost my volume D and E but when i recover it by Restorer 2000
> > professionnel. I get this error:
> > input/Output Error (BAD page ID) detected during read at of set .. in the
> > file: base.mdf.
> > I have no backup and i am desperate.
> > is there any chance?
> >
> > thanks for your replay
> >
> >
> >
> >
> >
>
>|||Did you restore sql server files to exactly the same location and with the
same name' If so, you could be SOL.
This may be an unfortunate occurrence of what gets a LOT of people when the
sh-t hits the fan - they have NEVER tested a full restore of a backup.
Hopefully you won't lose as much and have as much heartache as the State of
Alaska had last year when they wiped two drive systems and THEIR backups
didn't work either!
Best of luck.
--
TheSQLGuru
President
Indicium Resources, Inc.
"doudoune" <doudoune@.discussions.microsoft.com> wrote in message
news:ED4AAEA3-E515-4BBA-9DBA-ABCA63CFFA83@.microsoft.com...
> Hello,
> I have lost my volume D and E but when i recover it by Restorer 2000
> professionnel. I get this error:
> input/Output Error (BAD page ID) detected during read at of set .. in the
> file: base.mdf.
> I have no backup and i am desperate.
> is there any chance?
> thanks for your replay
>
>
>

Error 823

Hello,
I have lost my volume D and E but when i recover it by Restorer 2000
professionnel. I get this error:
input/Output Error (BAD page ID) detected during read at of set .. in the
file: base.mdf.
I have no backup and i am desperate.
is there any chance?
thanks for your replayDid you restore sql server files to exactly the same location and with the
same name' If so, you could be SOL.
This may be an unfortunate occurrence of what gets a LOT of people when the
sh-t hits the fan - they have NEVER tested a full restore of a backup.
Hopefully you won't lose as much and have as much heartache as the State of
Alaska had last year when they wiped two drive systems and THEIR backups
didn't work either!
Best of luck.
TheSQLGuru
President
Indicium Resources, Inc.
"doudoune" <doudoune@.discussions.microsoft.com> wrote in message
news:ED4AAEA3-E515-4BBA-9DBA-ABCA63CFFA83@.microsoft.com...
> Hello,
> I have lost my volume D and E but when i recover it by Restorer 2000
> professionnel. I get this error:
> input/Output Error (BAD page ID) detected during read at of set .. in the
> file: base.mdf.
> I have no backup and i am desperate.
> is there any chance?
> thanks for your replay
>
>
>|||Thanks for replay.
My log is intact. can we have a chance?
"TheSQLGuru" wrote:

> Did you restore sql server files to exactly the same location and with the
> same name' If so, you could be SOL.
> This may be an unfortunate occurrence of what gets a LOT of people when th
e
> sh-t hits the fan - they have NEVER tested a full restore of a backup.
> Hopefully you won't lose as much and have as much heartache as the State o
f
> Alaska had last year when they wiped two drive systems and THEIR backups
> didn't work either!
> Best of luck.
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "doudoune" <doudoune@.discussions.microsoft.com> wrote in message
> news:ED4AAEA3-E515-4BBA-9DBA-ABCA63CFFA83@.microsoft.com...
>
>|||Did you restore sql server files to exactly the same location and with the
same name' If so, you could be SOL.
This may be an unfortunate occurrence of what gets a LOT of people when the
sh-t hits the fan - they have NEVER tested a full restore of a backup.
Hopefully you won't lose as much and have as much heartache as the State of
Alaska had last year when they wiped two drive systems and THEIR backups
didn't work either!
Best of luck.
TheSQLGuru
President
Indicium Resources, Inc.
"doudoune" <doudoune@.discussions.microsoft.com> wrote in message
news:ED4AAEA3-E515-4BBA-9DBA-ABCA63CFFA83@.microsoft.com...
> Hello,
> I have lost my volume D and E but when i recover it by Restorer 2000
> professionnel. I get this error:
> input/Output Error (BAD page ID) detected during read at of set .. in the
> file: base.mdf.
> I have no backup and i am desperate.
> is there any chance?
> thanks for your replay
>
>
>sql

Error 80004005

Running on NT4.0 SP6
Running SQL 6.50.201
SQL-DMO v.6.05.02
SQL-Library v.6.50.252
Trying to access via IIS with an ASP page
Getting the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80004005'
Specified driver could not be loaded due to system error 5
(SQL Server).
/ntahawaii/block.asp, line 13
Checked permissions, looks ok.
Anyone have any idea's as to what to do?
Thank!
billHere are some google hits that you may wish to inspect. Sorry if the link
wraps, tinyurl.com is down -- or at least too slow for me, I haven't got all
minute! :-)
http://groups.google.com/groups?q=%22system+error+5%22+group%3A*sqlserver*&ie=UTF-8&oe=UTF-8&hl=en
"Bill Mukaida" <bmukaida@.hawaii.rr.com> wrote in message
news:0c0701c34720$8ac3d000$a001280a@.phx.gbl...
> Running on NT4.0 SP6
> Running SQL 6.50.201
> SQL-DMO v.6.05.02
> SQL-Library v.6.50.252
> Trying to access via IIS with an ASP page
> Getting the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80004005'
> Specified driver could not be loaded due to system error 5
> (SQL Server).
> /ntahawaii/block.asp, line 13
> Checked permissions, looks ok.
> Anyone have any idea's as to what to do?
> Thank!
> bill
>

Error 644

I'm getting this error message:
Could not find the index entry for RID '%.*hs' in index page %S_PGID, index
ID %d, database '%.*ls'.
How do I find out what the actual index is? No luck in BOLHi Jeff,
Make sure you run dbcc checkdb and check for any errors from the output.
Sincerely,
Yih-Yoon Lee [Microsoft]
Microsoft SQL Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

error 614

One of our 6.5 servers is getting error 614 (A row on a page x was accessed that has an illegal length of y in database z.) However, we can read the specified tables with "select * from a" and can "select into" a new table from those tables with no errors reported. DBCC checkdb and newalloc show no problems. Has anyone else seen this behaviour? We are running diagnostics on the server and raid hardware to determine if those components have problems that might be causing the 614 errors.Microsoft has stated that this error was resolved in Service Pack 3 for SQL Server 6.5. Verify that you have the service pack installed

SELECT @.@.version

6.50.258

It looks like you can get this error if your SELECT statement contains a large GROUP BY list of columns, total length > 512 bytes.|||Originally posted by achorozy
Microsoft has stated that this error was resolved in Service Pack 3 for SQL Server 6.5. Verify that you have the service pack installed

SELECT @.@.version

6.50.258

It looks like you can get this error if your SELECT statement contains a large GROUP BY list of columns, total length > 512 bytes.

------------------------
Thanks for the reply.

Our server version is 6.50.422 which is a "post SP5" version. I considered the large Group By as a possible cause, but no software changes were made prior to the first occurance of the error. I'll double check with the analyst who supports the app to make sure though.

Thanks again.

Error 605, 823

Does anyone see these errors before? How did you fixed it?
Attempt to fetch logical page (4:27456) in database 'tempdb' belongs to
object '0', not to object '#1AB78AA5'..
Error: 605, Severity: 21, State: 1
... IAM indicates that page is allocated to this object
(4:27456)/(4:27456) 0/448236197
pageno is/should be: objid is/should be:
Getpage: bstat=0x9, sstat=0x4800, cache
I/O error (bad page ID) detected during read at offset 0x000000b6ec4000 in
file 'I:\MSSQL\Data\tempdb1.mdf'..
Error: 823, Severity: 24, State: 2
Thanks,
LijunGeneral recommendations for corrupt or suspect databases:
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/
"Lijun Zhang" <nospam@.nospam.nospam> wrote in message news:usIUpWzdFHA.2736@.TK2MSFTNGP12.phx
.gbl...
> Does anyone see these errors before? How did you fixed it?
> Attempt to fetch logical page (4:27456) in database 'tempdb' belongs to
> object '0', not to object '#1AB78AA5'..
> Error: 605, Severity: 21, State: 1
> ... IAM indicates that page is allocated to this object
> (4:27456)/(4:27456) 0/448236197
> pageno is/should be: objid is/should be:
> Getpage: bstat=0x9, sstat=0x4800, cache
> I/O error (bad page ID) detected during read at offset 0x000000b6ec4000 in
> file 'I:\MSSQL\Data\tempdb1.mdf'..
> Error: 823, Severity: 24, State: 2
>
> Thanks,
> Lijun
>

Error 605, 823

Does anyone see these errors before? How did you fixed it?
Attempt to fetch logical page (4:27456) in database 'tempdb' belongs to
object '0', not to object '#1AB78AA5'..
Error: 605, Severity: 21, State: 1
... IAM indicates that page is allocated to this object
(4:27456)/(4:27456) 0/448236197
pageno is/should be: objid is/should be:
Getpage: bstat=0x9, sstat=0x4800, cache
I/O error (bad page ID) detected during read at offset 0x000000b6ec4000 in
file 'I:\MSSQL\Data\tempdb1.mdf'..
Error: 823, Severity: 24, State: 2
Thanks,
LijunGeneral recommendations for corrupt or suspect databases:
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/
"Lijun Zhang" <nospam@.nospam.nospam> wrote in message news:usIUpWzdFHA.2736@.TK2MSFTNGP12.phx.gbl...
> Does anyone see these errors before? How did you fixed it?
> Attempt to fetch logical page (4:27456) in database 'tempdb' belongs to
> object '0', not to object '#1AB78AA5'..
> Error: 605, Severity: 21, State: 1
> ... IAM indicates that page is allocated to this object
> (4:27456)/(4:27456) 0/448236197
> pageno is/should be: objid is/should be:
> Getpage: bstat=0x9, sstat=0x4800, cache
> I/O error (bad page ID) detected during read at offset 0x000000b6ec4000 in
> file 'I:\MSSQL\Data\tempdb1.mdf'..
> Error: 823, Severity: 24, State: 2
>
> Thanks,
> Lijun
>

Error 605, 823

Does anyone see these errors before? How did you fixed it?
Attempt to fetch logical page (4:27456) in database 'tempdb' belongs to
object '0', not to object '#1AB78AA5'..
Error: 605, Severity: 21, State: 1
... IAM indicates that page is allocated to this object
(4:27456)/(4:27456) 0/448236197
pageno is/should be: objid is/should be:
Getpage: bstat=0x9, sstat=0x4800, cache
I/O error (bad page ID) detected during read at offset 0x000000b6ec4000 in
file 'I:\MSSQL\Data\tempdb1.mdf'..
Error: 823, Severity: 24, State: 2
Thanks,
Lijun
General recommendations for corrupt or suspect databases:
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/
"Lijun Zhang" <nospam@.nospam.nospam> wrote in message news:usIUpWzdFHA.2736@.TK2MSFTNGP12.phx.gbl...
> Does anyone see these errors before? How did you fixed it?
> Attempt to fetch logical page (4:27456) in database 'tempdb' belongs to
> object '0', not to object '#1AB78AA5'..
> Error: 605, Severity: 21, State: 1
> ... IAM indicates that page is allocated to this object
> (4:27456)/(4:27456) 0/448236197
> pageno is/should be: objid is/should be:
> Getpage: bstat=0x9, sstat=0x4800, cache
> I/O error (bad page ID) detected during read at offset 0x000000b6ec4000 in
> file 'I:\MSSQL\Data\tempdb1.mdf'..
> Error: 823, Severity: 24, State: 2
>
> Thanks,
> Lijun
>