Error message 18750

If a companion server issues error message 18750, check the @@cmpstate of the servers. If the primary companion is in normal companion mode, but the secondary companion is in secondary failover mode, the cluster is in an inconsistent state, and you must manually recover. The inconsistent state may be caused by a failed sp_companion 'prepare_failback' command on the secondary companion. You can determine if this happened by examining the log (located in $SYBASE/SYBASE_ASE/install/server_name_ha.log) on the secondary node. To recover:

1. Shut down both the primary and the secondary companions.

2. Restart the secondary companion.

3. Repair all databases marked “suspect.” To determine which databases are suspect, issue:

   select name, status from sysdatabases
   

   Databases marked suspect have a status value of 320.

4. Allow updates to system tables:

   sp_configure “allow updates”, 1
   

5. For each suspect failed-over database, perform the following:

   1> update sysdatabase set status=status-256 where name='database_name'
   2> go
   1> dbcc traceon(3604)
   2> go
   1> dbcc dbrecover(database_name)
   2> go
   

6. From the secondary companion, issue:

   sp_companion primary_companion_name, prepare_failback
   

   Make sure that this command executes successfully.

7. Restart the TruCluster resource on the primary node.

Copyright © 2005. Sybase Inc. All rights reserved.

View this book as PDF