June 16, 2015 at 1:08 am
Good Day SQL Gurus,
We found an interesting 'issue' in one of our productive user database:
The output of msdb..suspect_pages table:
db_idfile_idpage_idevent_typeerror_countlast_update
16 2 22 32015.06.12 10:40
16 2 3 3 3 2015.06.12 10:40
16 2 6 3 3 2015.06.12 10:40
16 2 7 3 3 2015.06.12 10:40
16 2 1 3 3 2015.06.12 10:40
The problem is, that this user database only has one data file and file_id 2 is the log file.
I understand that the event_type shows checksum and torn page error but in the log file?
DBCC CHECKDB shows no errors and the database is part of an AOAG in synchronized state.
We have log backups in every 15 minutes.
Is this something to worry about?
Thank you.
________________________________________________________________
"Accept conditions as they exist, or accept the responsibility for changing them."
June 17, 2015 at 2:09 am
SOLVED
We were able to replicate the issue:
Turned out one of the DBA guys ran the DBCC PAGE command with the log file ID by accident, and that was causing those entries. So no real issue.
Moral of the story: Do not run DBCC PAGE command on the log file. 😛
________________________________________________________________
"Accept conditions as they exist, or accept the responsibility for changing them."
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply