<?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 Re: OBJECTID values in Oracle in Geodatabase Questions</title>
    <link>https://community.esri.com/t5/geodatabase-questions/objectid-values-in-oracle/m-p/872558#M6309</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's a bit more complicated than just a sequence, because sequence generation is too slow for bulk insert processes.&amp;nbsp; Instead, the sequence has an interval (size dependent on version) for a gap in values and a pipe is used to store the next value when a cursor is shut down.&amp;nbsp; When the next cursor comes along, it will fetch off the pipe before consulting the sequence, to prevent a gap.&amp;nbsp; If you shut down the instance, the DBMS_PIPE objects are lost, resulting in a gap in subsequent inserts (though there is a [somewhat elderly] &lt;A href="http://support.esri.com/es/knowledgebase/techarticles/detail/28835"&gt;KB document&lt;/A&gt; that addresses a workaround).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 25 Feb 2016 17:47:00 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2016-02-25T17:47:00Z</dc:date>
    <item>
      <title>OBJECTID values in Oracle</title>
      <link>https://community.esri.com/t5/geodatabase-questions/objectid-values-in-oracle/m-p/872555#M6306</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Where do OBJECTID values on a feature class in Oracle come from when inserts occur?&amp;nbsp; Is it a sequence somewhere, or does ArcMap scan to find the current maximum ID and do a +1 operation before the insert?&amp;nbsp; In my situation the feature class is versioned and uses ST Geometry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The feature class also has archiving enabled, so does the GDB_ARCHIVE_OID value on the archive table use the same mechanism to create OBJECTID values when records are inserted there when edits are posted to default?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Feb 2016 15:14:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/objectid-values-in-oracle/m-p/872555#M6306</guid>
      <dc:creator>AndrewRudin</dc:creator>
      <dc:date>2016-02-24T15:14:56Z</dc:date>
    </item>
    <item>
      <title>Re: OBJECTID values in Oracle</title>
      <link>https://community.esri.com/t5/geodatabase-questions/objectid-values-in-oracle/m-p/872556#M6307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Andrew&lt;/P&gt;&lt;P&gt;I am not sure but I think that each layer/table registered with the geodabase has its own Oracle sequence for obtaining the OID value. Sequences are named "RXXX" where XXX is the value of the &lt;SPAN&gt;&lt;SPAN class="Apple-converted-space"&gt; &lt;/SPAN&gt;REGISTRATION_ID&lt;/SPAN&gt; field related with an specific table/layer in the SDE table TABLE_REGISTRY .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jesús de Diego&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Feb 2016 15:29:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/objectid-values-in-oracle/m-p/872556#M6307</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2016-02-24T15:29:52Z</dc:date>
    </item>
    <item>
      <title>Re: OBJECTID values in Oracle</title>
      <link>https://community.esri.com/t5/geodatabase-questions/objectid-values-in-oracle/m-p/872557#M6308</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Look at the MINIMUM_ID field in the TABLE_REGISTRY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://desktop.arcgis.com/en/arcmap/latest/manage-data/gdbs-in-oracle/system-tables-oracle.htm" title="http://desktop.arcgis.com/en/arcmap/latest/manage-data/gdbs-in-oracle/system-tables-oracle.htm"&gt;System tables of a geodatabase stored in Oracle—Help | ArcGIS for Desktop&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-George&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Feb 2016 15:55:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/objectid-values-in-oracle/m-p/872557#M6308</guid>
      <dc:creator>George_Thompson</dc:creator>
      <dc:date>2016-02-24T15:55:58Z</dc:date>
    </item>
    <item>
      <title>Re: OBJECTID values in Oracle</title>
      <link>https://community.esri.com/t5/geodatabase-questions/objectid-values-in-oracle/m-p/872558#M6309</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's a bit more complicated than just a sequence, because sequence generation is too slow for bulk insert processes.&amp;nbsp; Instead, the sequence has an interval (size dependent on version) for a gap in values and a pipe is used to store the next value when a cursor is shut down.&amp;nbsp; When the next cursor comes along, it will fetch off the pipe before consulting the sequence, to prevent a gap.&amp;nbsp; If you shut down the instance, the DBMS_PIPE objects are lost, resulting in a gap in subsequent inserts (though there is a [somewhat elderly] &lt;A href="http://support.esri.com/es/knowledgebase/techarticles/detail/28835"&gt;KB document&lt;/A&gt; that addresses a workaround).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Feb 2016 17:47:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/objectid-values-in-oracle/m-p/872558#M6309</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2016-02-25T17:47:00Z</dc:date>
    </item>
  </channel>
</rss>

