Database hung after failure of large update query

I tried to run a large update query last night that did not complete.
But now I cannot access that database. In fact, when I click on Databases
in Enterprise Manager, that hangs and shows an hourglass.
I suspect that it failed due to a disc space. When I look at the process
status, I see a SPID that has a wait type of PAGEIOLatch_EX that is 'working'
on that database.
I don't really need to complete the update (partial complete would be fine).
I just need to free up the database so I can work on the database.
Any thoughts?
- Jesse
Jesse A wrote:
> I tried to run a large update query last night that did not complete.
> But now I cannot access that database. In fact, when I click on
> Databases in Enterprise Manager, that hangs and shows an hourglass.
> I suspect that it failed due to a disc space. When I look at the
> process status, I see a SPID that has a wait type of PAGEIOLatch_EX
> that is 'working' on that database.
> I don't really need to complete the update (partial complete would be
> fine). I just need to free up the database so I can work on the
> database.
> Any thoughts?
There is no such thing as a partial update unless you were using batches
to perform the updates in the first place. What likely happened is that
you ran out of space and SQL Server may be in the process of rolling
back the transaction (which can take just as long as the original update
took).
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||If u dont want any transaction for that particular SPID then u will kill the
particular process by KILL SPID
hope this will help
Herbert
"Jesse A" wrote:

> I tried to run a large update query last night that did not complete.
> But now I cannot access that database. In fact, when I click on Databases
> in Enterprise Manager, that hangs and shows an hourglass.
> I suspect that it failed due to a disc space. When I look at the process
> status, I see a SPID that has a wait type of PAGEIOLatch_EX that is 'working'
> on that database.
> I don't really need to complete the update (partial complete would be fine).
> I just need to free up the database so I can work on the database.
> Any thoughts?
> --
> - Jesse

Database hung after failure of large update query

I tried to run a large update query last night that did not complete.
But now I cannot access that database. In fact, when I click on Databases
in Enterprise Manager, that hangs and shows an hourglass.
I suspect that it failed due to a disc space. When I look at the process
status, I see a SPID that has a wait type of PAGEIOLatch_EX that is 'working'
on that database.
I don't really need to complete the update (partial complete would be fine).
I just need to free up the database so I can work on the database.
Any thoughts?
--
- JesseJesse A wrote:
> I tried to run a large update query last night that did not complete.
> But now I cannot access that database. In fact, when I click on
> Databases in Enterprise Manager, that hangs and shows an hourglass.
> I suspect that it failed due to a disc space. When I look at the
> process status, I see a SPID that has a wait type of PAGEIOLatch_EX
> that is 'working' on that database.
> I don't really need to complete the update (partial complete would be
> fine). I just need to free up the database so I can work on the
> database.
> Any thoughts?
There is no such thing as a partial update unless you were using batches
to perform the updates in the first place. What likely happened is that
you ran out of space and SQL Server may be in the process of rolling
back the transaction (which can take just as long as the original update
took).
David Gugick
Quest Software
www.imceda.com
www.quest.com|||If u dont want any transaction for that particular SPID then u will kill the
particular process by KILL SPID
hope this will help
--
Herbert
"Jesse A" wrote:
> I tried to run a large update query last night that did not complete.
> But now I cannot access that database. In fact, when I click on Databases
> in Enterprise Manager, that hangs and shows an hourglass.
> I suspect that it failed due to a disc space. When I look at the process
> status, I see a SPID that has a wait type of PAGEIOLatch_EX that is 'working'
> on that database.
> I don't really need to complete the update (partial complete would be fine).
> I just need to free up the database so I can work on the database.
> Any thoughts?
> --
> - Jesse

Database hung after failure of large update query

