Last updated on JUNE 02, 2011
Applies to:Oracle Spatial - Version: 10.2.0.4
Information in this document applies to any platform.
This occurs when hierarchical topology features are composed of a feature who
has the same numeric value for TG_LAYER_ID,TG_ID,TOPO_ID,TOPO_TYPE in
In the test case, table4 is a hierarchical feature layer that points to id 3
of table 3, which is associated with a polygon primitive with topo_id 3.
select * from TRICYCLE_relation$;
TG_LAYER_ID TG_ID TOPO_ID TOPO_TYPE
----------- ---------- ---------- ----------
3 3 3 3
The connect by loop error will happen (and has been occurring for us) any
time that the tg_layer_id/tg_id pair match the topo_id/topo_type pair, even
for 0-level layers in the topology. For example:
(TG_LAYER_ID,TG_ID,TOPO_ID,TOPO_TYPE) = (4,3,4,3)
throws the connect by loop error on get_geometry or get_topo_elements. So
would (we think) any tg_layer_id with this pattern so long as the tg_id is
1,2, or 3.”
Workaround: Ensure no feature is added to the topology that matches one of
the scenarios above.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms