Unlocking a Database

The Vulcan design database consists, along with the associated index files, of a work file (.wrk) and a design database. All changes and new work is performed on the .wrk file. This file is locked until a save operation is carried out, i.e. no other user can change or add data to the file.

Any queries by other users on Vulcan data is performed on the design database. The design database is only locked when the .wrk file is being saved, when a new design database is being created or if another user is using the database.

There are three types of locks placed on design databases:

Lock Description

Indicates that the database has been locked by you. This happens automatically when the database is opened to prevent it from being modified by another user.

Indicates that the original lock was not removed before exiting the application, this may have been due to a system failure.

Indicates that the file is being used by another user. It is only possible to unlock databases that have been locked by you.

Design databases can be unlocked through using one of the following methods:

  • Vulcan Explorer
    Right-click on the locked database file and select Unlock from the displayed context menu. If Vulcan is running, then the Unlock and Open option will also be available through the displayed context menu. Unlike the Unlock option, the Unlock and Open option will remove the database lock as well as open the selected design database.

  • Shell Window
    Enter the following command;
    rm <proj><sdi>.dgd.isis_lock rm <proj><sdi>.wrk_lock 
  • Vulcano
    Use the Unlock Databases option under Design.

Note:   The standard isis_lock file that is generated upon opening a database prevents multiple people from establishing the same working database.  Even if a file is locked for editing, other people still have read-only access to that database.  However, for certain operations, a stricter isis_wlock file is created upon opening a database.  The isis_wlock file restricts both read and write access to the database by anyone other than the primary user.