Usually I am facing this problem while locking any object in my local tools, it says that this object/ project is already locked by some other user. I bet that everyone faces this issue.
While getting DB extract these projects/objects extracted in locked state only. So, I don’t know any full proof solution for this. But we always have a work around, which I will compile in this post for future reference.
Problem:
We need to unlock any project/object on our local.
Solution:
We will change locked_flg from backend. Here backend means dbisql to run queries.
Path: ./Client_1/BIN/dbisqlc.exe
[su_lightbox type=”image” src=”http://askmesiebel.com/wp-content/uploads/2014/04/Capture.jpg”]
[/su_lightbox]
You have provide DBF path and userid/passw to run this and then you have to use below queries…
[su_heading size=”17″]Unlock Project:[/su_heading]
UPDATE SIEBEL.S_PROJECT AS PROJ SET PROJ.LOCKED_FLG = 'N', PROJ.LOCKED_DATE = NULL
WHERE PROJ.NAME = '';
COMMIT;
[su_spacer size=”10″]
[su_heading size=”17″]Unlock View:[/su_heading]
UPDATE SIEBEL.S_VIEW BC SET BC.OBJ_LOCKED_FLG = 'N', BC.OBJ_LOCKED_DATE = NULL, BC.OBJ_LOCKED_BY = NULL, BC.OBJ_LOCKED_LANG = NULL
WHERE BC.Name = '';
COMMIT;
[su_heading size=”17″]Unlock Business Component:[/su_heading]
UPDATE SIEBEL.S_BUSCOMP BC SET BC.OBJ_LOCKED_FLG = 'N', BC.OBJ_LOCKED_DATE = NULL, BC.OBJ_LOCKED_BY = NULL, BC.OBJ_LOCKED_LANG = NULL
WHERE BC.Name = '';
COMMIT;
[su_spacer size=”10″][su_heading size=”17″]Unlock Business Object:[/su_heading]
UPDATE SIEBEL.S_BUSOBJ BO SET BO.OBJ_LOCKED_FLG = 'N', BO.OBJ_LOCKED_DATE = NULL, BO.OBJ_LOCKED_BY = NULL, BO.OBJ_LOCKED_LANG = NULL
WHERE BO.Name = '';
COMMIT;
[su_spacer size=”10″][su_heading size=”17″]Unlock Business Service:[/su_heading]
UPDATE SIEBEL.S_SERVICE SERV SET SERV.OBJ_LOCKED_FLG = 'N', SERV.OBJ_LOCKED_DATE = NULL, SERV.OBJ_LOCKED_BY = NULL, SERV.OBJ_LOCKED_LANG = NULL
WHERE SERV.Name = '';
COMMIT;
[su_spacer size=”10″][su_heading size=”17″]Unlock Applet:[/su_heading]
UPDATE SIEBEL.S_APPLET APPL SET APPL.OBJ_LOCKED_FLG = 'N', APPL.OBJ_LOCKED_DATE = NULL, APPL.OBJ_LOCKED_BY = NULL, APPL.OBJ_LOCKED_LANG = NULL
WHERE APPL.Name = '';
COMMIT;
[su_spacer size=”10″][su_heading size=”17″]Unlock Table:[/su_heading]
UPDATE SIEBEL.S_TABLE TAB SET TAB.OBJ_LOCKED_FLG = 'N', TAB.OBJ_LOCKED_DATE = NULL, TAB.OBJ_LOCKED_BY = NULL, TAB.OBJ_LOCKED_LANG = NULL
WHERE TAB.NAME = ‘S_APPLICATION’
AND TAB.Name = '';
COMMIT;
[su_spacer size=”25″]
Note: I always make mistakes while not doing commit after unlocking project and frustrated to see no changes.
[su_divider]
@AskmeSiebel
3 comments for “How to unlock Siebel Project or other Repository Objects on local using DB”