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

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 the Microsoft 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:

"Log Shipping"
http://msdn.microsoft.com/library/psdk/sql/ad_1_server_8elj.htm

"How to set up and perform a log shipping role change"
http://msdn.microsoft.com/library/psdk/sql/ht_1_013_9t0p.htm

"sp_change_primary_role"
http://msdn.microsoft.com/library/psdk/sql/ts_sp_ca-cz_12hx.htm

"sp_change_secondary_role"
http://msdn.microsoft.com/library/psdk/sql/ts_sp_ca-cz_2o6d.htm

"sp_change_monitor_role"
http://msdn.microsoft.com/library/psdk/sql/ts_sp_ca-cz_6vl1.htm