Restoring IQ Store Data When Restoring the Database in the Same Location

Restore operations vary depending on where you are restoring the data.

1. Confirm that database home directories for each server still exist. If not, create them or restore them from file system backups.
2. Shut down every server in the multiplex (coordinator and all secondary servers). In Sybase Central, right-click the multiplex icon and use the Stop Server wizard. The wizard lets you select servers to stop.
   Note:

   If automatic startup is enabled in your ODBC configuration, users on the same machine as the server may be set up to start the server automatically. Prevent this from happening while you are restoring the database.

3. Confirm that the database shut down successfully:

   Platform	Actions
   UNIX	% ps -ef | grep iqsrv15 If you see an active iqsrv15 process with name of a multiplex, stop the process.
   Windows	In Task Manager, look on the Processes tab for iqsrv15.exe, or find the IQ Server icon in the system tray and stop it using right-click and Shutdown.

4. Move files required for debugging and reconfiguring the multiplex.

   • Make a file system copy of the .iqmsg file. If you have message log archiving configured, see System Administration Guide: Volume 1 > Data Backup, Recovery, and Archiving > System-Level Backups > Back Up the Right Files.

   • On each server, preserve any files that were added to IQ_SYSTEM_TEMP for that server. These files are of the form dbname.iqtmp if you used an operating system file, or they may be raw devices. If the IQ temporary store is damaged, start the server with the -iqnotemp switch to drop and recreate the temporary store dbspaces. For more information, see the Release Bulletin.

     Either drop the database or delete the following files from the coordinator:

     <database_home>/<dbname>.db

     <database_home>/<dbname>.log

     If a query server is damaged, however, drop it and re-create it after RESTORE. Then follow the instructions in Restoring IQ Store Data When Restoring the Database in a Different Location.

5. Start the utility database from the coordinator server directory. Use any valid identifier as the server name except the name of a registered secondary server. If you use the coordinator’s name, rename the coordinator after the restore.

   % start_iq -n utility_startup_svr -c 32MB 
   -x tcpip(port=1234) 

6. Connect to the utility database (utility_db):

   % dbisql -c "eng=utility_startup_svr;uid=DBA;pwd=SQL;
   dbn=utility_db"

7. Run the RESTORE command. To restore certain dbspace files to a different path, specify a RENAME clause. For details, see Reference: Statements and Options >SQL Statements > RESTORE Statement.
8. Shut down the utility database.
9. Make sure that the temporary dbspaces exist as before, on raw devices or as files of the correct length. See System Administration Guide: Volume 1 > Data Backup, Recovery, and Archiving > System-Level Backups > Back Up the Right Files. For information on starting the server without using the IQ temporary store, see the Release Bulletin for your platform.
10. Start the coordinator server and, if restoring to the same location, synchronize the secondary servers. For more information, see Multiplex Server Synchronization .
11. Start the secondary servers.