<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Pro Schema Locking in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/pro-schema-locking/m-p/526116#M23152</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anyone know if there's a way to clear a lock on a fgdb in pro without restarting the whole program? I close out&amp;nbsp; of any active maps that use that fgdb, I refresh catalog tree, but nothing seems to "unlock" the database. Just curious if people have similar experiences or have a workaround. Closing/restarting pro takes a good chunk of my day it seems and I'd love to find an alternative. I can't find any way to remove the lock other than a full shutdown of pro.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;More details:&lt;/P&gt;&lt;P&gt;&amp;nbsp;- A standalone python script I'm working on in Jupyter throws a schema lock error&lt;/P&gt;&lt;P&gt;&amp;nbsp;- There is a lock file in the file gdb I'm working with&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Removing the layer from the map looks like it clears the lock, UNLESS I have browsed to the layer in the fgdb through the catalog pane. If I first connect to it via the catalog panel in Pro, then removing the layer does NOT remove the lock.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 30 May 2019 14:30:10 GMT</pubDate>
    <dc:creator>roemhildtg</dc:creator>
    <dc:date>2019-05-30T14:30:10Z</dc:date>
    <item>
      <title>Pro Schema Locking</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/pro-schema-locking/m-p/526116#M23152</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anyone know if there's a way to clear a lock on a fgdb in pro without restarting the whole program? I close out&amp;nbsp; of any active maps that use that fgdb, I refresh catalog tree, but nothing seems to "unlock" the database. Just curious if people have similar experiences or have a workaround. Closing/restarting pro takes a good chunk of my day it seems and I'd love to find an alternative. I can't find any way to remove the lock other than a full shutdown of pro.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;More details:&lt;/P&gt;&lt;P&gt;&amp;nbsp;- A standalone python script I'm working on in Jupyter throws a schema lock error&lt;/P&gt;&lt;P&gt;&amp;nbsp;- There is a lock file in the file gdb I'm working with&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Removing the layer from the map looks like it clears the lock, UNLESS I have browsed to the layer in the fgdb through the catalog pane. If I first connect to it via the catalog panel in Pro, then removing the layer does NOT remove the lock.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 May 2019 14:30:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/pro-schema-locking/m-p/526116#M23152</guid>
      <dc:creator>roemhildtg</dc:creator>
      <dc:date>2019-05-30T14:30:10Z</dc:date>
    </item>
    <item>
      <title>Re: Pro Schema Locking</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/pro-schema-locking/m-p/526117#M23153</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What version and patch are you running?&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 May 2019 20:10:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/pro-schema-locking/m-p/526117#M23153</guid>
      <dc:creator>KoryKramer</dc:creator>
      <dc:date>2019-05-30T20:10:36Z</dc:date>
    </item>
    <item>
      <title>Re: Pro Schema Locking</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/pro-schema-locking/m-p/526118#M23154</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ArcGIS Pro 2.3.3&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jun 2019 20:35:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/pro-schema-locking/m-p/526118#M23154</guid>
      <dc:creator>roemhildtg</dc:creator>
      <dc:date>2019-06-13T20:35:45Z</dc:date>
    </item>
    <item>
      <title>Re: Pro Schema Locking</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/pro-schema-locking/m-p/526119#M23155</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Although I am not using python (you could probably still try and code this), I frequently encounter schema lock issues when using&lt;EM&gt; Field Calculator&lt;/EM&gt;&amp;nbsp;and by simply selecting&amp;nbsp;&lt;EM&gt;Enable Undo&lt;/EM&gt;&amp;nbsp;this allows me to complete the calculation 90% of the time.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jun 2019 21:26:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/pro-schema-locking/m-p/526119#M23155</guid>
      <dc:creator>MervynLotter</dc:creator>
      <dc:date>2019-06-13T21:26:49Z</dc:date>
    </item>
    <item>
      <title>Re: Pro Schema Locking</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/pro-schema-locking/m-p/526120#M23156</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Mervyn! Worked like a charm. I've been struggling with this issue for a couple of months now. I always had to close Pro, do the field calculations in ArcMap and the go back to Pro. I'm so glad that with your help that's over now.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jan 2020 16:39:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/pro-schema-locking/m-p/526120#M23156</guid>
      <dc:creator>JohannaPrüssmann1</dc:creator>
      <dc:date>2020-01-23T16:39:41Z</dc:date>
    </item>
  </channel>
</rss>

