<?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>Error in sql created by Powermap v8i</title><link>https://communities.bentley.com/products/geospatial/desktop/f/bentley-map-forum/73224/error-in-sql-created-by-powermap-v8i</link><description>I registered few 3d features in GSA (Powermap v8i v08.11.07.97) from existing Oracle 10g database. To connect to database I&amp;#39;m using oracle client 11.1. When I&amp;#39;m executing query database from view Powermap is creating sql similar to: 
 SELECT GGAZ.PEGAZ_ODCINEK_GAZ_LN</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Re: Error in sql created by Powermap v8i</title><link>https://communities.bentley.com/thread/196312?ContentTypeID=1</link><pubDate>Tue, 17 Jan 2012 01:13:43 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:cb65c135-ef69-468e-a21f-b808fb0ef974</guid><dc:creator>Krister Surell</dc:creator><description>&lt;p&gt;I&amp;#39;ve seen this several times, both in good? old GeoGraphics and in Bentley Map. In my case (if I remember correct) the filter query used the wrong srid (NULL in my case). Could it be that your file has a different coordinate system?&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Krister&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Re: Error in sql created by Powermap v8i</title><link>https://communities.bentley.com/thread/194977?ContentTypeID=1</link><pubDate>Wed, 04 Jan 2012 01:20:05 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:b4732fe9-15df-423e-8de2-34be11489ba4</guid><dc:creator>Martin Roy</dc:creator><description>&lt;p&gt;You can try defining a 2D spatial index even on 3D data. Maybe that will work better.&lt;/p&gt;
&lt;p&gt;Hope this helps,&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp;Martin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Re: Error in sql created by Powermap v8i</title><link>https://communities.bentley.com/thread/194923?ContentTypeID=1</link><pubDate>Tue, 03 Jan 2012 19:55:25 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:7c8a732d-96eb-42f7-b614-d271e04cfedf</guid><dc:creator>Jerry Walter - Bentley</dc:creator><description>&lt;p&gt;Ok, good information concerning the view vs. all records. &lt;/p&gt;
&lt;p&gt;Most generally, when a view will not retrieve, but all records do, it means that the spatial index was created, but did not compile or index correctly. I have seen this as incorrect data in the geometry column. There are Oracle SDO routines that can be ran against a table to check to see if the sdo_geometry information is correct. These are well documented online:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://docs.oracle.com/cd/B28359_01/appdev.111/b28400/toc.htm#BEGIN"&gt;docs.oracle.com/.../toc.htm&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Re: Error in sql created by Powermap v8i</title><link>https://communities.bentley.com/thread/194908?ContentTypeID=1</link><pubDate>Tue, 03 Jan 2012 19:04:13 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:38fd0e62-802e-4240-80e9-123b697ceea5</guid><dc:creator>prusinek</dc:creator><description>&lt;p&gt;but problem is that entire sql query is generated by Powermap Database Query tool with chosen view as area, when I select all elements query runs fine and elements are generated correctly. If there is any place where I can take some control above generation process pls point me to it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Re: Error in sql created by Powermap v8i</title><link>https://communities.bentley.com/thread/194895?ContentTypeID=1</link><pubDate>Tue, 03 Jan 2012 18:17:33 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:0b80368d-0de0-4228-b07d-0e75e3953058</guid><dc:creator>Jerry Walter - Bentley</dc:creator><description>&lt;p&gt;Looks like there is a incomplete or wrongly defined geometry for the type defined in the record. You are defining a 3007 etype and the rest of teh SDO_GEOMETRY record may not fit this definition. Please make sure this is correct. &lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;From Oracle online documentation......&lt;/p&gt;
&lt;table style="width:100%;" class="Formal" title="Values and Semantics in SDO_ELEM_INFO" summary="Values and Semantics in SDO_ELEM_INFO" dir="ltr" frame="hsides" rules="groups" border="1" cellpadding="3" cellspacing="0"&gt;&lt;/table&gt;
&lt;table style="width:100%;" class="Formal" title="Values and Semantics in SDO_ELEM_INFO" summary="Values and Semantics in SDO_ELEM_INFO" dir="ltr" frame="hsides" rules="groups" border="1" cellpadding="3" cellspacing="0"&gt;
&lt;tbody&gt;
&lt;tr align="left" valign="top"&gt;
&lt;td id="r15c1-t5" headers="r1c1-t5" align="left"&gt;
&lt;p&gt;1007&lt;/p&gt;
&lt;/td&gt;
&lt;td headers="r15c1-t5 r1c2-t5" align="left"&gt;
&lt;p&gt;&lt;span class="italic"&gt;n&lt;/span&gt; = 1 or 3&lt;/p&gt;
&lt;/td&gt;
&lt;td headers="r15c1-t5 r1c3-t5" align="left"&gt;
&lt;p&gt;&lt;a id="sthref224" name="sthref224"&gt;&lt;/a&gt;Solid consisting of multiple surfaces that are completely enclosed in a three-dimensional space, so that the solid has an interior volume. A solid element can have one exterior surface defined by the 1006 elements and zero or more interior boundaries defined by the 2006 elements. The value &lt;span class="italic"&gt;n&lt;/span&gt; in the Interpretation column must be 1 or 3.&lt;/p&gt;
&lt;p&gt;Subsequent triplets in the SDO_ELEM_INFO array describe the exterior 1006 and optional interior 2006 surfaces that make up the solid element.&lt;/p&gt;
&lt;p&gt;&lt;a id="sthref225" name="sthref225"&gt;&lt;/a&gt;&lt;a id="sthref226" name="sthref226"&gt;&lt;/a&gt;If &lt;span class="italic"&gt;n&lt;/span&gt; is 3, the solid is an &lt;span class="italic"&gt;optimized box&lt;/span&gt;, such that only two three-dimensional points are required to define it: one with minimum values for the box in the X, Y, and Z dimensions and another with maximum values for the box in the X, Y, and Z dimensions. For example: &lt;code&gt;SDO_GEOMETRY(3008, NULL, NULL, SDO_ELEM_INFO_ARRAY(1,1007,3), SDO_ORDINATE_ARRAY(1,1,1, 3,3,3))&lt;/code&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>