August 16, 2016 at 4:24 am
Hi Experts,
Got some data in msdb.dbo.suspect_pages table. Ran DBCC CHECKDB on that particular DB an it returned nothing. The file_id is showing as Log file. What action to take if the same happens in future for data or log file?
database_idfile_idpage_idevent_typeerror_countlast_update_date
522312016-07-28 16:44:20.090
523112016-07-28 16:44:20.093
526112016-07-28 16:44:20.097
527112016-07-28 16:44:20.100
521112016-07-28 16:44:20.103
August 17, 2016 at 11:45 pm
Experts please help on this
August 18, 2016 at 6:39 am
Hi,
The documentation reads :
Contains one row per page that failed with a minor 823 error or an 824 error. Pages are listed in this table because they are suspected of being bad, but they might actually be fine. When a suspect page is repaired, its status is updated in the event_type column.
The following table, which has a limit of 1,000 rows, is stored in the msdb database.
So I'd imagine that if you ran a DBCC CHECKDB WITH ALL_ERRORMSGS after these occur and it returned nothing, you should be fine.
However you should check the Windows Event logs for issues that occurred roughly at the same time, and check the disk state.
Nicolas.
August 18, 2016 at 6:50 am
ElSuket (8/18/2016)
Hi,The documentation reads :
Contains one row per page that failed with a minor 823 error or an 824 error. Pages are listed in this table because they are suspected of being bad, but they might actually be fine. When a suspect page is repaired, its status is updated in the event_type column.
The following table, which has a limit of 1,000 rows, is stored in the msdb database.
So I'd imagine that if you ran a DBCC CHECKDB WITH ALL_ERRORMSGS after these occur and it returned nothing, you should be fine.
However you should check the Windows Event logs for issues that occurred roughly at the same time, and check the disk state.
Nicolas.
Thanks Nicolas.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply