This section uses unix examples. Consult the Utilities
Programs for Windows for equivalent Windows syntax.
Comment out the entry for the Adaptive Server in the interfaces file.
Rename the RUN_SERVER file for the Adaptive Server to RUN_SERVER.old. Rename your configuration file, adding “.old” to the name.
Run srvbuild to install a new Adaptive Server. Install the Adaptive Server using the original master device, the original Adaptive Server name, and the sort order and character set to reflect that on the dump. This creates a new entry in the interfaces file as well as a new RUN_SERVER file to replace the one you renamed in step 2.
Start Adaptive Server in single-user mode. Refer to “How to Start Adaptive Server in Single-User Mode”.
Ensure that the Adaptive Server has the correct name for the Backup Server in the sysservers table. Refer to “How to Set A Default Backup Server Manually in Adaptive Server” for instructions.
The master database must look exactly
as it did and occupy exactly the same location on the master device
as it did before the database was lost.
Load the master database from backup using the load database command to specify the physical device or file name to reference. For example:
1> load database master from device_name 2> go
Adaptive Server shuts itself down after the load is complete.
With Adaptive Server still down, manually reestablish the number of devices configuration parameter if necessary. Refer to “How to Alter the number of devices Parameter Manually”.
Start Adaptive Server. Change the name of the start-up file with the “.old” suffix created in step 2 back to the original name and start Adaptive Server with that file.
Restore system catalog information for the master database if changes were made to it since the last dump. Refer to “How to Restore System Table Information in master Database”.
Load or rebuild the model database if necessary. Refer to “How to Alter the model Database”.
Drop, re-create, and load any user databases located fully or partially on the master device.
