ORA-13033 ORA-06512 at 11.1.0.7

Question

I have a single shape that seems to cause ORA-13033 at 11.1.0.7 but not at 11.1.0.6. Wondering if I am missing something stupid, or if anyone else has seen this problem. I did a quick search of the posts, but didn't find anything. It could also be that spatial has a problem on the 11.1.0.7 server...
Thanks
--on 11.1.0.7
SQL> drop index foo_spatial_index;
Index dropped.
SQL> drop table foo;
Table dropped.
SQL> delete from user_sdo_geom_metadata where table_name = 'FOO';
1 row deleted.
SQL>
SQL> create table foo (shape sdo_geometry);
Table created.
SQL> insert into foo values (SDO_GEOMETRY(3002, NULL, NULL, SDO_ELEM_INFO_ARRAY(1, 4, 1, 1, 2, 2), SDO_ORDINATE_ARRAY(484893.192, 1845442.68
, 0, 484881.786, 1845444.7, .5, 484871.639, 1845450.28, 1)));
1 row created.
SQL> insert into user_sdo_geom_metadata values('FOO', 'SHAPE', SDO_DIM_ARRAY(SDO_DIM_ELEMENT(NULL, 484719.102, 484904.266, .0000005), SDO_DI
M_ELEMENT(NULL, 1845366.11, 1845513.86, .0000005), SDO_DIM_ELEMENT(NULL, 0, 5368.70912, .0000005)), null );
1 row created.
SQL> create index foo_spatial_index on foo(shape) indextype is mdsys.spatial_index;
create index foo_spatial_index on foo(shape) indextype is mdsys.spatial_index
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13249: Error in spatial index: [mdrcrtxfergm]
ORA-13249: Error in spatial index: [mdpridxtxfergm]
ORA-13200: internal error [ROWID:AAFV8VAAHAAAGUtAAA] in spatial indexing.
ORA-13206: internal error [] while creating the spatial index
ORA-13033: Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
--on a different 11.1.0.6
SQL> drop index foo_spatial_index;
drop index foo_spatial_index
ERROR at line 1:
ORA-01418: specified index does not exist
SQL> drop table foo;
drop table foo
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> delete from user_sdo_geom_metadata where table_name = 'FOO';
0 rows deleted.
SQL>
SQL> create table foo (shape sdo_geometry);
Table created.
SQL> insert into foo values (SDO_GEOMETRY(3002, NULL, NULL, SDO_ELEM_INFO_ARRAY(1, 4, 1, 1, 2, 2), SDO_ORDINATE_ARRAY(484893.192, 1845442.68
, 0, 484881.786, 1845444.7, .5, 484871.639, 1845450.28, 1)));
1 row created.
SQL> insert into user_sdo_geom_metadata values('FOO', 'SHAPE', SDO_DIM_ARRAY(SDO_DIM_ELEMENT(NULL, 484719.102, 484904.266, .0000005), SDO_DI
M_ELEMENT(NULL, 1845366.11, 1845513.86, .0000005), SDO_DIM_ELEMENT(NULL, 0, 5368.70912, .0000005)), null );
1 row created.
SQL> create index foo_spatial_index on foo(shape) indextype is mdsys.spatial_index;
Index created.

Answer 1

There are a couple of things wrong with your geometry.
The specs says that for compound geometries (sdo_etype = 4) the SDO_INTERPRETATION (in this case with sdo_etype = 4) gives the numeber of subelements. This must be bigger then 1:
http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28400/sdo_objrelschema.htm#BGHDGCCE
4
n > 1
Compound line string with some vertices connected by straight line segments and some by circular arcs. The value n in the Interpretation column specifies the number of contiguous subelements that make up the line string.
The next n triplets in the SDO_ELEM_INFO array describe each of these subelements. The subelements can only be of SDO_ETYPE 2. The last point of a subelement is the first point of the next subelement, and must not be repeated.
In your case you either have single line string which makes the first triplet incorrect or even unnecessary in the SDO_ELEM_INFO, or you are missing a third triplet in the SDO_ELEM_INFO.
You should always validate your geometries first, if you do that also on your 11.1.0.6 version you will get:
SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT
54506 Point:0,Edge:2,
ORA-54506: compound curve not supported for 3-D geometries
Cause: The 3-D geometry contained one or more compound curves, which are not
supported for 3-D geometries.
Action: Remove all compound curves from the geometry.
As you will see additionally compound curveare not supported in 3D geometries.
IF it is not a compound (so with SDO_ELEM_INFO_ARRAY = (1,2,2), you will see that this geometry will validate.
Looks like the validation might be incorporated now in the index creation in 11.1.0.7.
Edited by: lucvanlinden on Mar 20, 2009 9:07 AM