<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>BM Oracle Connection</title><link>https://communities.bentley.com/products/geospatial/desktop/f/bentley-map-forum/46617/bm-oracle-connection</link><description>I am having a problem reading data from my Oracle Database. I am getting an error &amp;quot;There is no algorithm for assigning the given source geometry to the given target geometry, they do not match.&amp;quot; 
 
 
What does this error mean and how can I work around</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Re: BM Oracle Connection</title><link>https://communities.bentley.com/thread/105397?ContentTypeID=1</link><pubDate>Wed, 13 Jan 2010 00:25:48 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:977e1571-392e-43c3-a510-a4981e1b4eba</guid><dc:creator>IanTidy</dc:creator><description>&lt;p&gt;
Thanks Jerry,
&lt;/p&gt;
&lt;p&gt;
I found the problem.&amp;nbsp; The data was uploaded from MapInfo Tables (using EasyLoader), and although the geometeries where polylines, some contained multiple polylines (as a geometry collection or multi section line).&amp;nbsp; This is represented in Oracle as a MULITLINESTRING (as WKT).&amp;nbsp; These are what was causing the error.
&lt;/p&gt;
&lt;p&gt;
When I corrected the problem (by simplifing the geometries), and uploaded the data to Oracle, it all worked fine.&amp;nbsp; I am however having trouble adding and modifing XFM data in a Oracle connection.&amp;nbsp; I keep getting that the data is locked, and I can't seem to unlock it.&amp;nbsp; There are no locks on the Oracle server.&amp;nbsp; We are testing performing data maintenance without setting up the features through the GSA.
&lt;/p&gt;
&lt;p&gt;
Cheers Ian
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Re: BM Oracle Connection</title><link>https://communities.bentley.com/thread/105272?ContentTypeID=1</link><pubDate>Tue, 12 Jan 2010 16:42:14 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:89447db9-f388-49da-a9be-c8797bc89e7b</guid><dc:creator>Jerry Walter - Bentley</dc:creator><description>&lt;p&gt;
Ian;
&lt;/p&gt;
&lt;p&gt;
If you are usign Oracle Spatial , this looks like you may have a SDO_GEOMETRY type defined in teh table and a feature geometry type that does not match. Please make sure:
&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;There is only one geometry type defined for the spatial table.&lt;/li&gt;
	&lt;li&gt;The spatial index is set up and initiated.&lt;/li&gt;
	&lt;li&gt;You have at least 1 key filed defined.&lt;/li&gt;
	&lt;li&gt;You have registered features from the Oracle spatial datasource thru the GSA..&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
&amp;nbsp;
&lt;/p&gt;
&lt;p&gt;
These should take care of the matching of the geometry types between the Oracle Spatia ltable and the feature types.
&lt;/p&gt;
&lt;p&gt;
&amp;nbsp;
&lt;/p&gt;
&lt;p&gt;
If you are not using Oracle Spatial, just regular realational tables, then please provide more infromation. Version, table definition, feature definition.
&lt;/p&gt;
&lt;p&gt;
HTH
&lt;/p&gt;
&lt;p&gt;
Jerry
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>