<?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 ObjectID sequence in an enterprise geodatabase (Oracle) in Geodatabase Questions</title>
    <link>https://community.esri.com/t5/geodatabase-questions/objectid-sequence-in-an-enterprise-geodatabase/m-p/724925#M163</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In an enterprise geodatabase (Oracle), why is the sequence for the ObjectID incremented by 16?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 29 Mar 2016 13:40:29 GMT</pubDate>
    <dc:creator>KyleDixon1</dc:creator>
    <dc:date>2016-03-29T13:40:29Z</dc:date>
    <item>
      <title>ObjectID sequence in an enterprise geodatabase (Oracle)</title>
      <link>https://community.esri.com/t5/geodatabase-questions/objectid-sequence-in-an-enterprise-geodatabase/m-p/724925#M163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In an enterprise geodatabase (Oracle), why is the sequence for the ObjectID incremented by 16?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Mar 2016 13:40:29 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/objectid-sequence-in-an-enterprise-geodatabase/m-p/724925#M163</guid>
      <dc:creator>KyleDixon1</dc:creator>
      <dc:date>2016-03-29T13:40:29Z</dc:date>
    </item>
    <item>
      <title>Re: ObjectID sequence in an enterprise geodatabase (Oracle)</title>
      <link>https://community.esri.com/t5/geodatabase-questions/objectid-sequence-in-an-enterprise-geodatabase/m-p/724926#M164</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Because sequences are so pitifully slow.. Instead of paying the sequence cost with each insert, ArcGIS grabs one sequence value and allocates all the values in that range itself.&amp;nbsp; If any values are left over, they are stuffed in a DBMS_PIPE for later reuse. Note that some sequences are set to 200 or even 400.&amp;nbsp; If you restart the database, the pipe contents are lost, which could result in gaps.&amp;nbsp; The Knowledge Base has documents which discuss both &lt;A href="http://support.esri.com/es/knowledgebase/techarticles/detail/31437"&gt;changing the interval &lt;/A&gt;and &lt;A href="http://support.esri.com/fr/knowledgebase/techarticles/detail/28835"&gt;preserving cached ids&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Mar 2016 14:08:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/objectid-sequence-in-an-enterprise-geodatabase/m-p/724926#M164</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2016-03-29T14:08:22Z</dc:date>
    </item>
  </channel>
</rss>

