Sybase 12.4.2 Validating the database after you restore, Restore requires exclusive write access

Restoring your databases

Description	The DBLOG command line utility allows you to display or change the name
	of the transaction log or transaction log mirror associated with a database. You
	can also stop a database from maintaining a transaction log or mirror, or start
	maintaining a transaction log or mirror.

Transaction log utility options

Set the name of the transaction log mirror file (-m) This option sets a

filename for a new transaction log mirror. If the database is not currently using a transaction log mirror, it starts using one. If the database is already using a transaction log mirror, it changes to using the new file as its transaction log mirror. Most Adaptive Server IQ databases do not use a transaction log mirror, so this switch is rarely used.

Set the name of the transaction log file (-t) This option sets a filename,

including an optional directory path, for a new transaction log. If the database is not currently using a transaction log, it starts using one. If the database is already using a transaction log, it changes to using the new file as its transaction log.

Validating the database after you restore

To ensure that tapes have been restored in the correct order, you should run the stored procedure sp_iqcheckdb after you finish restoring your database. If you are restoring a set of incremental backups, it is safest to run sp_iqcheckdb after restoring each backup. Because this procedure can take many hours, however, you may prefer to run it after the full backup only, not after each incremental. For more information, see “Validating your database”.

Restore requires exclusive write access

Once RESTORE starts, no other users are allowed to access the specified database. If you restore from a full backup and then from one or more incremental backups, you should ensure that no users are modifying the database between the restores. The modifications are permitted, but you cannot perform any more incremental restores. Instead, you must start the entire restore again.

406