Locally unlocking a locked Project

March 22, 2007 at 7:47 pm 2 comments

With multiple developers building one application it’s inevitable that multiple developers will need to change the same project at the same time. There’s pros and cons and object-locking and change-control and build-control etc etc, but sometimes deadlines are too tight and you just have to fork.

In Siebel Tools, once one developer’s got a project locked the UI won’t let a second developer anywhere near it. To get around this you need to get into SQL Anywhere. Login to the second developer’s local database, then the following script will unlock the project locally:

UPDATE s_project
SET locked_flg = ‘N’
WHERE name = <Project Name>

The second developer can now log into Siebel Tools, manually lock the project as normal and do what she has to do. Of course, once build is done the two developers will need to go through a merge exercise to get their changes into the one repository, but that effort can be preferable to losing days of development time.


Entry filed under: Siebel, SQL.

Tools Object Explorer options Siebel Interview question


  • 1. Naga  |  August 25, 2007 at 2:56 am


    good blog… can tell me whether we can impliment both DB lohin and AD login in developmnt environmnt on single sibel server configuration.


  • 2. stuandgravy  |  August 25, 2007 at 9:33 am

    Hi Nagarjuna,

    Yes, you can implement both types of authentication in a single enterprise, you just need to use two different object managers.


%d bloggers like this: