614 error on a user database and 806 error on tempdb seen in the error log

[Anu]

Hi,

We have a production SQLServer 6.5 running with service pack SP5a update:

I got the following 2 errors.....

1.

Error : 806, Severity: 21, State: 1
Could not find virtual page for logical page 67833121 in database 'tempdb' database 'tempdb'

2.

I got error when I ran a job for Update statistics
Error : 614, Severity: 21, State: 3
A row on page 2697653 was accessed that has an illegal length of -8631 in database 'abc'.

For Error 2: I ran update statistics using query analyser. It is fine
Is there anything I have to do further?


For Error 1 : The work around given by Microsoft
=================================================
I ran
DBCC CHECKTABLE(syslogs)

I am getting the following message on :
master:
Checking syslogs
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 11 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

model:
Checking syslogs
The total number of data pages in this table is 47.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 532 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

tempdb:

Checking syslogs
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 31 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

I ran dbcc checkdb on master,model and tempdb . Still I get the same problem.

for tempdb:

Checking 8
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 19 data rows.

for master:
Checking 8
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 27 data rows.

for model:
Checking 8
The total number of data pages in this table is 47.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 532 data rows.

All system databases and userdatabase recovered successfully when I restarted sqlserver.

Please advice how to get rid of this problem.


Thanks in advance,
Anu

[Juergen Leis]

Error 1: should be vanished after you restart your server
because SQL Server rebuilds tempdb at start.