I tried to run a large update query last night that did not complete.
But now I cannot access that database. In fact, when I click on Databases
in Enterprise Manager, that hangs and shows an hourglass.
I suspect that it failed due to a disc space. When I look at the process
status, I see a SPID that has a wait type of PAGEIOLatch_EX that is 'working
'
on that database.
I don't really need to complete the update (partial complete would be fine).
I just need to free up the database so I can work on the database.
Any thoughts?
--
- JesseJesse A wrote:
> I tried to run a large update query last night that did not complete.
> But now I cannot access that database. In fact, when I click on
> Databases in Enterprise Manager, that hangs and shows an hourglass.
> I suspect that it failed due to a disc space. When I look at the
> process status, I see a SPID that has a wait type of PAGEIOLatch_EX
> that is 'working' on that database.
> I don't really need to complete the update (partial complete would be
> fine). I just need to free up the database so I can work on the
> database.
> Any thoughts?
There is no such thing as a partial update unless you were using batches
to perform the updates in the first place. What likely happened is that
you ran out of space and SQL Server may be in the process of rolling
back the transaction (which can take just as long as the original update
took).
David Gugick
Quest Software
www.imceda.com
www.quest.com|||If u dont want any transaction for that particular SPID then u will kill the
particular process by KILL SPID
hope this will help
Herbert
"Jesse A" wrote:

> I tried to run a large update query last night that did not complete.
> But now I cannot access that database. In fact, when I click on Database
s
> in Enterprise Manager, that hangs and shows an hourglass.
> I suspect that it failed due to a disc space. When I look at the process
> status, I see a SPID that has a wait type of PAGEIOLatch_EX that is 'worki
ng'
> on that database.
> I don't really need to complete the update (partial complete would be fine
).
> I just need to free up the database so I can work on the database.
> Any thoughts?
> --
> - Jessesql

database failure to restore from NT backup

Hello,
Have you seen this from Microsoft ?
http://support.microsoft.com/default.aspx?scid=kb;en-
us;268481
J

>--Original Message--
>One of our customers had a problem with SQL Server 7. We
have instigated a work around, but they want to know what
the root cause was.
>Problem description
>It seems that they had disk problems, then wanted to
restore the database from a backup. They were not doing
backups to disk, just to shutting down the services &
doing a cold NT backup to tape.
>Error Details
>The server lost a disc (one of five from RAID5 array).
After it was fixed, the data was restored from a backup
tape and the following appeared in the SQL Server activity
log. The database was in suspect mode.
>2004-04-29 19:36:45.31 spid9 Starting up
database 'dataname'.
>2004-04-29 19:36:45.31 spid9 Opening file
d:\SQL\data\dataname_Data.MDF.
>2004-04-29 19:36:45.31 spid9 Opening file
e:\SQL\data\dataname2_Data.NDF.
>2004-04-29 19:36:45.31 spid9 The header for
file 'e:\SQL\data\dataname2_Data.NDF' is not a valid
database file header. The PageAudit property is incorrect.
>2004-04-29 19:36:45.32 spid9 Device activation error.
The physical file name 'e:\SQL\data\dataname2_Data.NDF'
may be incorrect.
>2004-04-29 19:36:45.32 spid9 Opening file
d:\SQL\data\dataname_Log.LDF.
>2004-04-29 19:36:45.32 spid9 Opening file
e:\SQL\data\dataname2_Log.LDF.
>System Details
>SQL Server 7
>NT 4
>Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model
0
>4 * PIII 700 Mhz
>2 GB RAM
>40/80GB SCSI DLT Internal Tape Drive
>9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
>32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet
Pro100+)
>Regards
>David
>.
>Julie
Thanks for the link, but the customer says that the Bull RAID controller is
a Milex, not Adaptec,|||Ok, but does it use the Abaptec drivers such as graphics
tend to use the same ones ?
J

>--Original Message--
>Julie
>Thanks for the link, but the customer says that the Bull
RAID controller is a Milex, not Adaptec,
>.
>

database failure to restore from NT backup

One of our customers had a problem with SQL Server 7. We have instigated a
work around, but they want to know what the root cause was.
Problem description
It seems that they had disk problems, then wanted to restore the database fr
om a backup. They were not doing backups to disk, just to shutting down the
services & doing a cold NT backup to tape.
Error Details
The server lost a disc (one of five from RAID5 array). After it was fixed,
the data was restored from a backup tape and the following appeared in the S
QL Server activity log. The database was in suspect mode.
2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'.
2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF.
2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.NDF.
2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_D
ata.NDF' is not a valid database file header. The PageAudit property is inco
rrect.
2004-04-29 19:36:45.32 spid9 Device activation error. The physical file n
ame 'e:\SQL\data\dataname2_Data.NDF' may be incorrect.
2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF.
System Details
SQL Server 7
NT 4
Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model 0
4 * PIII 700 Mhz
2 GB RAM
40/80GB SCSI DLT Internal Tape Drive
9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+)
Regards
DavidDavid,
This scenario is a typical case why you should do backup using SQL Server BA
CKUP command instead of just
picking up the physical files. In general, it should work assuming that you
indeed get a consistent snapshot
of all files that constitutes a database. IMO, your best bet is to open a ca
se with MS Support for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Lascelles" <anonymous@.discussions.microsoft.com> wrote in message
news:88D14DC8-AF33-4016-B5A3-1E391707D7F6@.microsoft.com...
> One of our customers had a problem with SQL Server 7. We have instigated a work a
round, but they want to
know what the root cause was.
> Problem description
> It seems that they had disk problems, then wanted to restore the database from a b
ackup. They were not
doing backups to disk, just to shutting down the services & doing a cold NT backup to tape.[
vbcol=seagreen]
> Error Details
> The server lost a disc (one of five from RAID5 array). After it was fixed, the da
ta was restored from a[/vbcol]
backup tape and the following appeared in the SQL Server activity log. The database was in s
uspect mode.
> 2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'.
> 2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF
.
> 2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.ND
F.
> 2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_Data.ND
F' is not a valid database
file header. The PageAudit property is incorrect.
> 2004-04-29 19:36:45.32 spid9 Device activation error. The physical file name[/v
bcol]
'e:\SQL\data\dataname2_Data.NDF' may be incorrect.[vbcol=seagreen]
> 2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
> 2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF
.
> System Details
> SQL Server 7
> NT 4
> Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model 0
> 4 * PIII 700 Mhz
> 2 GB RAM
> 40/80GB SCSI DLT Internal Tape Drive
> 9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
> 32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+)
> Regards
> David

database failure to restore from NT backup

