Full System Recovery of Sybase Server: Restoring Defective Devices and Suspected Databases
A full Sybase restore may fail if one or more database devices are defective or have been physically deleted and the corresponding databases have therefore been marked as suspected. In such a case, all the databases marked as suspected and the corresponding devices whose files have been lost must be dropped and re-created.
Before You Begin
Complete the following task:
- Issue the following command to determine whether the database is suspected:
sp_marksuspect (<database name>)
- Drop the suspected database using the following command:
dbcc dbrepair (<database name>, dropdb)
dbcc dbrepair (<sybdb1>, dropdb)
- If the database to be recovered is sybsystemprocs (system database), use the following command to drop the corresponding device (since stored procedures are not available at this point):
disk release name = <device name>
disk release name = <tempdbdev>
- If any of the data device files do not exist but the device entry exists in sysdevices, drop those devices using the following command:
sp_dropdevice <device name>
- Repeat the above procedure for each suspected database.
- Resume the restore starting with the first database that was deemed suspected.