Recently, I had a situation where a production server was restarted and soon after the restart we found that the database mirroring was disconnected.
And as a bonus, one of the mirrored database was hung in recovery state.
When I investigated further, I found the below message in the SQL Server Logs.
And as a bonus, one of the mirrored database was hung in recovery state.
When I investigated further, I found the below message in the SQL Server Logs.
Bypassing recovery for database '<DB Name>' because it is marked as an inaccessible database mirroring database. A problem exists with the mirroring session. The session either lacks a quorum or the communications links are broken because of problems with links, endpoint configuration, or permissions (for the server account or security certificate). To gain access to the database, figure out what has changed in the session configuration and undo the change. |
This clearly says the connection between the principal and the mirror is not established properly and the combination of a Mirrored Database with a big log file and a server restart caused the "In Recovery State" of the mirrored database.
To fix this error, I had to Restart the Database Mirroring Endpoint.
--To Stop the Endpoint ALTER ENDPOINT <EndPoint Name> STATE=STOPPED --To Start the Endpoint ALTER ENDPOINT <EndPoint Name> STATE=STARTED
2 comments:
where you had this situatiion sir?//?
Today i learn very interesting point and easy fix.
Post a Comment