One of our customers had a problem with SQL Server 7. We have instigated a work around, but they want to know what the root cause was
Problem descriptio
It seems that they had disk problems, then wanted to restore the database from a backup. They were not doing backups to disk, just to shutting down the services & doing a cold NT backup to tape
Error Detail
The server lost a disc (one of five from RAID5 array). After it was fixed, the data was restored from a backup tape and the following appeared in the SQL Server activity log. The database was in suspect mode.
2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'
2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF.
2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.NDF.
2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_Data.NDF' is not a valid database file header. The PageAudit property is incorrect
2004-04-29 19:36:45.32 spid9 Device activation error. The physical file name 'e:\SQL\data\dataname2_Data.NDF' may be incorrect
2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF
System Detail
SQL Server
NT
Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model
4 * PIII 700 Mh
2 GB RA
40/80GB SCSI DLT Internal Tape Driv
9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1"
32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+
Regard
DavidHello,
Have you seen this from Microsoft ?
http://support.microsoft.com/default.aspx?scid=kb;en-
us;268481
J
>--Original Message--
>One of our customers had a problem with SQL Server 7. We
have instigated a work around, but they want to know what
the root cause was.
>Problem description
>It seems that they had disk problems, then wanted to
restore the database from a backup. They were not doing
backups to disk, just to shutting down the services &
doing a cold NT backup to tape.
>Error Details
>The server lost a disc (one of five from RAID5 array).
After it was fixed, the data was restored from a backup
tape and the following appeared in the SQL Server activity
log. The database was in suspect mode.
>2004-04-29 19:36:45.31 spid9 Starting up
database 'dataname'.
>2004-04-29 19:36:45.31 spid9 Opening file
d:\SQL\data\dataname_Data.MDF.
>2004-04-29 19:36:45.31 spid9 Opening file
e:\SQL\data\dataname2_Data.NDF.
>2004-04-29 19:36:45.31 spid9 The header for
file 'e:\SQL\data\dataname2_Data.NDF' is not a valid
database file header. The PageAudit property is incorrect.
>2004-04-29 19:36:45.32 spid9 Device activation error.
The physical file name 'e:\SQL\data\dataname2_Data.NDF'
may be incorrect.
>2004-04-29 19:36:45.32 spid9 Opening file
d:\SQL\data\dataname_Log.LDF.
>2004-04-29 19:36:45.32 spid9 Opening file
e:\SQL\data\dataname2_Log.LDF.
>System Details
>SQL Server 7
>NT 4
>Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model
0
>4 * PIII 700 Mhz
>2 GB RAM
>40/80GB SCSI DLT Internal Tape Drive
>9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
>32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet
Pro100+)
>Regards
>David
>.
>|||David,
This scenario is a typical case why you should do backup using SQL Server BACKUP command instead of just
picking up the physical files. In general, it should work assuming that you indeed get a consistent snapshot
of all files that constitutes a database. IMO, your best bet is to open a case with MS Support for this.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Lascelles" <anonymous@.discussions.microsoft.com> wrote in message
news:88D14DC8-AF33-4016-B5A3-1E391707D7F6@.microsoft.com...
> One of our customers had a problem with SQL Server 7. We have instigated a work around, but they want to
know what the root cause was.
> Problem description
> It seems that they had disk problems, then wanted to restore the database from a backup. They were not
doing backups to disk, just to shutting down the services & doing a cold NT backup to tape.
> Error Details
> The server lost a disc (one of five from RAID5 array). After it was fixed, the data was restored from a
backup tape and the following appeared in the SQL Server activity log. The database was in suspect mode.
> 2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'.
> 2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF.
> 2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.NDF.
> 2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_Data.NDF' is not a valid database
file header. The PageAudit property is incorrect.
> 2004-04-29 19:36:45.32 spid9 Device activation error. The physical file name
'e:\SQL\data\dataname2_Data.NDF' may be incorrect.
> 2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
> 2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF.
> System Details
> SQL Server 7
> NT 4
> Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model 0
> 4 * PIII 700 Mhz
> 2 GB RAM
> 40/80GB SCSI DLT Internal Tape Drive
> 9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
> 32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+)
> Regards
> David|||Juli
Thanks for the link, but the customer says that the Bull RAID controller is a Milex, not Adaptec,|||Ok, but does it use the Abaptec drivers such as graphics
tend to use the same ones ?
J
>--Original Message--
>Julie
>Thanks for the link, but the customer says that the Bull
RAID controller is a Milex, not Adaptec,
>.
>sql

database failure to restore from NT backup

