This document applies only to the following language version(s):
Instructions for removing the 'Exclusive Lock' on Microsoft SQL Server databases in iBase 8.
When trying to log into IBM i2 iBase (or iBase Designer) users may experience an error which reports that there is an 'Exclusive Lock' on their database.
Can occur when IBM i2 iBase or iBase Designer is improperly shutdown.
Resolving the problem
Ensure that you have a backup copy of your SQL database(s) before attempting the steps below.
To resolve the issue, follow these steps:
- Login to Microsoft SQL Server Management Studio
- Expand the Database folder
- Expand Tables folder
- Look for the entries 'dbo._Configuration_Def', 'dbo._Configuration_Text' and 'dbo._Configuration_Binary'
- Open the table 'dbo._Configuration_Def' and look for the entry SQLServer:Exclusive" and check the value against it. If the value is 1 then it means the same value also exist in the 'dbo._Configuration_Binary' table. However, if the value is 0 then it means the same value also exist in the 'dbo._Configuration_Text' table.
- Delete the entry (row) from table 'dbo._Configuration_Text' or 'dbo._Configuration_Binary'
- Then delete the value from 'dbo._Configuration_Def' table
This should remove the 'Exclusive Lock' from the database.
Other step to try, things to check:
1. Get the user to log back into IBM i2 iBase Designer if possible and then cleanly log-out
2. Check that no other applications are logged onto the SQL Server
3. Check for the use of triggers on the SQL Server database
4. Check the Activity Monitor report on SQL Server from the DBA staff
5. Run SQL command - 'ALTER DATABASE < db_name> SET SINGLE_USER WITH NO_WAIT'