error 823

Hello all,
I am fighting this error for a month now.I will explain:It started with the followying steps:

1 Could not allocate space for object '(SYSTEM table id: -789977678)' in database 'TEMPDB' because the 'DEFAULT' filegroup is full..Error: 1105, Severity: 17, State: 2

2 SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Error: 3624, Severity: 20, State: 1.

3 I/O error (bad page ID) detected during read at offset 0x000000bf074000 in file 'f:\SQL data files\data files\dw_prod.mdf'..
Error: 823, Severity: 24, State: 2

4 DBCC CHECKDB (dw_prod) executed by sa found 7 errors and repaired 0 errors.

5 DBCC CHECKDB (dw_prod, repair_rebuild) executed by sa found 7 errors and repaired 0 errors.

6 DBCC CHECKDB (dw_prod, repair_allow_data_loss) executed by sa found 7 errors and repaired 7 errors.

-- AFTER DBCC CHECKB--therefore in reality the error wasnot corrected--

7 I/O error (bad page ID) detected during read at offset 0x00000091d3a000 in file 'f:\SQL data files\data files\dw_prod.mdf'..
Error: 823, Severity: 24, State: 2

8 SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Error: 3624, Severity: 20, State: 1.

9 I/O error (bad page ID) detected during read at offset 0x00000091d36000 in file 'f:\SQL data files\data files\dw_prod.mdf'..

10 DBCC CHECKDB (dw_prod, repair_allow_data_loss) executed by sa found 24 errors and repaired 24 errors.

11 I/O error (bad page ID) detected during read at offset 0x000000f6994000 in file 'f:\SQL data files\data files\dw_prod.mdf'..
Error: 823, Severity: 24, State: 2

12 I finally had no other solution than to recover from a good backup (100 G database) - BUT my network admin considers that his hardware is well and WE DID NOT CHECK THE damn HARDWARE!!!!

13 24 H after again I/O error (bad page ID) detected during read at offset 0x0000009d456000 in file 'f:\SQL data files\data files\dw_prod.mdf'..

14 another recovery OK

15

1313 Could not allocate space for object '(SYSTEM table id: -219347948)' in database 'TEMPDB' because the 'DEFAULT' filegroup is full..

14 I/O error (bad page ID) detected during read at offset 0x000000440d0000 in file 'f:\SQL data files\data files\dw_prod.mdf'..

15 dbcc checkdb finds nothing

My question is:

- what I am going to do next? I have recovered now, all went well till the tempdb was not running out of space... I am in the process of checking the hardware

- please say what you think about this.I have never experienced such a pain!

Thanks

LMT|||I had the infamous 823 errors not long ago. In our case, it was a bad raid controller. Poke through your System event logs for error number 50 or 55. Thes can mean some disk problem. Unfortunately, some disk problem can be anything from the mainboard up to the spindle of the disk itself. Since the only moving part is the disk, you should start there, and do a full disk check for bad sectors and such. There are usually vendor specific utilities that should be used for that, so I am afraid I can not help you much further than that. Good luck.|||thanks

is it possible that this 832error to be determined partly bi a tempdb running out of space??

in my case most of errors came after the temdb ran out of space

lmt|||is tempdb also sitting on f: drive?

check your system log in event viewer. that's a darn good place to start. keep a log of dates and times from sql errorlog in front of you while going through system log and see if there were any io subsystem-related errors.

also, put tempdb onto a different drive. always a good idea to keep that bad boy separate. raid-0 for this guy is more than enough. i'd put it on a separate controller as well, preferrably a faster one.

Error 56

