You can only lock objects in Source Control for Oracle 2.
If your team works on a shared database, you can lock objects so other people can't edit the objects while you're working on them. This means teams don't accidentally overwrite work.
After you lock an object, you can work on it and check it in as usual. When you try to edit an object locked by someone else, the server returns an error. You can still unlock other people's objects if you need to.
Object locking isn't necessary for teams where each developer has their own copy of the database.
To use object locking, a SQL script needs to be run on the database. You can do this from the Lock objects tab, or you can run the script manually.
For more information, and to view the script, see Setting up object locking.
After locking is set up, the top pane lists objects that are currently locked in the database. The bottom pane lists objects that are currently unlocked.
The tab shows:
You can move the mouse over the Date and Last edited columns to see exact time stamps.
Type a comment explaining why you're locking the object (optional).
Click Lock selected objects.
The object is locked and appears in the Locked objects pane. The rest of your team can see you've locked the object and won't be able to edit it until it's unlocked.
You can also lock an object by right-clicking it.
For an example of how a team might use object locking, see Example - locking objects.