Consider the following scenario:
- You have a computer that is running a secondary instance of Microsoft SQL Server 2005, Microsoft SQL Server 2008, or Microsoft SQL Server 2008 R2 in a two-server database mirror.
- CPU usage reaches 100 percent on the computer, and you cannot stop the SQL Server service by using SQL Server Management Tools.
- You end the process of the SQL Server secondary instance by using Task Manager.
- You restart the secondary instance of SQL Server.
Bypassing recovery for database 'Database 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 issue occurs because of problems in the SQL Server database mirroring endpoints.
To resolve this issue, use the following methods. If the first method does not resolve the issue, use the second method.
Method 1Recycle the endpoint on the database mirror. To do this, follow these steps:
- On the principal database, execute the following SQL script to stop the endpoint:
ALTER ENDPOINT <Endpoint Name> STATE=STOPPED
- Execute the following SQL script to restart the endpoint:
ALTER ENDPOINT <Endpoint Name> STATE=STARTED
ALTER DATABASE <Database Name> SET PARTNER RESUME
Method 2Delete and re-create the database mirroring endpoints on both servers.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Id. de artículo: 2490051 - Última revisión: 30 ene. 2013 - Revisión: 1