Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
    Bumped by Community user
5 Added the tags of (a) the relevant DBMS and (b) the corresponding DBMS version. Removed the SQL tag because it should be used for questions about the langauge itself. Modified formatting. Made some rewordings.
source | link

Suspect (Torn) Pages recorded in TEMPDBregarding tempdb? (SQL Server 2005 SP3)

I have a virtualised SQL Server 2005 (SP3) server that reported the following msgmessage:

Database_Name, Database_Id, File_Id, Event_Type, Event_Type_Desc, Error_Count, Last_Update_Date
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:033
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:043
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:050
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:057
...

It is the 2ndsecond time in the past month that I've seen this error on this particular server - and in both cases it was in tempdbtempdb, with Event_type = 3 Event_type = 3 (i.e. Torn Page) only. It has never been event_type=1Event_type = 1, which corresponds to an 823 (disk error) or 824 error.

Running the command:

DBCC CHECKDB WITH ALL_ERRORMSGS, PHYSICAL_ONLY

returns:

DBCC results for 'tempdb'.
DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'tempdb'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

In other words, everything seems fine, but why then is suspect pages getting recorded?

Other actions taken:

  • HDDScan / chkdsk run to make sure its not a drive error (there is also nothing relevant recorded in the windows event logs around the time of the error)  .

  • Page_VerifyPAGE_VERIFY is currently set to NONE (default?) - investigated the possibility of setting it to CHECKSUM, but that's only possible for tempdbtempdb in SQL2008SQL Server 2008 onwards.

  • stoppedStopped SQL server, deleted existing tempdb files, restarted it (based upon a comment in the question -> How might a corrupt partition in TempDB result in DBCC CHECKDB reporting no error

  • readRead the similar questions (to the right) but none of them are relevant  .

Is there anything else I should be checking / doing, or should I simply disregard this because its TempDB (i.e. transient data)?

Thanks for any assistance/input.

Suspect (Torn) Pages recorded in TEMPDB? (SQL Server 2005 SP3)

I have a virtualised SQL Server 2005 (SP3) server that reported the following msg:

Database_Name, Database_Id, File_Id, Event_Type, Event_Type_Desc, Error_Count, Last_Update_Date
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:033
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:043
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:050
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:057
...

It is the 2nd time in the past month that I've seen this error on this particular server - and in both cases it was in tempdb, with Event_type = 3 (i.e. Torn Page) only. It has never been event_type=1, which corresponds to an 823 (disk error) or 824 error.

Running the command:

DBCC CHECKDB WITH ALL_ERRORMSGS, PHYSICAL_ONLY

returns:

DBCC results for 'tempdb'.
DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'tempdb'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

In other words, everything seems fine, but why then is suspect pages getting recorded?

Other actions taken:

  • HDDScan / chkdsk run to make sure its not a drive error (there is also nothing relevant recorded in the windows event logs around the time of the error)  

  • Page_Verify is currently set to NONE (default?) - investigated the possibility of setting it to CHECKSUM, but that's only possible for tempdb in SQL2008 onwards.

  • stopped SQL server, deleted existing tempdb files, restarted it (based upon a comment in the question -> How might a corrupt partition in TempDB result in DBCC CHECKDB reporting no error

  • read the similar questions (to the right) but none of them are relevant  

Is there anything else I should be checking / doing, or should I simply disregard this because its TempDB (i.e. transient data)?

Thanks for any assistance/input.

Suspect (Torn) Pages regarding tempdb?

I have a virtualised SQL Server 2005 (SP3) that reported the following message:

Database_Name, Database_Id, File_Id, Event_Type, Event_Type_Desc, Error_Count, Last_Update_Date
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:033
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:043
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:050
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:057
...

It is the second time in the past month that I've seen this error on this particular server - and in both cases it was in tempdb, with Event_type = 3 (i.e. Torn Page) only. It has never been Event_type = 1, which corresponds to an 823 (disk error) or 824 error.

Running the command:

DBCC CHECKDB WITH ALL_ERRORMSGS, PHYSICAL_ONLY

returns:

DBCC results for 'tempdb'.
DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'tempdb'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

In other words, everything seems fine, but why then is suspect pages getting recorded?

Other actions taken:

  • HDDScan / chkdsk run to make sure its not a drive error (there is also nothing relevant recorded in the windows event logs around the time of the error).

  • PAGE_VERIFY is currently set to NONE (default?) - investigated the possibility of setting it to CHECKSUM, but that's only possible for tempdb in SQL Server 2008 onwards.

  • Stopped SQL server, deleted existing tempdb files, restarted it (based upon a comment in the question -> How might a corrupt partition in TempDB result in DBCC CHECKDB reporting no error

  • Read the similar questions (to the right) but none of them are relevant.

Is there anything else I should be checking / doing, or should I simply disregard this because its TempDB (i.e. transient data)?

Thanks for any assistance/input.

    Bumped by Community user
4 replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
source | link

I have a virtualised SQL Server 2005 (SP3) server that reported the following msg:

Database_Name, Database_Id, File_Id, Event_Type, Event_Type_Desc, Error_Count, Last_Update_Date
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:033
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:043
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:050
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:057
...

It is the 2nd time in the past month that I've seen this error on this particular server - and in both cases it was in tempdb, with Event_type = 3 (i.e. Torn Page) only. It has never been event_type=1, which corresponds to an 823 (disk error) or 824 error.

Running the command:

DBCC CHECKDB WITH ALL_ERRORMSGS, PHYSICAL_ONLY

returns:

DBCC results for 'tempdb'.
DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'tempdb'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

In other words, everything seems fine, but why then is suspect pages getting recorded?

Other actions taken:

Is there anything else I should be checking / doing, or should I simply disregard this because its TempDB (i.e. transient data)?

Thanks for any assistance/input.

I have a virtualised SQL Server 2005 (SP3) server that reported the following msg:

Database_Name, Database_Id, File_Id, Event_Type, Event_Type_Desc, Error_Count, Last_Update_Date
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:033
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:043
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:050
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:057
...

It is the 2nd time in the past month that I've seen this error on this particular server - and in both cases it was in tempdb, with Event_type = 3 (i.e. Torn Page) only. It has never been event_type=1, which corresponds to an 823 (disk error) or 824 error.

Running the command:

DBCC CHECKDB WITH ALL_ERRORMSGS, PHYSICAL_ONLY

returns:

DBCC results for 'tempdb'.
DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'tempdb'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

In other words, everything seems fine, but why then is suspect pages getting recorded?

Other actions taken:

  • HDDScan / chkdsk run to make sure its not a drive error (there is also nothing relevant recorded in the windows event logs around the time of the error)

  • Page_Verify is currently set to NONE (default?) - investigated the possibility of setting it to CHECKSUM, but that's only possible for tempdb in SQL2008 onwards.

  • stopped SQL server, deleted existing tempdb files, restarted it (based upon a comment in the question -> How might a corrupt partition in TempDB result in DBCC CHECKDB reporting no error

  • read the similar questions (to the right) but none of them are relevant

Is there anything else I should be checking / doing, or should I simply disregard this because its TempDB (i.e. transient data)?

Thanks for any assistance/input.

I have a virtualised SQL Server 2005 (SP3) server that reported the following msg:

Database_Name, Database_Id, File_Id, Event_Type, Event_Type_Desc, Error_Count, Last_Update_Date
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:033
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:043
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:050
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:057
...

It is the 2nd time in the past month that I've seen this error on this particular server - and in both cases it was in tempdb, with Event_type = 3 (i.e. Torn Page) only. It has never been event_type=1, which corresponds to an 823 (disk error) or 824 error.

Running the command:

DBCC CHECKDB WITH ALL_ERRORMSGS, PHYSICAL_ONLY

returns:

DBCC results for 'tempdb'.
DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'tempdb'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

In other words, everything seems fine, but why then is suspect pages getting recorded?

Other actions taken:

  • HDDScan / chkdsk run to make sure its not a drive error (there is also nothing relevant recorded in the windows event logs around the time of the error)

  • Page_Verify is currently set to NONE (default?) - investigated the possibility of setting it to CHECKSUM, but that's only possible for tempdb in SQL2008 onwards.

  • stopped SQL server, deleted existing tempdb files, restarted it (based upon a comment in the question -> How might a corrupt partition in TempDB result in DBCC CHECKDB reporting no error

  • read the similar questions (to the right) but none of them are relevant

Is there anything else I should be checking / doing, or should I simply disregard this because its TempDB (i.e. transient data)?

Thanks for any assistance/input.

    Bumped by Community user
    Bumped by Community user
    Tweeted twitter.com/#!/StackDBAs/status/545108166615531520
3 added 16 characters in body; edited title
source | link

Suspect (Torn) Pages recorded in TEMPDB? (SQL2005SQL Server 2005 SP3)

I have a virtualised SQL2005SQL Server 2005 (SP3) server that reported the following msg:

Database_Name, Database_Id, File_Id, Event_Type, Event_Type_Desc, Error_Count, Last_Update_Date
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:033
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:043
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:050
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:057
...

It is the 2nd time in the past month that I've seen this error on this particular server - and in both cases it was in tempdb, with Event_type = 3 (i.e. Torn Page) only. It has never been event_type=1, which corresponds to an 823 (disk error) or 824 error.

Running the command:

DBCC CHECKDB WITH ALL_ERRORMSGS, PHYSICAL_ONLY

returns:

DBCC results for 'tempdb'.
DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'tempdb'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

In other words, everything seems fine, but why then is suspect pages getting recorded?

Other actions taken:

  • HDDScan / chkdsk run to make sure its not a drive error (there is also nothing relevant recorded in the windows event logs around the time of the error)

    HDDScan / chkdsk run to make sure its not a drive error (there is also nothing relevant recorded in the windows event logs around the time of the error)

  • Page_Verify is currently set to NONE (default?) - investigated the possibility of setting it to CHECKSUM, but that's only possible for tempdb in SQL2008 onwards.

    Page_Verify is currently set to NONE (default?) - investigated the possibility of setting it to CHECKSUM, but that's only possible for tempdb in SQL2008 onwards.

  • stopped SQL server, deleted existing tempdb files, restarted it (based upon a comment in the question -> How might a corrupt partition in TempDB result in DBCC CHECKDB reporting no error

    stopped SQL server, deleted existing tempdb files, restarted it (based upon a comment in the question -> How might a corrupt partition in TempDB result in DBCC CHECKDB reporting no error

  • read the similar questions (to the right) but none of them are relevant

    read the similar questions (to the right) but none of them are relevant

Is there anything else I should be checking / doing, or should I simply disregard this because its TempDB (i.e. transient data)?

Thanks for any assistance/input.

Suspect (Torn) Pages recorded in TEMPDB? (SQL2005 SP3)

I have a virtualised SQL2005 (SP3) server that reported the following msg:

Database_Name, Database_Id, File_Id, Event_Type, Event_Type_Desc, Error_Count, Last_Update_Date
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:033
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:043
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:050
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:057
...

It is the 2nd time in the past month that I've seen this error on this particular server - and in both cases it was in tempdb, with Event_type = 3 (i.e. Torn Page) only. It has never been event_type=1, which corresponds to an 823 (disk error) or 824 error.

Running the command:

DBCC CHECKDB WITH ALL_ERRORMSGS, PHYSICAL_ONLY

returns:

DBCC results for 'tempdb'.
DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'tempdb'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

In other words, everything seems fine, but why then is suspect pages getting recorded?

Other actions taken:

  • HDDScan / chkdsk run to make sure its not a drive error (there is also nothing relevant recorded in the windows event logs around the time of the error)
  • Page_Verify is currently set to NONE (default?) - investigated the possibility of setting it to CHECKSUM, but that's only possible for tempdb in SQL2008 onwards.
  • stopped SQL server, deleted existing tempdb files, restarted it (based upon a comment in the question -> How might a corrupt partition in TempDB result in DBCC CHECKDB reporting no error
  • read the similar questions (to the right) but none of them are relevant

Is there anything else I should be checking / doing, or should I simply disregard this because its TempDB (i.e. transient data)?

Thanks for any assistance/input.

Suspect (Torn) Pages recorded in TEMPDB? (SQL Server 2005 SP3)

I have a virtualised SQL Server 2005 (SP3) server that reported the following msg:

Database_Name, Database_Id, File_Id, Event_Type, Event_Type_Desc, Error_Count, Last_Update_Date
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:033
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:043
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:050
tempdb, 2, 1, 3, Torn page., 1, 10 Dec 2014 06:32:36:057
...

It is the 2nd time in the past month that I've seen this error on this particular server - and in both cases it was in tempdb, with Event_type = 3 (i.e. Torn Page) only. It has never been event_type=1, which corresponds to an 823 (disk error) or 824 error.

Running the command:

DBCC CHECKDB WITH ALL_ERRORMSGS, PHYSICAL_ONLY

returns:

DBCC results for 'tempdb'.
DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'tempdb'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

In other words, everything seems fine, but why then is suspect pages getting recorded?

Other actions taken:

  • HDDScan / chkdsk run to make sure its not a drive error (there is also nothing relevant recorded in the windows event logs around the time of the error)

  • Page_Verify is currently set to NONE (default?) - investigated the possibility of setting it to CHECKSUM, but that's only possible for tempdb in SQL2008 onwards.

  • stopped SQL server, deleted existing tempdb files, restarted it (based upon a comment in the question -> How might a corrupt partition in TempDB result in DBCC CHECKDB reporting no error

  • read the similar questions (to the right) but none of them are relevant

Is there anything else I should be checking / doing, or should I simply disregard this because its TempDB (i.e. transient data)?

Thanks for any assistance/input.

2 fixed typo
source | link
1
source | link