<?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: Error migrating to ST_GEOMETRY in Geodatabase Questions</title>
    <link>https://community.esri.com/t5/geodatabase-questions/error-migrating-to-st-geometry/m-p/1031859#M7008</link>
    <description>&lt;P&gt;It may be best to work with Esri Technical Support on this moving forward. I have seen successful migrations in the past so not sure what is going on.&lt;/P&gt;</description>
    <pubDate>Tue, 02 Mar 2021 11:57:47 GMT</pubDate>
    <dc:creator>George_Thompson</dc:creator>
    <dc:date>2021-03-02T11:57:47Z</dc:date>
    <item>
      <title>Error migrating to ST_GEOMETRY</title>
      <link>https://community.esri.com/t5/geodatabase-questions/error-migrating-to-st-geometry/m-p/1031580#M7002</link>
      <description>&lt;P&gt;There are a number of feature classes in our current Oracle 12c/19 GDB that are still SDE Binary or ESRI LOB that I'm running an impact analysis on for upgrading to ST_GEOMETRY.&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I tried to use the Migrate Storage tool, I received an underlying DBMS error &amp;nbsp; (Error 000955).&amp;nbsp; Upon having a trace run on the backend, we found that&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The following statements encountered a error during parse:&lt;/P&gt;&lt;P&gt;SELECT * FROM SDE.SCH_DATASET&lt;/P&gt;&lt;P&gt;Error encountered: ORA-00942&lt;/P&gt;&lt;P&gt;--------------------------------------------------------------------------------&lt;BR /&gt;UPDATE MYSCHEMA.BIRDS_FEATURES SET SDE_CONVERSION = SDE.ST_GEOMETRY(:s1,:s2,:s3,:s4,:s5,:s6,:s7,:s8,:s9,:s10,:s11,:s12,:s13,:s14) WHERE SHAPE = :fid1&lt;/P&gt;&lt;P&gt;Error encountered: ORA-00600&lt;/P&gt;&lt;P&gt;So, it appears that SDE.SCH_DATASET doesn't exist (?) - is there a way to remedy this?&lt;/P&gt;&lt;P&gt;I think the preferred upgrade path (especially since it's what ESRI suggests) would be the Migrate Storage route.&amp;nbsp; The other route (copy, paste as ST, then rename) while successful, could raise too many impact issues on possible roles inherited, privs, and any underlying tables that get updated from a different interface.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Mar 2021 17:47:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/error-migrating-to-st-geometry/m-p/1031580#M7002</guid>
      <dc:creator>BartPittari</dc:creator>
      <dc:date>2021-03-01T17:47:16Z</dc:date>
    </item>
    <item>
      <title>Re: Error migrating to ST_GEOMETRY</title>
      <link>https://community.esri.com/t5/geodatabase-questions/error-migrating-to-st-geometry/m-p/1031676#M7004</link>
      <description>&lt;P&gt;What is the version of the ArcGIS client and Enterprise Geodatabase that you are using?&lt;/P&gt;&lt;P&gt;Are you running this GP tool as the data owner?&lt;/P&gt;&lt;P&gt;The ORA-00600 seems like an internal Oracle error parsing the SQL statement.&lt;BR /&gt;&lt;BR /&gt;Are these feature classes point / line / polygon FC's or have networks, topology, etc. with them?&lt;/P&gt;</description>
      <pubDate>Mon, 01 Mar 2021 21:14:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/error-migrating-to-st-geometry/m-p/1031676#M7004</guid>
      <dc:creator>George_Thompson</dc:creator>
      <dc:date>2021-03-01T21:14:13Z</dc:date>
    </item>
    <item>
      <title>Re: Error migrating to ST_GEOMETRY</title>
      <link>https://community.esri.com/t5/geodatabase-questions/error-migrating-to-st-geometry/m-p/1031680#M7005</link>
      <description>&lt;P&gt;Yes, the tool is being run as the schema owner.&lt;/P&gt;&lt;P&gt;The 600 error occurs during the update attempt.&amp;nbsp; I thought it may be related to the 942 error.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The FCs are all point, line, polygon ones, no topology or networks.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Mar 2021 21:24:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/error-migrating-to-st-geometry/m-p/1031680#M7005</guid>
      <dc:creator>BartPittari</dc:creator>
      <dc:date>2021-03-01T21:24:19Z</dc:date>
    </item>
    <item>
      <title>Re: Error migrating to ST_GEOMETRY</title>
      <link>https://community.esri.com/t5/geodatabase-questions/error-migrating-to-st-geometry/m-p/1031699#M7006</link>
      <description>&lt;P&gt;What version of Pro and Geodatabase (not the Oracle version) are you running this on?&lt;/P&gt;&lt;P&gt;Just checking that you reviewed this doc:&amp;nbsp;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-oracle/data-migration.htm" target="_blank"&gt;https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-oracle/data-migration.htm&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Mar 2021 22:00:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/error-migrating-to-st-geometry/m-p/1031699#M7006</guid>
      <dc:creator>George_Thompson</dc:creator>
      <dc:date>2021-03-01T22:00:16Z</dc:date>
    </item>
    <item>
      <title>Re: Error migrating to ST_GEOMETRY</title>
      <link>https://community.esri.com/t5/geodatabase-questions/error-migrating-to-st-geometry/m-p/1031703#M7007</link>
      <description>&lt;P&gt;I've tried in all versions we have (10.4.1, 10.8.1 and 2.5).&amp;nbsp; The Geodatabase version I think is 10.4.&amp;nbsp;&lt;/P&gt;&lt;P&gt;And yes, I reviewed that document and my data meets all the migration prerequisites.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Mar 2021 22:07:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/error-migrating-to-st-geometry/m-p/1031703#M7007</guid>
      <dc:creator>BartPittari</dc:creator>
      <dc:date>2021-03-01T22:07:20Z</dc:date>
    </item>
    <item>
      <title>Re: Error migrating to ST_GEOMETRY</title>
      <link>https://community.esri.com/t5/geodatabase-questions/error-migrating-to-st-geometry/m-p/1031859#M7008</link>
      <description>&lt;P&gt;It may be best to work with Esri Technical Support on this moving forward. I have seen successful migrations in the past so not sure what is going on.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Mar 2021 11:57:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/error-migrating-to-st-geometry/m-p/1031859#M7008</guid>
      <dc:creator>George_Thompson</dc:creator>
      <dc:date>2021-03-02T11:57:47Z</dc:date>
    </item>
  </channel>
</rss>

