July 6, 2016 at 3:46 pm
I have a mirrored db that has had a snapshot created for it every day for a year (scripted) with no problems. Today, we added new datafiles to the source DB and verified the data files were created fine on the mirror and now when we run the script to create the snapshot (including the new datafiles), we get the following error:
Msg 1823, Level 16, State 6, Line 1
A database snapshot cannot be created because it failed to start.
Msg 1823, Level 16, State 7, Line 1
A database snapshot cannot be created because it failed to start.
Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 11:5964361; actual 0:0). It occurred during a read of page (11:5964361) in database ID 8 at offset 0x00000b60492000 in file 'B:\DB_SS_DF\DB-SS-RPT_Data4b.ss'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 3313, Level 21, State 1, Line 1
During redoing of a logged operation in database 'DB-SS-RPT', an error occurred at log record ID (1204229:88968:3). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
Obviously I cannot run a DBCC on the Mirror so I kicked one of on the primary. Waiting to see results. Any advice or input from those who have seen this before is appreciated.
Thanks,
JT
July 7, 2016 at 12:06 pm
Here is the latest: After running a DBCC CHECKDB on the primary, no errors were found. So naturally I am attempting to rebuild the mirror so I issue the "ALTER DATABASE [DB] SET PARTNER OFF;" and get a command executed successfully. The mirror immediately goes into a "Mirror,Disconnected/In Recovery" state. Next I want to issue a recovery command to bring it online so I can delete it and rebuild the mirror, however, I get messages stating the mirror is busy and to try the command later. I found this link - http://www.sqlservercentral.com/Forums/Topic1120657-146-1.aspx , but there are other DBs on this server so I cant restart the service. Any other ideas on how to get this DB out of mirrored mode so I can delete it?
Also, the primary has had mirroring removed so all is good on that side.
Thanks in advance,
JT
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply