Extend of a SQL Resource Fails

Symptom:

The Extend of a Microsoft SQL resource will fail if the primary and backup configurations are different (i.e. Microsoft SQL ID mismatch). Below is an example of the error message displayed in the LifeKeeper GUI during the can extend operation:

Process: canextend.ksh(1292)

ERROR (No. 14003) The target value for Database file location does not match the template value (target=- DQ:\SQLDEFAULT\MSSQL.1\MSSQL\DATA\MASTER.MDF,template=DQ:\SQLDEFAULT\MSSQL.4\MSSQL\DATA\MASTER.MDF)

Process: canextend.ksh(1572)

ERROR (No. 14003) The target value for Temp DB location does not match the template value (target=-EQ:\SQLDEFAULT\MSSQL.1\MSSQL\LOG\ERRORLOG,template=-EQ:\SQLDEFAULT\MSSQL.4\MSSQL\LOG\ERRORLOG)

Process: canextend.ksh(1156)

ERROR (No. 14003) The target value for Log file location does not match the template value (target=-LQ:\SQLDEFAULT\MSSQL.1\MSSQL\DATA\MASTLOG.LDF,template=-LQ:\SQLDEFAULT\MSSQL.4\MSSQL\DATA\MASTLOG.LDF)

Error – extmgr (HAWK, MSSQL.0, MSSQL.0, OSPREY) – canextend failed

Suggested Actions:

Use the ID Conflict Resolution option to resolve Microsoft SQL ID mismatches between the primary and backup servers. In the LifeKeeper GUI, right-click on the SQL Server resource (on the right-hand side of the LifeKeeper GUI) and select properties, then select the SQL Server Configuration tab. Click the Admin Actions button and select ID Conflict Resolution on the SQL Server Configuration page.

See the topic Managing a SQL Server Configuration for more details on the SQL Server Configuration page.