Recovery and repair overview

If your Sybase IQ server or database has problems restarting, use the information in this chapter to diagnose database startup problems, verify the consistency of databases, and repair databases. If you are able to restart the server after a failure, Sybase recommends that you verify your database, preferably before allowing users to connect. You verify databases using the sp_iqcheckdb stored procedure, as described in this chapter.

If you have trouble starting a server or database, if the database starts but users are unable to connect to it, or if problems are found during database verification, you may need to perform a forced recovery or restore the database.

This chapter explains how to determine when you need to perform each of these functions. It describes database verification, forced recovery, leaked space recovery, and index repair. For details on restoring databases, see Chapter 12, “Data Backup, Recovery, and Archiving,” in the System Administration Guide: Volume 1.

Examining the server log and IQ message log

To determine what type of recovery or repair is needed, you need information from your server log (servername.nnnn.srvlog) and IQ message log (dbname.iqmsg). Be sure to retain this information so you can provide it to Sybase Technical Support if necessary.

For example, if data inconsistency is detected, the dbname.iqmsg file may include detailed diagnostic information.