One of our customers had a problem with SQL Server 7. We have instigated a work around, but they want to know what the root cause was.
Problem description
It seems that they had disk problems, then wanted to restore the database from a backup. They were not doing backups to disk, just to shutting down the services & doing a cold NT backup to tape.
Error Details
The server lost a disc (one of five from RAID5 array). After it was fixed, the data was restored from a backup tape and the following appeared in the SQL Server activity log. The database was in suspect mode.
2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'.
2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF.
2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.NDF.
2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_Data.NDF' is not a valid database file header. The PageAudit property is incorrect.
2004-04-29 19:36:45.32 spid9 Device activation error. The physical file name 'e:\SQL\data\dataname2_Data.NDF' may be incorrect.
2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF.
System Details
SQL Server 7
NT 4
Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model 0
4 * PIII 700 Mhz
2 GB RAM
40/80GB SCSI DLT Internal Tape Drive
9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+)
Regards
David
David,
This scenario is a typical case why you should do backup using SQL Server BACKUP command instead of just
picking up the physical files. In general, it should work assuming that you indeed get a consistent snapshot
of all files that constitutes a database. IMO, your best bet is to open a case with MS Support for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Lascelles" <anonymous@.discussions.microsoft.com> wrote in message
news:88D14DC8-AF33-4016-B5A3-1E391707D7F6@.microsoft.com...
> One of our customers had a problem with SQL Server 7. We have instigated a work around, but they want to
know what the root cause was.
> Problem description
> It seems that they had disk problems, then wanted to restore the database from a backup. They were not
doing backups to disk, just to shutting down the services & doing a cold NT backup to tape.
> Error Details
> The server lost a disc (one of five from RAID5 array). After it was fixed, the data was restored from a
backup tape and the following appeared in the SQL Server activity log. The database was in suspect mode.
> 2004-04-29 19:36:45.31 spid9 Starting up database 'dataname'.
> 2004-04-29 19:36:45.31 spid9 Opening file d:\SQL\data\dataname_Data.MDF.
> 2004-04-29 19:36:45.31 spid9 Opening file e:\SQL\data\dataname2_Data.NDF.
> 2004-04-29 19:36:45.31 spid9 The header for file 'e:\SQL\data\dataname2_Data.NDF' is not a valid database
file header. The PageAudit property is incorrect.
> 2004-04-29 19:36:45.32 spid9 Device activation error. The physical file name
'e:\SQL\data\dataname2_Data.NDF' may be incorrect.
> 2004-04-29 19:36:45.32 spid9 Opening file d:\SQL\data\dataname_Log.LDF.
> 2004-04-29 19:36:45.32 spid9 Opening file e:\SQL\data\dataname2_Log.LDF.
> System Details
> SQL Server 7
> NT 4
> Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model 0
> 4 * PIII 700 Mhz
> 2 GB RAM
> 40/80GB SCSI DLT Internal Tape Drive
> 9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
> 32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet Pro100+)
> Regards
> David

database failure to restore from NT backup

Hello,
Have you seen this from Microsoft ?
http://support.microsoft.com/default.aspx?scid=kb;en-
us;268481
J

