<?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: Transfer ST_GEOMETRY data across Oracle Database Link - possible? in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/transfer-st-geometry-data-across-oracle-database/m-p/619985#M35026</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Nicholas,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;No one is jumping in to answer your question.&amp;nbsp; I've never tried this myself but I think the answer is "Probably No".&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You need to first check to see if both your instances involved in the database link have the same type oids for all the types and subcomponents of SDE.ST_GEOMETRY.&amp;nbsp; If you installed ArcSDE on your Oracle instance before 9.3 the values for the type oids were arbitrary and subsequent upgrades would not change them.&amp;nbsp; See&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://resources.arcgis.com/content/kbase?fa=articleShow&amp;amp;d=34928"&gt;http://resources.arcgis.com/content/kbase?fa=articleShow&amp;amp;d=34928&lt;/A&gt;&lt;BR /&gt;&lt;SPAN&gt;So none of my production servers have the same OIDs as they date back to 9.1 days.&amp;nbsp; Attempting to move SDE.ST_GEOMETRY from one to the other is futile as the servers will not recognize the other server's types as even being SDE.ST_GEOMETRY.&amp;nbsp; It might work if both servers were fresh installs of ArcSDE.&amp;nbsp; I looked at my 11gR2 test machine on which I installed 9.3.1 fresh and those types match the ids in the above mentioned article.&amp;nbsp; My production machines are slated for an 11gR2 upgrade but even then I think the type OIDs will stay the same.&amp;nbsp; Until someone rebuilds my production servers from scratch, I am stuck.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Secondly your ST_SRID coordinate system values from SDE.ST_SPATIAL_REFERENCES must match between servers.&amp;nbsp; Otherwise one server will have no idea what coordinate system the geometry from the other server has.&amp;nbsp; We've talked about this issue in the forum and how difficult this would be conquer. See&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://forums.arcgis.com/threads/3464-How-to-ensure-consistent-ST_Geometry-SRIDs-when-importing-feature-classes"&gt;http://forums.arcgis.com/threads/3464-How-to-ensure-consistent-ST_Geometry-SRIDs-when-importing-feature-classes&lt;/A&gt;&lt;BR /&gt;&lt;SPAN&gt;So the geometry on server A might have ST_SRID 66 meaning NAD83 but server B probably will have ST_SRID 66 assigned to some other coordinate system.&amp;nbsp; How do you bring this in harmony?&amp;nbsp; I have no idea.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thirdly, what are you really after in terms of using this database link?&amp;nbsp; If all you want to do is pull geometries from one server to another, then you might get things to work with some (a lot?) effort.&amp;nbsp; But if you expect to "work" across the database link with queries and such, you can forget it.&amp;nbsp; Domain indexes such as the SDE.ST_SPATIAL_INDEX don't work across database links.&amp;nbsp; This is the same for Oracle SDO_GEOMETRY.&amp;nbsp; You might want to look at&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://forums.oracle.com/forums/thread.jspa?threadID=375036"&gt;http://forums.oracle.com/forums/thread.jspa?threadID=375036&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Anyhow, that's my two cents and feel free to correct anything I misstated.&amp;nbsp; To my mind its just not worth the effort to try this.&amp;nbsp; If you are using Oracle and ArcSDE, why not overcome the first two issues by using MDSYS.SDO_GEOMETRY storage rather than SDE.ST_GEOMETRY?&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Paul&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Aug 2010 11:29:15 GMT</pubDate>
    <dc:creator>PaulDziemiela</dc:creator>
    <dc:date>2010-08-05T11:29:15Z</dc:date>
    <item>
      <title>Transfer ST_GEOMETRY data across Oracle Database Link - possible?</title>
      <link>https://community.esri.com/t5/data-management-questions/transfer-st-geometry-data-across-oracle-database/m-p/619983#M35024</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We have a Production instance Oracle 11.1.0.6.0 / SDE 9.3.1 and an Edit instance Oracle 11.1.0.6.0 / SDE 9.3.1 running on Solaris 10. ST_GEOMETRY set as default. No versioning. We have created a database link between the two instances.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm thinking about this method to make nightly updates from Edit to Production. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;i.e.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;delete * from geo.buildings (in Production)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;insert into geo.buildings (in Production) select * from geo.buildings@edit&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;a) I realise that I would have to generate the OBJECTID in geo.buildings (in Production) via the sequence number of geo.buildings (in Production).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;b) I would not use * in my final version but list the column names.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For a simple Polygon Feature Class located in the Edit instance is it possible to transfer data to Production instance across a database link? Any issues to be aware?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 May 2010 13:11:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/transfer-st-geometry-data-across-oracle-database/m-p/619983#M35024</guid>
      <dc:creator>NicholasO_Connor</dc:creator>
      <dc:date>2010-05-31T13:11:05Z</dc:date>
    </item>
    <item>
      <title>Re: Transfer ST_GEOMETRY data across Oracle Database Link - possible?</title>
      <link>https://community.esri.com/t5/data-management-questions/transfer-st-geometry-data-across-oracle-database/m-p/619984#M35025</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;...Any one using Database links to transfer data?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Jul 2010 09:10:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/transfer-st-geometry-data-across-oracle-database/m-p/619984#M35025</guid>
      <dc:creator>NicholasO_Connor</dc:creator>
      <dc:date>2010-07-28T09:10:53Z</dc:date>
    </item>
    <item>
      <title>Re: Transfer ST_GEOMETRY data across Oracle Database Link - possible?</title>
      <link>https://community.esri.com/t5/data-management-questions/transfer-st-geometry-data-across-oracle-database/m-p/619985#M35026</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Nicholas,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;No one is jumping in to answer your question.&amp;nbsp; I've never tried this myself but I think the answer is "Probably No".&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You need to first check to see if both your instances involved in the database link have the same type oids for all the types and subcomponents of SDE.ST_GEOMETRY.&amp;nbsp; If you installed ArcSDE on your Oracle instance before 9.3 the values for the type oids were arbitrary and subsequent upgrades would not change them.&amp;nbsp; See&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://resources.arcgis.com/content/kbase?fa=articleShow&amp;amp;d=34928"&gt;http://resources.arcgis.com/content/kbase?fa=articleShow&amp;amp;d=34928&lt;/A&gt;&lt;BR /&gt;&lt;SPAN&gt;So none of my production servers have the same OIDs as they date back to 9.1 days.&amp;nbsp; Attempting to move SDE.ST_GEOMETRY from one to the other is futile as the servers will not recognize the other server's types as even being SDE.ST_GEOMETRY.&amp;nbsp; It might work if both servers were fresh installs of ArcSDE.&amp;nbsp; I looked at my 11gR2 test machine on which I installed 9.3.1 fresh and those types match the ids in the above mentioned article.&amp;nbsp; My production machines are slated for an 11gR2 upgrade but even then I think the type OIDs will stay the same.&amp;nbsp; Until someone rebuilds my production servers from scratch, I am stuck.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Secondly your ST_SRID coordinate system values from SDE.ST_SPATIAL_REFERENCES must match between servers.&amp;nbsp; Otherwise one server will have no idea what coordinate system the geometry from the other server has.&amp;nbsp; We've talked about this issue in the forum and how difficult this would be conquer. See&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://forums.arcgis.com/threads/3464-How-to-ensure-consistent-ST_Geometry-SRIDs-when-importing-feature-classes"&gt;http://forums.arcgis.com/threads/3464-How-to-ensure-consistent-ST_Geometry-SRIDs-when-importing-feature-classes&lt;/A&gt;&lt;BR /&gt;&lt;SPAN&gt;So the geometry on server A might have ST_SRID 66 meaning NAD83 but server B probably will have ST_SRID 66 assigned to some other coordinate system.&amp;nbsp; How do you bring this in harmony?&amp;nbsp; I have no idea.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thirdly, what are you really after in terms of using this database link?&amp;nbsp; If all you want to do is pull geometries from one server to another, then you might get things to work with some (a lot?) effort.&amp;nbsp; But if you expect to "work" across the database link with queries and such, you can forget it.&amp;nbsp; Domain indexes such as the SDE.ST_SPATIAL_INDEX don't work across database links.&amp;nbsp; This is the same for Oracle SDO_GEOMETRY.&amp;nbsp; You might want to look at&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://forums.oracle.com/forums/thread.jspa?threadID=375036"&gt;http://forums.oracle.com/forums/thread.jspa?threadID=375036&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Anyhow, that's my two cents and feel free to correct anything I misstated.&amp;nbsp; To my mind its just not worth the effort to try this.&amp;nbsp; If you are using Oracle and ArcSDE, why not overcome the first two issues by using MDSYS.SDO_GEOMETRY storage rather than SDE.ST_GEOMETRY?&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Paul&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Aug 2010 11:29:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/transfer-st-geometry-data-across-oracle-database/m-p/619985#M35026</guid>
      <dc:creator>PaulDziemiela</dc:creator>
      <dc:date>2010-08-05T11:29:15Z</dc:date>
    </item>
    <item>
      <title>Re: Transfer ST_GEOMETRY data across Oracle Database Link - possible?</title>
      <link>https://community.esri.com/t5/data-management-questions/transfer-st-geometry-data-across-oracle-database/m-p/619986#M35027</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Nicholas&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The Data Interoperability extension solves this sort of problem.&amp;nbsp; You can get an evaluation license if you want to learn how.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Aug 2010 14:38:28 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/transfer-st-geometry-data-across-oracle-database/m-p/619986#M35027</guid>
      <dc:creator>BruceHarold</dc:creator>
      <dc:date>2010-08-06T14:38:28Z</dc:date>
    </item>
  </channel>
</rss>

