<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Unlock a Project</title>
	<link>http://siebelguide.com/siebelblogs/2008/01/22/unlock-a-project/</link>
	<description>Siebel Blogs, News, Events, Tips and Tricks</description>
	<pubDate>Sat, 19 May 2012 08:57:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Walter Stolyar</title>
		<link>http://siebelguide.com/siebelblogs/2008/01/22/unlock-a-project/#comment-15219</link>
		<author>Walter Stolyar</author>
		<pubDate>Tue, 13 Apr 2010 18:44:13 +0000</pubDate>
		<guid>http://siebelguide.com/siebelblogs/2008/01/22/unlock-a-project/#comment-15219</guid>
		<description>I think additional columns need to be updated to avoid future confusion:


update .S_PROJECT
set
locked_date = null,
locked_by = null,
locked_lang = null,
locked_flg = 'N'
where name = 'Project Name'
and repository_id = 'x_xxx';</description>
		<content:encoded><![CDATA[<p>I think additional columns need to be updated to avoid future confusion:</p>
<p>update .S_PROJECT<br />
set<br />
locked_date = null,<br />
locked_by = null,<br />
locked_lang = null,<br />
locked_flg = &#8216;N&#8217;<br />
where name = &#8216;Project Name&#8217;<br />
and repository_id = &#8216;x_xxx&#8217;;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sridhar</title>
		<link>http://siebelguide.com/siebelblogs/2008/01/22/unlock-a-project/#comment-2064</link>
		<author>Sridhar</author>
		<pubDate>Tue, 03 Jun 2008 22:07:59 +0000</pubDate>
		<guid>http://siebelguide.com/siebelblogs/2008/01/22/unlock-a-project/#comment-2064</guid>
		<description>Good point Mike. You are correct. We have to make sure the update is on the intended repository.

Thanks for Participating. If you have more ideas and would like to share, please write a blog that I can publish it over here. Thanks!</description>
		<content:encoded><![CDATA[<p>Good point Mike. You are correct. We have to make sure the update is on the intended repository.</p>
<p>Thanks for Participating. If you have more ideas and would like to share, please write a blog that I can publish it over here. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike M. Lin</title>
		<link>http://siebelguide.com/siebelblogs/2008/01/22/unlock-a-project/#comment-2062</link>
		<author>Mike M. Lin</author>
		<pubDate>Tue, 03 Jun 2008 18:21:44 +0000</pubDate>
		<guid>http://siebelguide.com/siebelblogs/2008/01/22/unlock-a-project/#comment-2062</guid>
		<description>If you have multiple repositories, make sure you only unlock the project in the intended repository:

UPDATE SIEBEL.S_PROJECT
SET LOCKED_FLG = 'N'
WHERE NAME = 'Account'
AND REPOSITORY_ID = (
  SELECT ROW_ID 
  FROM SIEBEL.S_REPOSITORY 
  WHERE NAME = 'The Intended Repository');</description>
		<content:encoded><![CDATA[<p>If you have multiple repositories, make sure you only unlock the project in the intended repository:</p>
<p>UPDATE SIEBEL.S_PROJECT<br />
SET LOCKED_FLG = &#8216;N&#8217;<br />
WHERE NAME = &#8216;Account&#8217;<br />
AND REPOSITORY_ID = (<br />
  SELECT ROW_ID<br />
  FROM SIEBEL.S_REPOSITORY<br />
  WHERE NAME = &#8216;The Intended Repository&#8217;);</p>
]]></content:encoded>
	</item>
</channel>
</rss>

