Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

[solved] problems creating spatial index on SDO_ORDINATE_ARRAY in 11g

667716Feb 14 2011 — edited Feb 14 2011
We have a problem to create a spatial index on a field with geometries as SDO_ORDINATE_ARRAY points (3d) in 11g. The same method worked well in version 10.
Test case:

Create a new table:

CREATE TABLE "TESTUSER"."MYTEST"
(
"ID" VARCHAR2(15 BYTE),
"GEOM" "MDSYS"."SDO_GEOMETRY"
);


Register the GEOM field:

INSERT INTO USER_SDO_GEOM_METADATA VALUES
('MYTEST', 'GEOM',
MDSYS.SDO_DIM_ARRAY(
MDSYS.SDO_DIM_ELEMENT('X',4287662.44360155,4609289.08479709,5E-7),
MDSYS.SDO_DIM_ELEMENT('Y',5259525.06564855,5586464.07446503,5E-7),
MDSYS.SDO_DIM_ELEMENT('Z',0,10000,5E-7)),
31464);

Add some data:

INSERT INTO MYTEST ("ID", "GEOM") VALUES
('1', SDO_GEOMETRY(
3001,
31464,
NULL,
SDO_ELEM_INFO_ARRAY(1,1,1),
SDO_ORDINATE_ARRAY(4506206.54518109,5300630.21512683,459.255030927715,null)
)
);


Create spatial index

CREATE INDEX MYTEST_GIX ON MYTEST
(
"GEOM"
)
INDEXTYPE IS "MDSYS"."SPATIAL_INDEX";

The index will be created, but the building of the index will fail with the following error:

Error report:
SQL Error: 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:AACq+7AAEAAACscAAA] 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
29855. 00000 - "error occurred in the execution of ODCIINDEXCREATE routine"
*Cause: Failed to successfully execute the ODCIIndexCreate routine.
*Action: Check to see if the routine has been coded correctly.

Has anyone already experienced this problem or do you have any idea on how to solve it?

Regards. Carsten

Edited by: Carsten Heidmann on 14.02.2011 07:20: wrong tablename

Edited by: Carsten Heidmann on 14.02.2011 08:45
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 14 2011
Added on Feb 14 2011
1 comment
517 views