>--Original Message--
>One of our customers had a problem with SQL Server 7. We
have instigated a work around, but they want to know what
the root cause was.
>Problem description
>It seems that they had disk problems, then wanted to
restore the database from a backup. They were not doing
backups to disk, just to shutting down the services &
doing a cold NT backup to tape.
>Error Details
>The server lost a disc (one of five from RAID5 array).
After it was fixed, the data was restored from a backup
tape and the following appeared in the SQL Server activity
log. The database was in suspect mode.
>2004-04-29 19:36:45.31 spid9 Starting up
database 'dataname'.
>2004-04-29 19:36:45.31 spid9 Opening file
d:\SQL\data\dataname_Data.MDF.
>2004-04-29 19:36:45.31 spid9 Opening file
e:\SQL\data\dataname2_Data.NDF.
>2004-04-29 19:36:45.31 spid9 The header for
file 'e:\SQL\data\dataname2_Data.NDF' is not a valid
database file header. The PageAudit property is incorrect.
>2004-04-29 19:36:45.32 spid9 Device activation error.
The physical file name 'e:\SQL\data\dataname2_Data.NDF'
may be incorrect.
>2004-04-29 19:36:45.32 spid9 Opening file
d:\SQL\data\dataname_Log.LDF.
>2004-04-29 19:36:45.32 spid9 Opening file
e:\SQL\data\dataname2_Log.LDF.
>System Details
>SQL Server 7
>NT 4
>Bull Express5800 180Ra-7 Rack P-III Xeon 700MHz/1MB Model
0
>4 * PIII 700 Mhz
>2 GB RAM
>40/80GB SCSI DLT Internal Tape Drive
>9.1GB Ultra 160/m SCSI HDD 7.2Krpm (1")
>32 bit PCI 10/100Mbps Ethernet Adapter (Intel Ethernet
Pro100+)
>Regards
>David
>.
>
Julie
Thanks for the link, but the customer says that the Bull RAID controller is a Milex, not Adaptec,
|||Ok, but does it use the Abaptec drivers such as graphics
tend to use the same ones ?
J

>--Original Message--
>Julie
>Thanks for the link, but the customer says that the Bull
RAID controller is a Milex, not Adaptec,
>.
>

database errors on dbcc

We had a failure of a machine, but got the .mdf file off only. The .ldf was
unrecoverable. After restoring it, and running dbcc checkdb i get these
errors (although all seems ok in the database otherwise)
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:46098). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:46099). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:46100). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:46101). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:46102). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:46103). The PageId in the
page header = (0:0).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46097) could not be processed.
See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1010102639, index ID 255, page (1:46097). Test
(m_freeCnt == freeCnt) failed. Values are 0 and 8094.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1010102639, index ID 255, page (1:46097). Test
(emptySlotCnt == 0) failed. Values are 1 and 0.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46098) could not be processed.
See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46099) could not be processed.
See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46100) could not be processed.
See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46101) could not be processed.
See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46102) could not be processed.
See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46103) could not be processed.
See other errors for details.
DBCC results for myDatabase.
CHECKDB found 0 allocation errors and 6 consistency errors not associated
with any single object.
_____
DC G
Hi,
First and best option is restore from the latest backup into a new database
and restore the transaction logs, because the data consistency would have
been
lost since the LDF file is lost/corrupted.
If you do not have any backup files then try the below options:
DBCC CHECKDB('dbname','REPAIR_REBUILD ')
if you still have errors then try using
DBCC CHECKDB('DBNAME','REPAIR_ALLOW_DATA_LOSS')
The above command can be ran only in single user mode and will result in
data loss. so the comamnd is not at all recommended.
Thanks
Hari
MCDBA
"DC Gringo" <dcgringo@.visiontechnology.net> wrote in message
news:OMuhAlDnEHA.1800@.TK2MSFTNGP15.phx.gbl...
> We had a failure of a machine, but got the .mdf file off only. The .ldf
> was
> unrecoverable. After restoring it, and running dbcc checkdb i get these
> errors (although all seems ok in the database otherwise)
>
>
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46098). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46099). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46100). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46101). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46102). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46103). The PageId in the
> page header = (0:0).
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46097) could not be processed.
> See other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1010102639, index ID 255, page (1:46097). Test
> (m_freeCnt == freeCnt) failed. Values are 0 and 8094.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1010102639, index ID 255, page (1:46097). Test
> (emptySlotCnt == 0) failed. Values are 1 and 0.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46098) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46099) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46100) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46101) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46102) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46103) could not be processed.
> See other errors for details.
> DBCC results for myDatabase.
> CHECKDB found 0 allocation errors and 6 consistency errors not associated
> with any single object.
> --
> _____
> DC G
>
|||The most recent update of Books Online has explicit recommendation for most error numbers. Search
for your error numbers in Books Online and see what the recommendations are. Also, you might want to
read:
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/
"DC Gringo" <dcgringo@.visiontechnology.net> wrote in message
news:OMuhAlDnEHA.1800@.TK2MSFTNGP15.phx.gbl...
> We had a failure of a machine, but got the .mdf file off only. The .ldf was
> unrecoverable. After restoring it, and running dbcc checkdb i get these
> errors (although all seems ok in the database otherwise)
>
>
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46098). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46099). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46100). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46101). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46102). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46103). The PageId in the
> page header = (0:0).
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46097) could not be processed.
> See other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1010102639, index ID 255, page (1:46097). Test
> (m_freeCnt == freeCnt) failed. Values are 0 and 8094.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1010102639, index ID 255, page (1:46097). Test
> (emptySlotCnt == 0) failed. Values are 1 and 0.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46098) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46099) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46100) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46101) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46102) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46103) could not be processed.
> See other errors for details.
> DBCC results for myDatabase.
> CHECKDB found 0 allocation errors and 6 consistency errors not associated
> with any single object.
> --
> _____
> DC G
>