This morning, within the space of just a few minutes, we got a WHOLE lot of
these errors:
Event Type: Warning
Event Source: mraid35x
Event Category: None
Event ID: 56
Date: 1/27/2005
Time: 7:06:27 AM
User: N/A
Computer: SQL
Description:
The driver failed to allocate memory.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 10 00 01 00 66 00 .....f.
0008: 00 00 00 00 38 00 04 80 ...8..?
0010: 10 00 00 00 9a 00 00 c0 ...?..À
0018: 00 00 00 00 00 00 00 00 ......
0020: 00 00 00 00 00 00 00 00 ......
0028: 53 63 50 44 e0 01 00 00 ScPDà...
0030: 6c 69 74 75 b4 06 00 00 litu´...
I can't find any information regarding this error. We're running SQL on a
Windows 2003 server.
Thank you for your attention
mHello
Well, the first thing we are going to want to do is run chkdsk /f /r on the
server
to hopefully clear up the NTFS and FTDISK errors on the drive.
This will require a server reboot and could take over an hour to complete.
Next, we need you to delete and recreate your pagefile.sys. To do this,
1) When the Chkdsk.exe utility has completed, set the paging file size to 0.
a. Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b. In the Initial Size (MB): box, type "0" (without the quotation marks).
c. In the Maximum Size (MB): box, type "0" (without the quotation marks).
d. Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
2) After the computer has restarted, reset the Pagefile.sys file to the
correct
size.
a. Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b. In the Initial Size (MB): box, type a value equal to the amount of
random
access memory (in megabytes) in your computer plus 11.
c. In the Maximum Size (MB): box, type a value equal to or less than the
amount of
disk space available (in megabytes) on the specified partition minus 1.
d. Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
Hopefully this will correct the NTFS, FTDISK, and errors with your Promise
Controller.
If not, we will need to continue investigating further and review your next
memory.dmp file.
Let me know when you have completed the above actions.
Best Regards,
Regev Avivi (Mcse)
http://www.regevnet.com
<-- Please reply to the NewsGroup only -->

Error 56

This morning, within the space of just a few minutes, we got a WHOLE lot of
these errors:
Event Type: Warning
Event Source: mraid35x
Event Category: None
Event ID: 56
Date: 1/27/2005
Time: 7:06:27 AM
User: N/A
Computer: SQL
Description:
The driver failed to allocate memory.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 10 00 01 00 66 00 .....f.
0008: 00 00 00 00 38 00 04 80 ...8..
0010: 10 00 00 00 9a 00 00 c0 .....
0018: 00 00 00 00 00 00 00 00 ......
0020: 00 00 00 00 00 00 00 00 ......
0028: 53 63 50 44 e0 01 00 00 ScPD...
0030: 6c 69 74 75 b4 06 00 00 litu...
I can't find any information regarding this error. We're running SQL on a
Windows 2003 server.
Thank you for your attention
mHello
Well, the first thing we are going to want to do is run chkdsk /f /r on the
server
to hopefully clear up the NTFS and FTDISK errors on the drive.
This will require a server reboot and could take over an hour to complete.
Next, we need you to delete and recreate your pagefile.sys. To do this,
1) When the Chkdsk.exe utility has completed, set the paging file size to 0.
a. Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b. In the Initial Size (MB): box, type "0" (without the quotation marks).
c. In the Maximum Size (MB): box, type "0" (without the quotation marks).
d. Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
2) After the computer has restarted, reset the Pagefile.sys file to the
correct
size.
a. Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b. In the Initial Size (MB): box, type a value equal to the amount of
random
access memory (in megabytes) in your computer plus 11.
c. In the Maximum Size (MB): box, type a value equal to or less than the
amount of
disk space available (in megabytes) on the specified partition minus 1.
d. Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
Hopefully this will correct the NTFS, FTDISK, and errors with your Promise
Controller.
If not, we will need to continue investigating further and review your next
memory.dmp file.
Let me know when you have completed the above actions.
Best Regards,
Regev Avivi (Mcse)
http://www.regevnet.com
<-- Please reply to the NewsGroup only -->

Error 56

This morning, within the space of just a few minutes, we got a WHOLE lot of
these errors:
Event Type: Warning
Event Source: mraid35x
Event Category: None
Event ID: 56
Date: 1/27/2005
Time: 7:06:27 AM
User: N/A
Computer: SQL
Description:
The driver failed to allocate memory.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 10 00 01 00 66 00 .....f.
0008: 00 00 00 00 38 00 04 80 ...8..
0010: 10 00 00 00 9a 00 00 c0 .....
0018: 00 00 00 00 00 00 00 00 ......
0020: 00 00 00 00 00 00 00 00 ......
0028: 53 63 50 44 e0 01 00 00 ScPD...
0030: 6c 69 74 75 b4 06 00 00 litu...
I can't find any information regarding this error. We're running SQL on a
Windows 2003 server.
Thank you for your attention
m
Hello
Well, the first thing we are going to want to do is run chkdsk /f /r on the
server
to hopefully clear up the NTFS and FTDISK errors on the drive.
This will require a server reboot and could take over an hour to complete.
Next, we need you to delete and recreate your pagefile.sys. To do this,
1) When the Chkdsk.exe utility has completed, set the paging file size to 0.
a.Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b.In the Initial Size (MB): box, type "0" (without the quotation marks).
c.In the Maximum Size (MB): box, type "0" (without the quotation marks).
d.Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
2) After the computer has restarted, reset the Pagefile.sys file to the
correct
size.
a.Click Start, point to Settings, click Control Panel, and then
double-click
System. Click the Performance tab, click Change, and then point to the
partition
containing the Pagefile.sys file.
b.In the Initial Size (MB): box, type a value equal to the amount of
random
access memory (in megabytes) in your computer plus 11.
c.In the Maximum Size (MB): box, type a value equal to or less than the
amount of
disk space available (in megabytes) on the specified partition minus 1.
d.Click Set, click OK, click Close, and then click Yes when you are
prompted to
restart the computer.
Hopefully this will correct the NTFS, FTDISK, and errors with your Promise
Controller.
If not, we will need to continue investigating further and review your next
memory.dmp file.
Let me know when you have completed the above actions.
Best Regards,
Regev Avivi (Mcse)
http://www.regevnet.com
<-- Please reply to the NewsGroup only -->

