FIX: Log Shipping: Cannot Change Role From Secondary to Primary When Database Names Are Different

This article was previously published under Q300497
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 235878 (SHILOH_BUGS)
SYMPTOMS
When using log shipping with a primary server and two secondary servers, the log shipping monitor may fail to update the remaining secondary node after a role change if the shipped database name is not the same on all servers.
CAUSE
The log shipping tool assumes that the database name is the same on both primary and secondary server(s). The shipping plan is for the database as named on the primary server.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 1.
MORE INFORMATION
For additional information, see SQL Server 2000 Books Online and the following links:
Properties

Article ID: 300497 - Last Review: 01/16/2015 22:56:18 - Revision: 1.4

Microsoft SQL Server 2000 Enterprise Edition

  • kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix kbsqlservlogship KB300497
Feedback