<?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: modify/alter column length on sde9.3.1 for oracle in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/modify-alter-column-length-on-sde9-3-1-for-oracle/m-p/214117#M12325</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You're not changing the length of an ST_GEOMETRY, you're changing the display size of&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;numeric column in a table (which happens to contain a geometry column).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The supported mechanism to doing database design changes is to backup the table, drop &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;the table, recreate the table (with the new layout), and repopulate the table (from backup,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;if possible).&amp;nbsp; I use this nearly exclusively.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It may also be possible to use SQL to alter the table (if it's not versioned), then use 'sdetable&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;-o describe' (as the owner) to convince ArcSDE to re-evaluate the table contents.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Finally, the unsupported mechanisms involve hacking the column registry table and/or the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;geodatabase XML.&amp;nbsp; I *never* mess with the XML, since a simple mistake can trash the entire&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;instance (though the same is true for etiher mechanism, which is why they're unsupported).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 02 Sep 2012 11:11:53 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2012-09-02T11:11:53Z</dc:date>
    <item>
      <title>modify/alter column length on sde9.3.1 for oracle</title>
      <link>https://community.esri.com/t5/data-management-questions/modify-alter-column-length-on-sde9-3-1-for-oracle/m-p/214116#M12324</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I've created a feature class with arc catalog 10 in arcsde on oracle ST_GEOMETRY type.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I needed to change one of the columns from long integer 8 to long integer 10.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If I'm using pure oracle sql it's only changing the length in oracle, arc catalog still see the original length (8).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For some reason when we changed the text column the same way, arc catalog did see the changes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I've even looked in "ARCSDE Administration Command" both in "sdelayer" and "sdetable" but couldn�??t find any command but the one for changing data type.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What is the best way for changing column length on ST_GEOMETRY type?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Tank's ahead &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Iris Hadar&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Sep 2012 08:35:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/modify-alter-column-length-on-sde9-3-1-for-oracle/m-p/214116#M12324</guid>
      <dc:creator>irishadar</dc:creator>
      <dc:date>2012-09-02T08:35:47Z</dc:date>
    </item>
    <item>
      <title>Re: modify/alter column length on sde9.3.1 for oracle</title>
      <link>https://community.esri.com/t5/data-management-questions/modify-alter-column-length-on-sde9-3-1-for-oracle/m-p/214117#M12325</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You're not changing the length of an ST_GEOMETRY, you're changing the display size of&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;numeric column in a table (which happens to contain a geometry column).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The supported mechanism to doing database design changes is to backup the table, drop &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;the table, recreate the table (with the new layout), and repopulate the table (from backup,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;if possible).&amp;nbsp; I use this nearly exclusively.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It may also be possible to use SQL to alter the table (if it's not versioned), then use 'sdetable&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;-o describe' (as the owner) to convince ArcSDE to re-evaluate the table contents.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Finally, the unsupported mechanisms involve hacking the column registry table and/or the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;geodatabase XML.&amp;nbsp; I *never* mess with the XML, since a simple mistake can trash the entire&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;instance (though the same is true for etiher mechanism, which is why they're unsupported).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Sep 2012 11:11:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/modify-alter-column-length-on-sde9-3-1-for-oracle/m-p/214117#M12325</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2012-09-02T11:11:53Z</dc:date>
    </item>
  </channel>
</rss>