Error 5149: Not enough disk space

Newbie question:
Importing a 25,000,000 record .csv file into SQL2000 fails
with a disk space error. I go into sql enterprise manager
to increase the size of the database and it will only let
me go to about 4000 MB. I need about 30GIG. At 5000 MB
enterprise manager says:
Error 5149: ModifyFile encountered operating system error
112 (There is not enough space on the disk while
attempting to expand physical file).
I have 50GIG free on that disk.
What am I doing wrong'"Ben Silvert" <anonymous@.discussions.microsoft.com> wrote in message
news:1be701c39fc7$d4faa450$3101280a@.phx.gbl...
> Newbie question:
> Importing a 25,000,000 record .csv file into SQL2000 fails
> with a disk space error. I go into sql enterprise manager
> to increase the size of the database and it will only let
> me go to about 4000 MB. I need about 30GIG. At 5000 MB
> enterprise manager says:
> Error 5149: ModifyFile encountered operating system error
> 112 (There is not enough space on the disk while
> attempting to expand physical file).
> I have 50GIG free on that disk.
> What am I doing wrong'
It's possible that you are either running out of transaction log space (on
either the target database) or on tempdb -- check that you have enabled
database file autogrow, or have size the database large enough to hold the
imported data (my preference).
If this fails, you may want to watch the server os page file (performance
monitor) in case the os is swapping out memory to disk...
Steve|||I'm getting this error when I go into properties of the
database, Data Files tab, Space Allocated (MB) column. I
try to change the entry from 4000 to 5000, and it gives me
the 5149 error. I'm not trying to import the data, yet.
When I tried before to import the data it failed with a
message the Primary File Group ran out of space. So I
deleted the database, made a new one, and tried to set the
data file size, to no avail.
The database is set to grow automatically, and it grows
unlimited.
>--Original Message--
>"Ben Silvert" <anonymous@.discussions.microsoft.com> wrote
in message
>news:1be701c39fc7$d4faa450$3101280a@.phx.gbl...
>> Newbie question:
>> Importing a 25,000,000 record .csv file into SQL2000
fails
>> with a disk space error. I go into sql enterprise
manager
>> to increase the size of the database and it will only
let
>> me go to about 4000 MB. I need about 30GIG. At 5000 MB
>> enterprise manager says:
>> Error 5149: ModifyFile encountered operating system
error
>> 112 (There is not enough space on the disk while
>> attempting to expand physical file).
>> I have 50GIG free on that disk.
>> What am I doing wrong'
>It's possible that you are either running out of
transaction log space (on
>either the target database) or on tempdb -- check that
you have enabled
>database file autogrow, or have size the database large
enough to hold the
>imported data (my preference).
>If this fails, you may want to watch the server os page
file (performance
>monitor) in case the os is swapping out memory to disk...
>Steve
>
>.
>|||Could it be the version of SQL? I have the personal
edition?
>--Original Message--
>Newbie question:
>Importing a 25,000,000 record .csv file into SQL2000
fails
>with a disk space error. I go into sql enterprise manager
>to increase the size of the database and it will only let
>me go to about 4000 MB. I need about 30GIG. At 5000 MB
>enterprise manager says:
>Error 5149: ModifyFile encountered operating system error
>112 (There is not enough space on the disk while
>attempting to expand physical file).
>I have 50GIG free on that disk.
>What am I doing wrong'
>.
>

Error 3140 on SQL Server 2000

