Views Not Seen in Local DB

When I logined from my thick (developer) client to local environment , I realised that some views aren’t visible. As a sample, I could not open “Workspace Projects” view in Administration-Product screen in my local db. This view is added to my responsibilities , both in Siebel Administrator (out of box one) and X which is the custom one (which is copied from Siebel Administrator and including other custom views). It could be because of the srf, so I took the srf from the server side, in which this view is visible.  But nothing changed after these controls in my local, still not visible.

After a search, I got some information from Oracle Support: If a user has more than one responsibility, all the responsibilities’ Local Access Check flag should be True. If  any of one has this view with Local Access as False, view gets invisible in the client side. Porblem was fixed, deleting the Siebel Administrator (out of box one, so it is read only, its Local Access flag can not be checked under Administration-Application -> Views ) Responsibility under the local user. So, all the responsibilities of the user has the view with Local Access check flag is set to Y. Logoff – login again, the view is now available.

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.