Error 2: Use DBCC PAGE to identify the object (if you dont't know it already)



------------
Anu at 1/5/2002 11:22:51 AM

Hi,

We have a production SQLServer 6.5 running with service pack SP5a update:

I got the following 2 errors.....

1.

Error : 806, Severity: 21, State: 1
Could not find virtual page for logical page 67833121 in database 'tempdb' database 'tempdb'

2.

I got error when I ran a job for Update statistics
Error : 614, Severity: 21, State: 3
A row on page 2697653 was accessed that has an illegal length of -8631 in database 'abc'.

For Error 2: I ran update statistics using query analyser. It is fine
Is there anything I have to do further?


For Error 1 : The work around given by Microsoft
=================================================
I ran
DBCC CHECKTABLE(syslogs)

I am getting the following message on :
master:
Checking syslogs
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 11 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

model:
Checking syslogs
The total number of data pages in this table is 47.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 532 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

tempdb:

Checking syslogs
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 31 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

I ran dbcc checkdb on master,model and tempdb . Still I get the same problem.

for tempdb:

Checking 8
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 19 data rows.

for master:
Checking 8
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 27 data rows.

for model:
Checking 8
The total number of data pages in this table is 47.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 532 data rows.

All system databases and userdatabase recovered successfully when I restarted sqlserver.

Please advice how to get rid of this problem.


Thanks in advance,
Anu

[Juergen Leis]

Error 1: should be vanished after you restart your server
because SQL Server rebuilds tempdb at start.

Error 2: Use DBCC PAGE to identify the object (if you dont't know it already)



------------
Anu at 1/5/2002 11:22:51 AM

Hi,

We have a production SQLServer 6.5 running with service pack SP5a update:

I got the following 2 errors.....

1.

Error : 806, Severity: 21, State: 1
Could not find virtual page for logical page 67833121 in database 'tempdb' database 'tempdb'

2.

I got error when I ran a job for Update statistics
Error : 614, Severity: 21, State: 3
A row on page 2697653 was accessed that has an illegal length of -8631 in database 'abc'.

For Error 2: I ran update statistics using query analyser. It is fine
Is there anything I have to do further?


For Error 1 : The work around given by Microsoft
=================================================
I ran
DBCC CHECKTABLE(syslogs)

I am getting the following message on :
master:
Checking syslogs
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 11 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

model:
Checking syslogs
The total number of data pages in this table is 47.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 532 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

tempdb:

Checking syslogs
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 31 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

I ran dbcc checkdb on master,model and tempdb . Still I get the same problem.

for tempdb:

Checking 8
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 19 data rows.

for master:
Checking 8
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 27 data rows.

for model:
Checking 8
The total number of data pages in this table is 47.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 532 data rows.

All system databases and userdatabase recovered successfully when I restarted sqlserver.

Please advice how to get rid of this problem.


Thanks in advance,
Anu

[Juergen Leis]

Error 1:
Should be vanished after you restart your server
because SQL Server rebuilds tempdb at start.

Error 2:
Use DBCC PAGE to identify the object (if you dont't know it already)
and/or DBCC CHECKTABLE with this object ID to identify whether it is an
index or the table itself.
If it is an Index, simply drop and recreate the index.
If it is the Table you should copy your table to a new table
(INSERT SELECT, bcp out + bcp in etc.)
then drop the table and rename the new table to the old name.

BTW: If you can restore and recover vom checked Database and transaction log
backups, this would be the safest way.

The message
*** NOTICE: Notification of log space used/free cannot be reported
because the log segment is not on its own device.
is by design (it is NOT an error) because you didn't place your logs
on separate devices (which you should do for your user databases).
system databases (master, model, tempdb) are on one device after install.

------------
Anu at 1/5/2002 11:22:51 AM

Hi,

We have a production SQLServer 6.5 running with service pack SP5a update:

I got the following 2 errors.....

1.

Error : 806, Severity: 21, State: 1
Could not find virtual page for logical page 67833121 in database 'tempdb' database 'tempdb'

2.

I got error when I ran a job for Update statistics
Error : 614, Severity: 21, State: 3
A row on page 2697653 was accessed that has an illegal length of -8631 in database 'abc'.

For Error 2: I ran update statistics using query analyser. It is fine
Is there anything I have to do further?


For Error 1 : The work around given by Microsoft
=================================================
I ran
DBCC CHECKTABLE(syslogs)

I am getting the following message on :
master:
Checking syslogs
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 11 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

model:
Checking syslogs
The total number of data pages in this table is 47.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 532 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

tempdb:

Checking syslogs
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 31 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

I ran dbcc checkdb on master,model and tempdb . Still I get the same problem.

for tempdb:

Checking 8
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 19 data rows.

for master:
Checking 8
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 27 data rows.

for model:
Checking 8
The total number of data pages in this table is 47.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 532 data rows.

All system databases and userdatabase recovered successfully when I restarted sqlserver.

Please advice how to get rid of this problem.


Thanks in advance,
Anu

[Anu]

Thanks for explaining very detail.

For Error 1:
I ran the dbcc checks on all the database including tempdb.
I saw 2 objects corrupted on tempdb. It went off after running dbcc checks.

For Error 2:
After doing DBCC checks on all the databases, I ran the update statistics.

Now everything is fine.

Thanks again
-Anu



------------
Juergen Leis at 1/8/2002 7:07:41 AM

Error 1:
Should be vanished after you restart your server
because SQL Server rebuilds tempdb at start.

Error 2:
Use DBCC PAGE to identify the object (if you dont't know it already)
and/or DBCC CHECKTABLE with this object ID to identify whether it is an
index or the table itself.
If it is an Index, simply drop and recreate the index.
If it is the Table you should copy your table to a new table
(INSERT SELECT, bcp out + bcp in etc.)
then drop the table and rename the new table to the old name.

BTW: If you can restore and recover vom checked Database and transaction log
backups, this would be the safest way.

The message
*** NOTICE: Notification of log space used/free cannot be reported
because the log segment is not on its own device.
is by design (it is NOT an error) because you didn't place your logs
on separate devices (which you should do for your user databases).
system databases (master, model, tempdb) are on one device after install.

------------
Anu at 1/5/2002 11:22:51 AM

Hi,

We have a production SQLServer 6.5 running with service pack SP5a update:

I got the following 2 errors.....

1.

Error : 806, Severity: 21, State: 1
Could not find virtual page for logical page 67833121 in database 'tempdb' database 'tempdb'

2.

I got error when I ran a job for Update statistics
Error : 614, Severity: 21, State: 3
A row on page 2697653 was accessed that has an illegal length of -8631 in database 'abc'.

For Error 2: I ran update statistics using query analyser. It is fine
Is there anything I have to do further?


For Error 1 : The work around given by Microsoft
=================================================
I ran
DBCC CHECKTABLE(syslogs)

I am getting the following message on :
master:
Checking syslogs
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 11 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

model:
Checking syslogs
The total number of data pages in this table is 47.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 532 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

tempdb:

Checking syslogs
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 31 data rows.
DBCC execution completed. If DBCC printed error messages, see your System Administrator.

I ran dbcc checkdb on master,model and tempdb . Still I get the same problem.

for tempdb:

Checking 8
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 19 data rows.

for master:
Checking 8
The total number of data pages in this table is 1.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 27 data rows.

for model:
Checking 8
The total number of data pages in this table is 47.
*** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.
Table has 532 data rows.

All system databases and userdatabase recovered successfully when I restarted sqlserver.

Please advice how to get rid of this problem.


Thanks in advance,
Anu