MS SQL Server - DBCC checkdb error Msg 2574, Level 16, State 1, Line 1

Author

DBCC checkdb error Msg 2574, Level 16, State 1, Line 1

Koni Kogan

2005-05-31, 11:23 am

Hi, All.
I am wondering if anyone has seen this error before:

dbcc checkdb ("EMIOPER")
Server: Msg 2574, Level 16, State 1, Line 1
Object ID 1112703362, index ID 1: Page (1:1688519) is empty. This is not
permitted at level 2 of the B-tree.
DBCC results for 'EMIOPER'.

select object_name(11127033
62) returns spaces.

Thanks in advance,
Koni.

Hari Prasad

2005-05-31, 8:23 pm

Hi,

Looks like this error is come thing new:-

1. backup the database and try to drop and recreate all the indexes
2. After that try to execute the DBCC Checkdb again

If the problem still persits then try to restore from the latest good backup
or open a case with Microsoft PSS.

Thanks
Hari
SQL Server MVP

"Koni Kogan" <kkogan@haiint.com> wrote in message
news:uvtELVfZFHA.3048@TK2MSFTNGP14.phx.gbl...
> Hi, All.
> I am wondering if anyone has seen this error before:
>
> dbcc checkdb ("EMIOPER")
> Server: Msg 2574, Level 16, State 1, Line 1
> Object ID 1112703362, index ID 1: Page (1:1688519) is empty. This is not
> permitted at level 2 of the B-tree.
> DBCC results for 'EMIOPER'.
>
> select object_name(11127033
62) returns spaces.
>
> Thanks in advance,
> Koni.

Tibor Karaszi

2005-05-31, 8:23 pm

> select object_name(11127033
62) returns spaces.

Are you in the right database when running above? If you spot the table, it sounds like dropping the
clustered index should cut it. But BOL has another oppinion (see BOL text below). Of course, you
want to know why this happened in the first place:
http://www.karaszi.com/SQLServer/ i...t
_db.asp

And here's BOL recommendations for 2574:

Severity Level 10
Message Text
Object ID O_ID, index ID I_ID: Page P_ID is empty. This is not permitted at level LEVEL of the
B-tree.

Explanation
A B-tree page above the leaf level is empty (that is, it has no rows). This used to be possible for
leaf level pages, but has never been possible in tree levels.

Action
Run hardware diagnostics and correct any problems. Also examine the Microsoft® Windows NT® system
and application logs and the SQL ServerT error log to see if the error occurred as the result of
hardware failure. Fix any hardware related problems.

If you have persistent data corruption problems, try to swap out different hardware components to
isolate the problem. Check to ensure that your system does not have write caching enabled on the
disk controller. If you suspect this to be the problem, contact your hardware vendor.

Finally, you might find it beneficial to switch to a completely new hardware system, including
reformatting the disk drives and reinstalling the operating system.

RESTORE FROM BACKUP

If the problem is not hardware related and a known clean backup is available, restore the database
from the backup.

DBCC CHECKDB

If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the
extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC
CHECKDB with the appropriate repair clause to repair the corruption.

Caution If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact
your primary support provider before executing this statement.

Performing a repair will rebuild the index. If running DBCC CHECKDB with one of the repair clauses
does not correct the problem, contact your primary support provider.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www. solidqualitylearning
.com/

"Koni Kogan" <kkogan@haiint.com> wrote in message news:uvtELVfZFHA.3048@TK2MSFTNGP14.phx.gbl...
> Hi, All.
> I am wondering if anyone has seen this error before:
>
> dbcc checkdb ("EMIOPER")
> Server: Msg 2574, Level 16, State 1, Line 1
> Object ID 1112703362, index ID 1: Page (1:1688519) is empty. This is not permitted at level 2 of
> the B-tree.
> DBCC results for 'EMIOPER'.
>
> select object_name(11127033
62) returns spaces.
>
> Thanks in advance,
> Koni.

SkyWalker

2005-05-31, 8:23 pm

This is can be a hardware issue.
There are some explanations and workarounds:
http://msdn.microsoft.com/library/d...60l0
.asp

Regards.

"Koni Kogan" wrote:

> Hi, All.
> I am wondering if anyone has seen this error before:
>
> dbcc checkdb ("EMIOPER")
> Server: Msg 2574, Level 16, State 1, Line 1
> Object ID 1112703362, index ID 1: Page (1:1688519) is empty. This is not
> permitted at level 2 of the B-tree.
> DBCC results for 'EMIOPER'.
>
> select object_name(11127033
62) returns spaces.
>
> Thanks in advance,
> Koni.
>

Sponsored Links