During system recovery, any uncommitted transactions are rolled back and any disk space used for old versions (snapshots of database pages that were being used by transactions that did not commit) returns to the pool of available space. The database then contains only the most recently committed version of each permanent table, unless it is a multiplex database. A multiplex database contains all versions accessible to secondary servers. For more information on versioning, see Chapter 10, “Transactions and Versioning,” in the System Administration Guide: Volume 1.
During recovery from a system failure or normal system shutdown, Sybase IQ reopens all connections that were active. If the -gm option, which sets the number of user connections, was in effect at the time of the failure, you need to restart the IQ server with at least as many connections as were actually in use when the server stopped.