When I do shrink trans log file or database error message came out "Error
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.
Bin,
How are you trying to shrink this log? What other steps have you taken before trying to shrink? Are you doing this from enterprise manage or through query analyzer?
Please post the exact error message here and someone may be able to assist.
Tunji O
"BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B628FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
When I do shrink trans log file or database error message came out "Error
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.
|||I shrink data through SQL Server Enterprise Manager All Tasks Shrink Database
task the error message as follow:
Microsoft SQL-DMO(ODBC SQLSTATE:42000)
Error 3140:Could not adjust the space allocation for the file'truck_data'.
DBCC execution completeed. If DBCC printed error messages, contact your
system administrator.
"Tunji" wrote:

> Bin,
> How are you trying to shrink this log? What other steps have you taken before trying to shrink? Are you doing this from enterprise manage or through query analyzer?
> Please post the exact error message here and someone may be able to assist.
> Tunji O
> "BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B628FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
> When I do shrink trans log file or database error message came out "Error
> 3140 Could not adjust the space allocation for the file". I search on
> Microsoft WEB only show SQL 7.0. Can someone help me please I already
> installed SP3 for it

Error 3140 on SQL Server 2000

When I do shrink trans log file or database error message came out "Error
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.Bin,
How are you trying to shrink this log? What other steps have you taken befor
e trying to shrink? Are you doing this from enterprise manage or through que
ry analyzer?
Please post the exact error message here and someone may be able to assist.
Tunji O
"BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B628FE
5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
When I do shrink trans log file or database error message came out "Error
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.|||I shrink data through SQL Server Enterprise Manager All Tasks Shrink Databas
e
task the error message as follow:
Microsoft SQL-DMO(ODBC SQLSTATE:42000)
Error 3140:Could not adjust the space allocation for the file'truck_data'.
DBCC execution completeed. If DBCC printed error messages, contact your
system administrator.
"Tunji" wrote:

> Bin,
> How are you trying to shrink this log? What other steps have you taken bef
ore trying to shrink? Are you doing this from enterprise manage or through q
uery analyzer?
> Please post the exact error message here and someone may be able to assist
.
> Tunji O
> "BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B6
28FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
> When I do shrink trans log file or database error message came out "Erro
r
> 3140 Could not adjust the space allocation for the file". I search on
> Microsoft WEB only show SQL 7.0. Can someone help me please I already
> installed SP3 for it

Error 3140 on SQL Server 2000

When I do shrink trans log file or database error message came out "Error
3140 Could not adjust the space allocation for the file". I search on
Microsoft WEB only show SQL 7.0. Can someone help me please I already
installed SP3 for it.This is a multi-part message in MIME format.
--=_NextPart_000_008A_01C4CCFC.9D0630B0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
Bin,
How are you trying to shrink this log? What other steps have you taken =before trying to shrink? Are you doing this from enterprise manage or =through query analyzer? Please post the exact error message here and someone may be able to =assist.
Tunji O
"BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message =news:8B628FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
When I do shrink trans log file or database error message came out ="Error 3140 Could not adjust the space allocation for the file". I search on Microsoft WEB only show SQL 7.0. Can someone help me please I already installed SP3 for it.
--=_NextPart_000_008A_01C4CCFC.9D0630B0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Bin,
How are you trying to shrink this log? =What other steps have you taken before trying to shrink? Are you doing this from =enterprise manage or through query analyzer?
Please post the exact error message =here and someone may be able to assist.
Tunji O
"BIN YANG" wrote in message news:8B6=28FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...When I do shrink trans log file or database error message came out "Error =3140 Could not adjust the space allocation for the file". I search on =Microsoft WEB only show SQL 7.0. Can someone help me please I already =installed SP3 for it.

---

--=_NextPart_000_008A_01C4CCFC.9D0630B0--|||I shrink data through SQL Server Enterprise Manager All Tasks Shrink Database
task the error message as follow:
Microsoft SQL-DMO(ODBC SQLSTATE:42000)
Error 3140:Could not adjust the space allocation for the file'truck_data'.
DBCC execution completeed. If DBCC printed error messages, contact your
system administrator.
"Tunji" wrote:
> Bin,
> How are you trying to shrink this log? What other steps have you taken before trying to shrink? Are you doing this from enterprise manage or through query analyzer?
> Please post the exact error message here and someone may be able to assist.
> Tunji O
> "BIN YANG" <BINYANG@.discussions.microsoft.com> wrote in message news:8B628FE5-842E-4A14-9331-2BA683E3F97B@.microsoft.com...
> When I do shrink trans log file or database error message came out "Error
> 3140 Could not adjust the space allocation for the file". I search on
> Microsoft WEB only show SQL 7.0. Can someone help me please I already
> installed SP3 for it