database errors on dbcc

We had a failure of a machine, but got the .mdf file off only. The .ldf was
unrecoverable. After restoring it, and running dbcc checkdb i get these
errors (although all seems ok in the database otherwise)
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:46098). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:46099). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:46100). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:46101). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:46102). The PageId in the
page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:46103). The PageId in the
page header = (0:0).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46097) could not be processed.
See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1010102639, index ID 255, page (1:46097). Test
(m_freeCnt == freeCnt) failed. Values are 0 and 8094.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1010102639, index ID 255, page (1:46097). Test
(emptySlotCnt == 0) failed. Values are 1 and 0.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46098) could not be processed.
See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46099) could not be processed.
See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46100) could not be processed.
See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46101) could not be processed.
See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46102) could not be processed.
See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1010102639, index ID 255: Page (1:46103) could not be processed.
See other errors for details.
DBCC results for myDatabase.
CHECKDB found 0 allocation errors and 6 consistency errors not associated
with any single object.
--
_____
DC GHi,
First and best option is restore from the latest backup into a new database
and restore the transaction logs, because the data consistency would have
been
lost since the LDF file is lost/corrupted.
If you do not have any backup files then try the below options:
DBCC CHECKDB('dbname','REPAIR_REBUILD ')
if you still have errors then try using
DBCC CHECKDB('DBNAME','REPAIR_ALLOW_DATA_LOSS')
The above command can be ran only in single user mode and will result in
data loss. so the comamnd is not at all recommended.
Thanks
Hari
MCDBA
"DC Gringo" <dcgringo@.visiontechnology.net> wrote in message
news:OMuhAlDnEHA.1800@.TK2MSFTNGP15.phx.gbl...
> We had a failure of a machine, but got the .mdf file off only. The .ldf
> was
> unrecoverable. After restoring it, and running dbcc checkdb i get these
> errors (although all seems ok in the database otherwise)
>
>
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46098). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46099). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46100). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46101). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46102). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46103). The PageId in the
> page header = (0:0).
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46097) could not be processed.
> See other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1010102639, index ID 255, page (1:46097). Test
> (m_freeCnt == freeCnt) failed. Values are 0 and 8094.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1010102639, index ID 255, page (1:46097). Test
> (emptySlotCnt == 0) failed. Values are 1 and 0.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46098) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46099) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46100) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46101) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46102) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46103) could not be processed.
> See other errors for details.
> DBCC results for myDatabase.
> CHECKDB found 0 allocation errors and 6 consistency errors not associated
> with any single object.
> --
> _____
> DC G
>|||The most recent update of Books Online has explicit recommendation for most error numbers. Search
for your error numbers in Books Online and see what the recommendations are. Also, you might want to
read:
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/
"DC Gringo" <dcgringo@.visiontechnology.net> wrote in message
news:OMuhAlDnEHA.1800@.TK2MSFTNGP15.phx.gbl...
> We had a failure of a machine, but got the .mdf file off only. The .ldf was
> unrecoverable. After restoring it, and running dbcc checkdb i get these
> errors (although all seems ok in the database otherwise)
>
>
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46098). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46099). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46100). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46101). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46102). The PageId in the
> page header = (0:0).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page ID (1:46103). The PageId in the
> page header = (0:0).
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46097) could not be processed.
> See other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1010102639, index ID 255, page (1:46097). Test
> (m_freeCnt == freeCnt) failed. Values are 0 and 8094.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1010102639, index ID 255, page (1:46097). Test
> (emptySlotCnt == 0) failed. Values are 1 and 0.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46098) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46099) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46100) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46101) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46102) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1010102639, index ID 255: Page (1:46103) could not be processed.
> See other errors for details.
> DBCC results for myDatabase.
> CHECKDB found 0 allocation errors and 6 consistency errors not associated
> with any single object.
> --
> _____
> DC G
>sql