Unlock a Project in Local Repository

If you get a Project from the Server Repository , which is locked by another user, the Project’s “Locked” flag is checked. You can not modify the objects belonging to this locked Project. To be able to work with this Project in local repository , it should be locked by local repository user. If you know the user’s password , you can login to Server Repository and unlock the Project, then get it. But, it is so risky that this user can not check in the Project from his local repository anymore. You can login to your local db and with an SQL, the lock on the Project can be removed:

UPDATE SIEBEL.S_PROJECT SET LOCKED_FLG = ‘N’ WHERE NAME = < PROJECT_NAME >;

Symbolic String Error

When I tried to check out the Project that stores the Symbolic Strings (Project_B), I got an error meanwhile which is :

[Siebel Database][ODBC Driver][Adaptive Server Anywhere] Integrity constraint violation: Index ‘S_SYM_STR_U1′ for table ‘S_SYM_STR’ would not be unique

After clicking OK another pop up which says:

Siebel-ERR- 1124: Unable to import table ‘S_SYM_STR’ (UTLOdbcExecute insert)

So , I could not get the project from the Server.

After that, I increased the log level to find out the error. I searched the log text and came up with a symbolic string named X_xxx causes the error. I searched this in my local repository and its Project was seemed Project_A. Also, I logined to the server from Siebel Tools , again searched it but its Project was Project_B. While getting the Project_B , X_xxx loses uniqueness, so Siebel Tools throws like an error. To overcome, first I got the Project_A from the server which does not contain X_xxx to crush the code in repository. Following this, I was successful to check out the Project_B.