-
Title
Error: Exclusive access could not be obtained because the database is in use when restoring LiteS -
Description
The LiteSpeedLocal database restore attempt failed with the followng error message:
SQL Server has returned a failure message to LiteSpeed for SQL Server which has prevented the operation from succeeding. The following message is not a LiteSpeed for SQL Server message. Please refer to SQL Server books online or Microsoft technical support for a solution:
RESTORE DATABASE is terminating abnormally.
Exclusive access could not be obtained because the database is in use.
-
Cause
When the LiteSpeed application is in use, a connection to the LiteSpeedLocal and/or the LiteSpeedCentral is maintained.
-
Resolution
WORKAROUND:
1. If you are NOT using LiteSpeed Log Shipping and do not require the statistics in the databases, run Instance Configuration to recreate the LiteSpeedLocal and/or LiteSpeedCentral, however you'll be missing the history since the new DBs will be empty. Many of the SQLServer's activities may be c9ollected from the history tables in the msdb database.2. You include a KILL command to drop the users and start the restore before the database could reconnect to the server. The command must be executed consecutively.
SAMPLE:---- Kill all current connectionsDECLARE @cmdKill VARCHAR(50)DECLARE killCursor CURSOR FOR
SELECT 'KILL ' + Convert(VARCHAR(5), p.spid)
FROM master.dbo.sysprocesses AS p
WHERE p.dbid = db_id('LiteSpeedLocal')OPEN killCursor
FETCH killCursor INTO @cmdKillWHILE 0 = @@fetch_status
BEGIN
EXECUTE (@cmdKill)
FETCH killCursor INTO @cmdKill
ENDCLOSE killCursor
DEALLOCATE killCursor-----------------------exec master.dbo.xp_restore_database @database = N'LiteSpeedLocal' ,
@filename = N'D:\Backup\LiteSpeedLocal_Full_20100405104447.bak',
@filenumber = 1,
@with = N'REPLACE',
@with = N'STATS = 10',
@affinity = 0,
@logging = 0
GO