If
you inadvertently take the failed resource group offline before
issuing prepare_failback, the primary
companion’s devices will be removed by FailSafe. This causes
an Adaptive Server error 840 on all the primary databases that have
been moved to the secondary companion. The databases are marked as not
recovered, offline.
This error can be corrected, but requires advanced system administration. If you’re not comfortable performing these steps, contact Sybase Technical Support.
Perform the following to recover from a failed manual prepare_failback:
Bring the Primary Resource Group back Online. See “Bring the primary resource group online” for more information.
Take the Secondary Resource Group Offline, then Online. See “Take the primary companion’s resource group offline” and “Bring the primary resource group online” but use sec_rg instead of pri_rg for the resource group name.
Allow updates to the system catalogs. Log into the secondary companion using isql and enter:
sp_configure “allow updates”, 1
Unset the not recovered flag.
Log into the secondary companion using isql and
enter:
update sysdatabases set status = status & ~256 where status & 256 = 256
Disallow Updates to the System Catalogs. Log into the secondary companion using isql and enter:
sp_configure “allow updates”, 0
(This is a repeat of step 2) Take the secondary resource group offline, then online. See “Take the primary companion’s resource group offline” and “Bring the primary resource group online”, but use sec_rg instead of pri_rg for the resource group name.
Confirm that the databases are recovered. Log into the secondary companion using isql, and enter:
sp_helpdb
