ORA-13249: Error in Rtree .. Spatial Index fails 10.2.0.3.0
We have a table with spatial data (polygon), containing 2.4 million rows. SRID=8307. Creating spatial index fails on this table. Spatial version 10.2.0.3.0 and it is valid in dba_registry. Please help. Thanks in advance. Error message is
Error starting at line 3 in command:
CREATE INDEX SST_BASEDATA.SIDX_ISPSPATIALTEMP ON SST_BASEDATA.ISP_SPATIALTEMP (GEOMETRY)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS ('tablespace=tdx_basedata_isp layer_gtype=POLYGON') PARALLEL
Error report:
SQL Error: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: Error in Rtree: [mdrcrrdmddata, select /*+ PARALLEL(a, 32767) */ rid, cen from M8_1CC99$$ a where cen >= :1 and cen <= :2], 83243 83244
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
We have a similar problem with ORACLE 10.2.0.3, SRID 31297, 2-dimensional data, points, lines polygon.
We installed a new Computer (WINDOWS 2003 Server, Oracle 10.2.0.3) and transfered an application from an existing Oracle 10.2.0.2 instance.
We transferred the data by exp/imp utility.
The creation of the index failed (during import or creating the index by a sql command)
for all tables with more than 2 mill rows with the following message:
SQL Error: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
We did not get the ORA-13249 error.
For tables with less than 1 mill rows the index was created.
We decided to go back to Oracle 10.2.0.2 and all works fine.
We will upgrade the database to 10.2.0.3 when a patch will be available.
Similar Messages
-
Errors when creating spatial index
Hi,
I am new to OTN and oracle technology. I met a problem as I wanted to create a spatial index.
I created a table 'geoobject' with a column 'shape' of sdo_geometry.
The I run the following script:
insert into user_sdo_geom_metadata values ('geoobject', 'shape',
mdsys.sdo_dim_array(
mdsys.sdo_dim_element('latitude', 0.0000, 50.0000, 0.000050),
mdsys.sdo_dim_element('longitude', 0.0000, 80.0000, 0.000050)), 8265
after that I insert data into the table:
update geoobject set shape=
mdsys.sdo_geometry(2001, 8265,
mdsys.sdo_point_type
(to_number((select latitude from temp_location where temp_location.gid = geoobject.geo_id)),
to_number((select longitude from temp_location where temp_location.gid = geoobject.geo_id)), null),
null, null);
Then I wanted to create the spatial index:
create index geoobject_idx on geoobject(shape)
indextype is mdsys.spatial_index;
But I got the error messages:
Error in line 1:
ORA-29855: Fehler bei Ausführung der Routine ODCIINDEXCREATE (Error at running routine ODCIINDEXCREATE)
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13230: Temporäre Tabelle [temp-table: M2_7A21$$] konnte während Erstellen von R-Baum nicht erstellt werden
(temporary tables could not be established when R-tree was generated)
ORA-29400: Data Cartridge-Fehler
ORA-01659: Kann MINEXTENTS über 2 in Tablespace AMSDB hinaus nicht zuweisen
ORA-06512: in "MDSYS.SDO_INDEX_METHOD_9I", Zeile 7
ORA-06512: in Zeile 1
I read some messages from the OTN forum and got to know to test the data with the following script:
SELECT geo_id FROM geoobject
WHERE SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(shape, .005) <> 'TRUE';
All data passed this test.
Could somebody give me some suggestions?
regards,
YiweiMy spatial index has been successfully generated after i enlarged the tablespace. But I encounter a new problem.
I have saved many points in the table. I can use oracle spatial analyzer to see all the points. But as I tried to run the following query according to the examples in the oracle spatial user guider, I always get error messages. I have no idea about which problems there might be.
The Query is:
select geo_id, geo_name from geoobject g
where mdsys.sdo_filter
(g.shape, mdsys.sdo_geometry
(2003, null, null,
mdsys.sdo_elem_info_array(1, 1003, 1),
mdsys.sdo_ordinate_array(25.00, 60.00, 25.00, 70.00, 35.00, 70.00, 35.00, 60.00, 25.00, 60.00)
), 'querytype=WINDOW') ='true'
and sdo_relate
(g.shape, mdsys.sdo_geometry
(2003, null, null,
mdsys.sdo_elem_info_array(1, 1003, 1),
mdsys.sdo_ordinate_array(25.00, 60.00, 25.00, 70.00, 35.00, 70.00, 35.00, 60.00, 25.00, 60.00)
), 'masktype=TOUCH querytype=WINDOW') ='true';
The error messages are:
ERROR in line 1:
ORA-29902: Fehler bei der Ausführung von Routine ODCIIndexStart()
ORA-13207: Falsche Benutzung des Operators [SDO_FILTER]
ORA-06512: in "MDSYS.SDO_INDEX_METHOD_9I", Zeile 368
ORA-06512: in Zeile 1
I use SRID = 8307, I want to use Geodetic Coordinate Support. For that reason, as I insert the information into the database, I just insert '8307' as the SRID both in the geo table and in the table user_sdo_geom_metadata. Except for that I did nothing which seems to be related to support geodetic coordination system. I think the problems might be here.
I am looking forward to helps.
Yiwei -
Rebuilding spatial indexing fail after patch 9.2.0.8.0
Hi!
I did apply patchset, and after i did try to
set NLS_LANG=American_America.CL8MSWIN1251
sqlplusw ......
SQL> alter index XXXX.YYYYYYYY_g_idx rebuild; -- <- Russian name
alter index XXXX.YYYYYYYY_g_idx rebuild
ERROR at line 1:
ORA-29858: error occurred in the execution of ODCIINDEXALTER routine
ORA-29400: data cartridge error
¡a¤
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13205: internal error while parsing spatial parameters
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 259
ORA-06512: at line 1
As you can see, rebuilding was failed.
Before upgrade all did work fine.
If i will create table WITH_ENGLISH_NAME as SELECT from my table all working fine ;(
I DID apply all *.sql from patchset.
Any idea, gurus ?
P.S.
I did use script from metalink
verify_spatial_installation.sql :
SQL>
SQL> prompt Verify version and status
Verify version and status
SQL> select COMP_NAME, SCHEMA, VERSION, STATUS
2 from dba_registry where comp_id='SDO';
COMP_NAME SCHEMA VERSION STATUS
Spatial MDSYS 9.2.0.8.0 VALID
SQL>
SQL> prompt Number of objects
Number of objects
SQL> select count(*)
2 from dba_objects where owner='MDSYS';
COUNT(*)
250
SQL>
SQL> prompt Summary count of objects
Summary count of objects
SQL> select object_type, count(*)
2 from dba_objects where owner='MDSYS'
3 group by object_type;
OBJECT_TYPE COUNT(*)
FUNCTION 47
INDEX 17
INDEXTYPE 2
LIBRARY 12
LOB 12
OPERATOR 14
PACKAGE 25
PACKAGE BODY 25
SEQUENCE 2
TABLE 18
TRIGGER 7
TYPE 34
TYPE BODY 10
VIEW 25
14 rows selected.
SQL>
SQL> prompt Any invalid objects ?
Any invalid objects ?
SQL> select object_name, object_type, status
2 from dba_objects
3 where owner='MDSYS'
4 and status <> 'VALID'
5 order by object_name;
OBJECT_NAME OBJECT_TYPE STATUS
SDO_MIGRATE PACKAGE BODY INVALID
SQL>
SQL> prompt List of all spatial objects ordered by object_name
List of all spatial objects ordered by object_name
SQL> select object_name, object_type, status
2 from dba_objects where owner='MDSYS'
3 order by object_name;
OBJECT_NAME OBJECT_TYPE STATUS
AGGRCENTROID TYPE VALID
AGGRCENTROID TYPE BODY VALID
AGGRCONVEXHULL TYPE VALID
AGGRCONVEXHULL TYPE BODY VALID
AGGRLRSCONCAT TYPE VALID
AGGRLRSCONCAT TYPE BODY VALID
AGGRLRSCONCAT3D TYPE VALID
AGGRLRSCONCAT3D TYPE BODY VALID
AGGRMBR TYPE VALID
AGGRMBR TYPE BODY VALID
AGGRUNION TYPE VALID
AGGRUNION TYPE BODY VALID
ALL_GEOMETRY_COLUMNS VIEW VALID
ALL_SDO_GEOM_METADATA VIEW VALID
ALL_SDO_INDEX_INFO VIEW VALID
ALL_SDO_INDEX_METADATA VIEW VALID
ALL_SDO_LRS_METADATA VIEW VALID
ALL_SDO_MAPS VIEW VALID
ALL_SDO_STYLES VIEW VALID
ALL_SDO_THEMES VIEW VALID
CS_SRS TABLE VALID
DBA_GEOMETRY_COLUMNS VIEW VALID
DBA_SDO_INDEX_INFO VIEW VALID
DBA_SDO_INDEX_METADATA VIEW VALID
DBA_SDO_LRS_METADATA VIEW VALID
DBA_SDO_MAPS VIEW VALID
DBA_SDO_STYLES VIEW VALID
DBA_SDO_THEMES VIEW VALID
F81_INDEX_OBJECT TYPE VALID
F81_INDEX_OBJ_ARRAY TYPE VALID
F81_NT_IND_TYPE TYPE VALID
GEOCODER_HTTP PACKAGE VALID
GEOCODER_HTTP PACKAGE BODY VALID
GEOCODE_RESULT TYPE VALID
GEODETIC_SRIDS VIEW VALID
H81_INDEX_OBJECT TYPE VALID
H81_INDEX_OBJ_ARRAY TYPE VALID
H81_NT_IND_TYPE TYPE VALID
HHAND FUNCTION VALID
HHBYTELEN FUNCTION VALID
HHCBIT FUNCTION VALID
HHCELLBNDRY FUNCTION VALID
HHCELLSIZE FUNCTION VALID
HHCLDATE FUNCTION VALID
HHCOLLAPSE FUNCTION VALID
HHCOMMONCODE FUNCTION VALID
HHCOMPARE FUNCTION VALID
HHCOMPOSE FUNCTION VALID
HHDECODE FUNCTION VALID
HHDISTANCE FUNCTION VALID
HHENCODE FUNCTION VALID
HHENCODE_BYLEVEL FUNCTION VALID
HHGBIT FUNCTION VALID
HHGETCID FUNCTION VALID
HHGROUP FUNCTION VALID
HHGTBIT FUNCTION VALID
HHGTYPE FUNCTION VALID
HHIDLPART FUNCTION VALID
HHIDPART FUNCTION VALID
HHINCRLEV FUNCTION VALID
HHJLDATE FUNCTION VALID
HHLENGTH FUNCTION VALID
HHLEVELS FUNCTION VALID
HHMATCH FUNCTION VALID
HHMAXCODE FUNCTION VALID
HHNCOMPARE FUNCTION VALID
HHNDIM FUNCTION VALID
HHOR FUNCTION VALID
HHORDER FUNCTION VALID
HHPRECISION FUNCTION VALID
HHSBIT FUNCTION VALID
HHSETCID FUNCTION VALID
HHSTBIT FUNCTION VALID
HHSTYPE FUNCTION VALID
HHSUBDIVIDE FUNCTION VALID
HHSUBSTR FUNCTION VALID
HHXOR FUNCTION VALID
LOCATOR_WITHIN_DISTANCE OPERATOR VALID
MD PACKAGE VALID
MD PACKAGE BODY VALID
MD$RELATE TABLE VALID
MD1 PACKAGE VALID
MD1 PACKAGE BODY VALID
MD2 PACKAGE VALID
MD2 PACKAGE BODY VALID
MDERR PACKAGE VALID
MDERR PACKAGE BODY VALID
MDPRVT_IDX PACKAGE VALID
MDPRVT_IDX PACKAGE BODY VALID
MD_LRS PACKAGE VALID
MD_LRS PACKAGE BODY VALID
OGIS_GEOMETRY_COLUMNS TABLE VALID
OGIS_SPATIAL_REFERENCE_SYSTEMS TABLE VALID
ORDMD_AG_LIBS LIBRARY VALID
ORDMD_CS_LIBS LIBRARY VALID
ORDMD_IDX_LIBS LIBRARY VALID
ORDMD_LRS_LIBS LIBRARY VALID
ORDMD_MBR_LIBS LIBRARY VALID
ORDMD_MIG_LIBS LIBRARY VALID
ORDMD_PRIDX_LIBS LIBRARY VALID
ORDMD_REL_LIBS LIBRARY VALID
ORDMD_RTREE_LIBS LIBRARY VALID
ORDMD_UDT_LIBS LIBRARY VALID
ORDMD_UTL_LIBS LIBRARY VALID
ORDMD_WD_LIBS LIBRARY VALID
PK_SDO_MASK INDEX VALID
PK_SRID INDEX VALID
PRVT_IDX PACKAGE VALID
PRVT_IDX PACKAGE BODY VALID
RTREE_FILTER OPERATOR VALID
RTREE_IDX PACKAGE VALID
RTREE_IDX PACKAGE BODY VALID
RTREE_INDEX INDEXTYPE VALID
RTREE_INDEX_METHOD TYPE VALID
RTREE_INDEX_METHOD TYPE BODY VALID
RTREE_NN OPERATOR VALID
SAMPLE_SEQ SEQUENCE VALID
SDO PACKAGE VALID
SDO PACKAGE BODY VALID
SDOAGGR TYPE VALID
SDOAGGR TYPE BODY VALID
SDOAGGRTYPE TYPE VALID
SDO_3GL PACKAGE VALID
SDO_3GL PACKAGE BODY VALID
SDO_ADMIN PACKAGE VALID
SDO_ADMIN PACKAGE BODY VALID
SDO_AGGR_CENTROID FUNCTION VALID
SDO_AGGR_CONVEXHULL FUNCTION VALID
SDO_AGGR_LRS_CONCAT FUNCTION VALID
SDO_AGGR_LRS_CONCAT_3D FUNCTION VALID
SDO_AGGR_MBR FUNCTION VALID
SDO_AGGR_UNION FUNCTION VALID
SDO_ANGLE_UNITS TABLE VALID
SDO_AREA_UNITS TABLE VALID
SDO_CATALOG PACKAGE VALID
SDO_CATALOG PACKAGE BODY VALID
SDO_CONSTRUCT_DIM_ARRAY FUNCTION VALID
SDO_CS PACKAGE VALID
SDO_CS PACKAGE BODY VALID
SDO_DATUMS TABLE VALID
SDO_DIM_ARRAY TYPE VALID
SDO_DIM_ELEMENT TYPE VALID
SDO_DIST_UNITS TABLE VALID
SDO_DROP_USER TRIGGER VALID
SDO_ELEM_INFO_ARRAY TYPE VALID
SDO_ELLIPSOIDS TABLE VALID
SDO_FILTER OPERATOR VALID
SDO_GEOM PACKAGE VALID
SDO_GEOM PACKAGE BODY VALID
SDO_GEOMETRY TYPE VALID
SDO_GEOMETRY TYPE BODY VALID
SDO_GEOM_IDX INDEX VALID
SDO_GEOM_METADATA_TABLE TABLE VALID
SDO_GEOM_TRIG_DEL1 TRIGGER VALID
SDO_GEOM_TRIG_INS1 TRIGGER VALID
SDO_GEOM_TRIG_UPD1 TRIGGER VALID
SDO_IDX PACKAGE VALID
SDO_IDX PACKAGE BODY VALID
SDO_IDX_MDATA_IDX INDEX VALID
SDO_IDX_TAB_SEQUENCE SEQUENCE VALID
SDO_INDEX_METADATA_TABLE TABLE VALID
SDO_INDEX_METHOD_9I TYPE VALID
SDO_INDEX_METHOD_9I TYPE BODY VALID
SDO_INT2_FILTER OPERATOR VALID
SDO_INT2_RELATE OPERATOR VALID
SDO_INT_FILTER OPERATOR VALID
SDO_INT_RELATE OPERATOR VALID
SDO_LRS PACKAGE VALID
SDO_LRS PACKAGE BODY VALID
SDO_LRS_METADATA_TABLE TABLE VALID
SDO_LRS_META_IDX INDEX VALID
SDO_LRS_TRIG_DEL TRIGGER VALID
SDO_LRS_TRIG_INS TRIGGER VALID
SDO_LRS_TRIG_UPD TRIGGER VALID
SDO_MAPS_TABLE TABLE VALID
SDO_MBR TYPE VALID
SDO_META PACKAGE VALID
SDO_META PACKAGE BODY VALID
SDO_MIGRATE PACKAGE VALID
SDO_MIGRATE PACKAGE BODY INVALID
SDO_NN OPERATOR VALID
SDO_NN_DISTANCE OPERATOR VALID
SDO_NUMTAB TYPE VALID
SDO_ORDINATE_ARRAY TYPE VALID
SDO_POINT_TYPE TYPE VALID
SDO_PRIDX PACKAGE VALID
SDO_PRIDX PACKAGE BODY VALID
SDO_PROJECTIONS TABLE VALID
SDO_RELATE OPERATOR VALID
SDO_RELATEMASK_TABLE VIEW VALID
SDO_RELATE_MASK PACKAGE VALID
SDO_RELATE_MASK PACKAGE BODY VALID
SDO_RID_ARRAY TYPE VALID
SDO_RTREE_ADMIN PACKAGE VALID
SDO_RTREE_ADMIN PACKAGE BODY VALID
SDO_RTREE_FILTER OPERATOR VALID
SDO_RTREE_RELATE OPERATOR VALID
SDO_STAT TYPE VALID
SDO_STATTAB TYPE VALID
SDO_STYLES_TABLE TABLE VALID
SDO_THEMES_IDX INDEX VALID
SDO_THEMES_TABLE TABLE VALID
SDO_TUNE PACKAGE VALID
SDO_TUNE PACKAGE BODY VALID
SDO_UTIL PACKAGE VALID
SDO_UTIL PACKAGE BODY VALID
SDO_VERSION FUNCTION VALID
SDO_VPOINT_TYPE TYPE VALID
SDO_WITHIN_DISTANCE OPERATOR VALID
SPATIAL_INDEX INDEXTYPE VALID
SYS_C001565 INDEX VALID
SYS_C001571 INDEX VALID
SYS_C001706 INDEX VALID
SYS_LOB0000027008C00040$$ LOB VALID
SYS_LOB0000027008C00041$$ LOB VALID
SYS_LOB0000027053C00012$$ LOB VALID
SYS_LOB0000027053C00013$$ LOB VALID
SYS_LOB0000027209C00004$$ LOB VALID
SYS_LOB0000027216C00005$$ LOB VALID
SYS_LOB0000027216C00006$$ LOB VALID
SYS_LOB0000027216C00013$$ LOB VALID
SYS_LOB0000027216C00014$$ LOB VALID
SYS_LOB0000027229C00006$$ LOB VALID
SYS_LOB0000028651C00012$$ LOB VALID
SYS_LOB0000028651C00013$$ LOB VALID
TRANSFORM_MAP PACKAGE VALID
TRANSFORM_MAP PACKAGE BODY VALID
UNIQUE_ANGLE_UNITS INDEX VALID
UNIQUE_AREA_UNITS INDEX VALID
UNIQUE_DIST_UNITS INDEX VALID
UNIQUE_LAYERS INDEX VALID
UNIQUE_MAPS INDEX VALID
UNIQUE_STYLES INDEX VALID
UNIQUE_TABLES INDEX VALID
UNIQUE_THEMES INDEX VALID
USER_CS_SRS TABLE VALID
USER_GEOMETRY_COLUMNS VIEW VALID
USER_SDO_GEOM_METADATA VIEW VALID
USER_SDO_INDEX_INFO VIEW VALID
USER_SDO_INDEX_METADATA VIEW VALID
USER_SDO_LRS_METADATA VIEW VALID
USER_SDO_MAPS VIEW VALID
USER_SDO_STYLES VIEW VALID
USER_SDO_THEMES VIEW VALID
USER_TRANSFORM_MAP TABLE VALID
V81_INDEX_OBJECT TYPE VALID
V81_INDEX_OBJ_ARRAY TYPE VALID
V81_NT_IND_TYPE TYPE VALID
VERTEX_SET_TYPE TYPE VALID
VERTEX_TYPE TYPE VALID
250 rows selected.
SQL>
SQL> spool offSir! No Sir! :)
I will try to explain.
If I do have table with russian letter, than creating index creation will fail, no matter name of index :(
But if I will prepare copy of my table with english name (including meta-data) - index creations is succesfull. -
Error when creating spatial index in 10g
Hello.
I have a problen when I try to create a spatial index. The strange thing is that the same commands always works fine in some machines, but if always fails in others. I tryed in diferent versiones of Oracle, but I have the error in al of them. The versions I have tryed are:
- 10.2.0.1
- 10.2.0.4
The operating systems are:
Windows XP professional 32 bits
Windows 2003 Server 32 bits
These are the steps i make:
1) Create a Table with a SDO_GEOMETRY column (GEOMETRY)
2) Load data with SQLLDR (I hve tryed different SRID's, and all fail)
So far everything is ok
3) Create the INDEX
When I execute the CREATE INDEX command CREATE INDEX MADRID_SX ON MADRID (GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX;
I obtain the error:
ERROR en linea 1:+
ORA-29855: se ha producido un error en la ejecucion de la rutina+
ODCIINDEXCREATE+
ORA-13282: fallo al inicializar la transformacion de coordenadas+
ORA-06512: en "MDSYS.SDO_INDEX_METHOD_10I", line 10+
I too have noticed that if I execute the next command, I have an error:
SELECT MDSYS.sdo_cs.transform(sdo_geometry(2001,8192,sdo_point_type(13.6,52.4,null),null,null),25830) from dual;
ERROR en linea 1:+
ORA-13282: fallo al inicializar la transformacion de coordenadas+
ORA-06512: en "MDSYS.SDO_CS", linea 75+
ORA-06512: en "MDSYS.SDO_CS", linea 112+
ORA-06512: en "MDSYS.SDO_CS", linea 2678+
And if I execute the next command, I too have another error:
SELECT SDO_CS.VALIDATE_WKT(25830) FROM DUAL;
FALSE (169)*
Any ideas? Could it be related with something inside the machines, user privileges, etc.?
Thanks in advance.I have found that the problem is to use a SRID of AUTH_NAME column in MDSYS.CS_SRS table without the value "Oracle." in it.
If I use an Oracle’s SRID, everything works fine. If I use an EPSG’s SRID, fails.
For example, this command uses an Oracle SRID (8192) and one from the EPSG (25830), and fails:
SELECT MDSYS.sdo_cs.transform(sdo_geometry(2001,8192,sdo_point_type(13.6,52.4,null),null,null),25830) from dual;
ERROR en linea 1:
ORA-13282: fallo al inicializar la transformacion de coordenadas
ORA-06512: en "MDSYS.SDO_CS", linea 79
ORA-06512: en "MDSYS.SDO_CS", linea 116
ORA-06512: en "MDSYS.SDO_CS", linea 2690
However, if I use two Oracle SRID (8192 and 83030), it works.
SELECT MDSYS.sdo_cs.transform(sdo_geometry(2001,8192,sdo_point_type(13.6,52.4,null),null,null),83030) from dual;
SDO_GEOMETRY(2001, 83030, SDO_POINT_TYPE(1625183.71, 5936269.06, NULL), NULL, NULL
Therefore, the problem seems to be to use a non Oracle SRID. -
ORA-13199 Error on a spatial query
Hi,
I am getting following Error on a spatial query (on version 11.1.0.7)
"ORA-13199: Dimensionalities of geometry (GTYPE 3003) and diminfo (2) do not match.
ORA-06512: at "MDSYS.MD", line 1723
ORA-06512: at "MDSYS.MDERR", line 17
ORA-06512: at "MDSYS.SDO_CS", line 2809
ORA-06512: at "MDSYS.SDO_3GL", line 182 "
The same query used to work fine on 10.2.
My query looks like
Select Sfilt.GEOMETRY FROM
(Select TA.GEOMETRY FROM LANDPLAN.TOPOAREA TA, TEST.PLAN PL
WHERE PL.PLAN_ID = 12345 AND TA.LOC_CODE = 7
AND SDO_FILTER(TA.GEOMETRY,PL.GEOMETRY) = 'TRUE'
) Sfilt
,TEST.PLAN PL2 WHERE
PL2.PLAN_ID = 12345 AND
SDO_RELATE(PL2.GEOMETRY, sfilt.GEOMETRY, 'mask=anyinteract') = 'TRUE';
in the above data TEST.PLAN table is 2D table and LANDPLAN.TOPOAREA is 3D table and both are indexed.
Any help appriciated..Siva,
Thank you for your response. Now I have tried by increasing the DIMINFO (rebuiding the index) to three.
Now it shows below error..
ORA-29902: error in executing ODCIIndexStart() routine
ORA-13243: specified operator is not supported for 3- or higher-dimensional R-tree
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 416
I didn't reason now...for clarity
Can I have 3d layer with 2d index's ?
If Yes, can Spatial query work using these 2d index's against other 2d layer and 3d layers ? -
Spatial index fails for arcs in geodetic data
Where is the documentation for describing the differences between Oracle 8.1.7.2 and Oracle 9.2.0.3 for Spatial? We have 8.1.7.2 for production and are testing 9.2.0.3 in development. Data that loads and builds spatial indexes just fine in 8i fails miserably with the 'arcs in geodetic data' error in 9i. Catpatch.sql has been run twice for the 9i database. What specifically has changed in 9i to prevent the spatial r-tree indexing of geodetic data in 9i? I have run the sdo_geom.sdo_arc_densify and the indexes still fails. No problems were found with the geometry using the sdo_geom.validate_geometry_with_context and indexes still fail. Changed the tolerances on test data and still no indexes.
Any information would be appreciated. Thanks!Hi,
Arcs, compound line segments containing arcs, circles, and optimized rectangles are not supported for geodetic data in 9i. Also, the distance between two coordinates specified in spatial cannot be equal to or greater than 1/2 the great circle distance around the Earth, and single polygons must be smaller than 1/2 the Earth's surface area. All of the above is associated with geodetic data.
Also, tolerance for geodetic data is specified in meters, where previously the tolerance was specified in degrees. Also, the bounds of the coordinate system have to be -180 to 180 in longitude, and -90 to 90 in latitude (tolerance and bounds are set in user_sdo_geom_metadata).
If you want to continue using your data as you had been in 8i, you should probably remove the spatial reference system id in the data and in user_sdo_geom_metadata.
However, the whole earth geometry model will get you a lot of functionality, so you should consider modifying your data to adhere to the rules of geodetic data.
Hope this helps,
Dan -
Insert using Spatial Index fails when called from PHP
I have a stored procedure that inserts into a table with a spatial index on one of its fields.
When I run the procedure from SQL Server Management Studio it runs just fine.
When I run it from PHP, it returns the error: "INSERT failed because the following SET options have incorrect settings: 'CONCAT_NULL_YIELDS_NULL, ANSI_WARNINGS, ANSI_PADDING'. Verify that SET options are correct for use with indexed views and/or indexes
on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations"
From within Management Studio, I have tried many different combinations of settings, until I wound up with the list I have in the procedure below.
Within Managment Studio the error changes based on the options I have set, but PHP always replies with: 'CONCAT_NULL_YIELDS_NULL, ANSI_WARNINGS, ANSI_PADDING'
I have configured PHP to use the same SQL user as management studio, and I have tried both mssql_query and mssql_execute with bound parameters.
The spatial index is on the field post.location If I remove the spatial index it works, but I need the spatial index.
CREATE PROCEDURE insert_post ( @subject AS VARCHAR(250), @body AS VARCHAR(2000), @latitude AS FLOAT, @longitude AS FLOAT ) AS BEGIN
SET NOCOUNT ON
SET ANSI_WARNINGS ON
SET ANSI_PADDING ON
SET CONCAT_NULL_YIELDS_NULL ON
SET NUMERIC_ROUNDABORT OFF
DECLARE @location AS geography = geography::Point(@latitude, @longitude, 4326)
INSERT INTO post
subject,
body,
location
) VALUES (
@subject,
@body,
@location
ENDHi Charles
Your issue looks like it have two basic sources: (1) The connection string properties, (2) The table structure and the data which you try to insert.
(1) The connection string properties can be specified in various ways.
You can set most of them during the connection, depending on the provider which you are using. We did not get from you any information about the PHP code, so we have no information regarding this part.
The connection properties can be changed after the connection was made, which is basically what you have try to do. But we don't know what properties
are differents (since you .. the PHP code..) but you can check those properties dynamically, insert them to a table and then compare. To check all the properties you can use this post:
http://ariely.info/Blog/tabid/83/EntryId/153/SQL-Server-Get-Connection-Properties.aspx
(2) We need to understand your
table structure and compare it to yours query. Please post your DDL+DML (queries to create the table and to insert some sample data), and the full SP code
as it is now.
[Personal Site] [Blog] [Facebook] -
ORA-22813 error when deleting spatial objects in LIVE
Hi,
We are getting an ORA-22813 error when attempting to delete a spatial object from a version-enabled table in workspace LIVE. The spatial object to be removed has a SDO type of multipolygon. The geometry information consists of 4 rings with a combined ordinate count of 4120. The statement used to delete the row is:
delete from tableA where tableA.id in (select tableA.id from tableA where tableA.id = 3);
The error occurs only on a 10g R1 Oracle instance (10.1.0.5.0) with Workspace Manager version 10.1.0.7.1. The delete operation succeeds without problems on a 10g R2 (10.2.0.2.0) instance with Workspace Manager version 10.2.0.3.1. The statement is also executed successfully on the 10g R1 instance if the table is not version-enabled.
Any help on this would be appreciated.
ThanksHi,
I would recommend filing a TAR in this one. The only ora-22813 error involving workspace manager and geometry columns that I know about involves queries that need to sort data for which the size of the geometry column was >30k. Does the execution plan for the delete statement involve any kind of sort? However, this is an old 9.2 bug, that I believe was fixed for all 10.1 and newer releases.
Does the same error happen if you do not use the subquery?
Regards,
Ben -
Ora-29879 on creating a spatial index
Database version 11.2.0.1
--STEP 1
DELETE FROM USER_SDO_GEOM_METADATA WHERE table_name='P_WALLACE_WORKPLAN';
commit;
--STEP 2
INSERT INTO USER_SDO_GEOM_METADATA
(table_name, column_name, diminfo,srid )
VALUES ('P_WALLACE_WORKPLAN','GEOMETRY',
MDSYS.SDO_DIM_ARRAY(
MDSYS.SDO_DIM_ELEMENT('X', -2.147E+09, 2147483647, .000005),
MDSYS.SDO_DIM_ELEMENT('Y', -2.147E+09, 2147483647, .000005)),4000000);
commit;
select * from user_sdo_geom_metadata WHERE table_name='P_WALLACE_WORKPLAN';
-- RECORD DOES EXIST
--STEP 3
drop index P_WALLACE_WORKPLAN_INDX_RTREE force;
-- DOESNT EXIST
--STEP 4
CREATE INDEX P_WALLACE_WORKPLAN_INDX_RTREE
ON P_WALLACE_WORKPLAN (GEOMETRY) INDEXTYPE IS
MDSYS.SPATIAL_INDEX PARAMETERS (' SDO_INDX_DIMS=3
LAYER_GTYPE="COLLECTION" SDO_RTR_PCTFREE=2 INITIAL=64K
NEXT=8192 MINEXTENTS=1 MAXEXTENTS=2147483645 PCTINCREASE=0');
--error ORA-29879 cannot create multiple domain indexes on a column list using same indextypeYour example works for me with little adjustments:
DROP TABLE P_WALLACE_WORKPLAN;
CREATE TABLE P_WALLACE_WORKPLAN(
id NUMBER,
GEOMETRY MDSYS.SDO_GEOMETRY);
DELETE FROM USER_SDO_GEOM_METADATA WHERE table_name='P_WALLACE_WORKPLAN';
COMMIT;
--STEP 2
-- SRID 4000000 does not exist ?!
-- changed to 2029
-- added third dimension
INSERT INTO USER_SDO_GEOM_METADATA
(table_name, column_name, diminfo,srid )
VALUES ('P_WALLACE_WORKPLAN','GEOMETRY',
MDSYS.SDO_DIM_ARRAY(
MDSYS.SDO_DIM_ELEMENT('X', -2.147E+09, 2147483647, .000005),
MDSYS.SDO_DIM_ELEMENT('Y', -2.147E+09, 2147483647, .000005),
MDSYS.SDO_DIM_ELEMENT('Z', 0, 10000, .000005)
),2029);
COMMIT;
SELECT table_name from user_sdo_geom_metadata
WHERE table_name='P_WALLACE_WORKPLAN';
-- RECORD DOES EXIST
--STEP 3
DROP INDEX p_wallace_workplan_indx_rtree FORCE;
-- DOESNT EXIST
--STEP 4
-- here the geometry is 3-dimensional
CREATE INDEX P_WALLACE_WORKPLAN_INDX_RTREE
ON P_WALLACE_WORKPLAN (GEOMETRY) INDEXTYPE IS
MDSYS.SPATIAL_INDEX PARAMETERS (' SDO_INDX_DIMS=3
LAYER_GTYPE="COLLECTION" SDO_RTR_PCTFREE=2 INITIAL=64K
NEXT=8192 MINEXTENTS=1 MAXEXTENTS=2147483645 PCTINCREASE=0'); -
Spatial index creation fails in oracle9i but works in 8i
Hi--
i'm using oracle9.0.1.2.0 and arcSDE on solaris 8
when i create a spatial feature table and index oracle gives me the foloowing error:
Extended error code(29855): 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-13236: internal error in R-tree processing: [failed to cluster in memory]
ORA-13249: Internal error in Spatial index: [mdrcrclmem]
ORA-13232: failed to allocate memory during R-tree creation
ORA-13249: Error in Rtree: [mdrcrrdtbl, select /*+ PARALLEL 4 */ rid , min_d1, max_d1 , min_d2, max_d2 from (select rownum rnum, rid , m(MDSYS.SPATIAL_INDEX)
this occurs whether i use cov2sde at the command line or Create Index in sqlplus:
SQL> create index COUNTY_IDX on COUNTY_SDO(shape)
2 indextype is mdsys.spatial_index
3 parameters ('SDO_INDX_DIMS=2 tablespace=sde2_idx');
create index COUNTY_IDX on COUNTY_SDO(shape)
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: Stmt-Execute Failure: SELECT count(*) from SDE.COUNTY_SDO
ORA-29400: data cartridge error
ORA-01116: error in opening database file 14
ORA-01110: data file 14: '/u04/oradata/GIS2/sde3_idx01.dbf'
ORA-27041: unable to open file
SVR4 Error: 24: Too many open files
Additional information: 3
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 7
ORA-06512: at line 1
the bizarre thing is that everything works tickety-boo in oracle 8i *8.1.7.3)
has anyone run across this?
cheers
--kassimthanks for the suggestion, but that didnt work either
i increased the file descriptor limit from 256 to 2048 (my sysadmin sez that could break lots of things in solaris and had another go:
elvis{1}% ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 2048
vmemory(kbytes) unlimited
lvis{2}% cov2sde -o create -l plstrfill_sdo,shape -f $GISDATA/survey.ws/plstr_fill,poly -e a -R 1 -k spatial -a file=$GISDATA/survey.ws/plstr_fields.txt -g SPIDX_RTREE
ArcSDE 8.2 Build 115 Wed Mar 6 09:48:27 PST 2002
Coverage to Layer Loading Administration Utility
Reading column selection file "/data/jack02/in_put/survey.ws/plstr_fields.txt"
Library /data/jack02/in_put/survey not found.
Unable to open library "/data/jack02/in_put/survey"
Loading feature class/subclass "poly"
from Coverage "/data/jack02/in_put/survey.ws/plstr_fill"
sde_layer_plstrfill_sdo: plstrfill_sdo is in LOADONLY mode
Imported 158399 features into SDE plstrfill_sdo,shape from coverage /data/jack02/in_put/survey.ws/plstr_fill,poly
SDE Error(-51) Underlying DBMS error
Extended error code(29855): 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-13230: failed to create temporary table [M2_8496$$] during R-tree creation
ORA-13249: Error in stmt: CREATE TABLE M2_8496$$ NOLOGGING tablespace SDE_IDX STORAGE (initial 4096K next 4096K pctincrease 0 maxextents unlimited) as (select rid , min_d1, max_d1 , min_d2, max_d2 from M0_8496$$ a, (select (min_d2+max_d2) value fro(MDSYS.SPATIAL_INDEX)
Not able to set layer into Normal-IO mode.
Cov2SDE completed.
No libraries currently set.
SQL> create index plstrfill_idx on plstrfill_sdo(shape)
2 indextype is mdsys.spatial_index
3 parameters ('SDO_INDX_DIMS=2 tablespace=sde4_idx');
create index plstrfill_idx on plstrfill_sdo(shape)
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-13230: failed to create temporary table [M2_84A5$$] during R-tree creation
ORA-13249: Error in stmt: CREATE TABLE M2_84A5$$ NOLOGGING tablespace SDE4_IDX
STORAGE (initial 4096K next 4096K pctincrease 0 maxextents unlimited) as
(select rid , min_d1, max_d1 , min_d2, max_d2 from M0_84A5$$ a, (select
(min_d2+max_d2) value from M0_84A5$$ where rowid='AAAISqAAPAAACCYABK') b where
(((a.min_d2+a.max_d2) < b.value) or (((a.min_d2+a.max_d2) = b.value) and (a.rid
<= 'AAAISeAAJAAAnvnAASZ'))))
ORA-13230: failed to create temporary table [M2_84A5$$] during R-tree creation
ORA-29400: data cartridge error
ORA-00210: cannot open the specified controlfile
ORA-00202: controlfile: '/u01/oradata/GIS2/control01.ctl'
ORA-27041: unable to open file
SVR4 Error: 24: Too many open files
Additional information: 3
ORA-06512: at "MDSYS.SDO_INDEX_METH
this is really killing me
my oracle is setup following the esri and oracle guidelines:
all our tablespaces are with UNLIMITED extent and maxsize on
any files. All the tablespaces follow Oracle9i best practices
such as OFA, SAFE, and SAME including Temporary Tablespace.
any suggestions would be realy helpful
--kassim -
ORA-29855 - Error creating Spatial Index using a Stored Procedure
Hi
I am using Oracle 10gR2 database and I have written a stored procedure to create spatial index. But when i execute this function i get the following error message.
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 R-tree: [mdrcrtscrt]
ORA-13231: failed to create index table [MDRT_217C1$] during R-tree creation
ORA-13249: Stmt-Execute Failure: CREATE TABLE FGDABZ40.MDRT_217C1$ (NODE_ID NUMBER, NODE_LEVEL NUMBER, INFO BLOB) LOB (INFO) STORE AS (CACHE) NOLOGGING PCTFREE 2
ORA-29400: data cartridge error
ORA-01031: insufficient privileges
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
ORA-06512: at line 1
ORA-06512: at "FGDABZ40.PKG_PSSDBE_APPLICATION", line 298
ORA-06512: at line 17
The tables that i am passing are registered in metadata and I am able to create indexes directly in sql plus. But when i try to create using this stored procedure, it fails.
it should be possible to create indexes using a generic function. Has any faced a similar problem?
regards
samHi,
I am having a same error on Oracle 10gR2 database. When I execute the same statement in sqlplus, it works. But it gives this error when I call the procedure which has this create spatial index statement.
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 R-tree: [mdrcrtscrt]
ORA-13231: failed to create index table [MDRT_20CDA$] during R-tree creation
ORA-13249: Stmt-Execute Failure: CREATE TABLE "SDOMGR".MDRT_20CDA$ (NODE_ID NUMBER, NODE_LEVEL NUMBER, INFO BLOB) LOB (INFO) STORE AS (CACHE) NOLOGGING PCTFREE 2
ORA-29400: data cartridge error
ORA-01031: i
Any help will be appreciated.
Thanks,
Sri -
ORA-13249 creating RTREE on 9.0.1.1.1 on NT
Attempting to create RTREE Spatial index as follows:
create index usiwc1_sdx
on usiwc (geom)
indextype is mdsys.spatial_index;
Receive following errors:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE
routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error initializing transformation for geodetic srid
8192
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 7
ORA-06512: at line 1
I initially upgraded this database from 8.1.7.2.1 to 9.0.1.1.1.
After running into this error I did a complete rebuild on
spatial, but the error is still here.
Any ideas?
Thanks.
Matt.Matt,
The SRID 8192 is not a valid srid as it is does not
have a valid WKT to represent it.
In the previous releases, this was allowed but
this is now being phased out as it can lead to
other problems.
The easiest way to fix the problems is change
the srid to 8307 (from 8192) which is the common SRID
for geodetic data for the whole earth model.
Or do the following to replace the existing wkt
for 8192 with the wkt for 8307:
Connect as MDSYS user and,
update cs_srs set wktext =
(select wktext from cs_srs where srid=8307)
where srid = 8192; -
Error creating spatial indexes
I'm using oracle 10g2.
I retrieve the following error message during spatial index creation:
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-13236: internal error in R-tree processing: [failed to cluster in memory]
ORA-13232: failed to allocate memory during R-tree creation
ORA-13236: internal error in R-tree processing: [failed to allocate memory
4387752 (mdrtsalloc)]
ORA-04031: unable to allocate ORA-04031: unable to allocate 4387800 bytes of
shared memory ("large pool","unknown object","koh-kghu sessi","kpmalloc")
bytes of shared memory ("","","","")
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
I've already tried to increase memory, shared and large pool, actually I have the following settings:
Shared pool 500
Buffer cache 200
Large pool 200
Pool Java 20
I've already installed data and created spatial indexes on other machine correctly with the same data with less memory use, and I can't find any difference.
Could anybody help me?Andre,
I didn't think the , and ; in the sdo_geom_metadata would be causing the problem because he indicated that he could build indexes on other data - I assume he uses the same diminfo values for these as well. But, one can never be too sure!
But certainly, follow what the error messages indicate.
The Oracle Error message manual says:
"ORA-13232: failed to allocate memory during R-tree creation
Cause: This feature assumes a minimum of 64K memory for bulk creation.
Action: Create the index for a small subset of the data. Then, use transactional insert operations for the rest of the data."
The spatial manual says:
"Before you create a spatial index, be sure that the rollback segment size and the SORT_AREA_SIZE parameter value are adequate, as described in Section 4.1.1."
One way to change the sort area size is to alter your existing session before
executing the create index statement. So, from 4.1.1. this can be done via:
ALTER SESSION SET SORT_AREA_SIZE = 20000000;
Also, do what Andre suggests. On my laptop with 1G of memory as a matter of course I change the SGA from the default to being much larger.
regards
S -
Spatial Index Creation Error on 9.2.0.1
Hi,
I can´t create a spatial index on an Oracle 9.2.0.1, Windows 2000 Server. I create the table, register metadata and when I try to create the index the folowing error is returned (some messages in Portuguese):
ORA-29855: ocorreu um erro na execução da rotina ODCIINDEXCREATE
ORA-13249: Error executing stmt: begin mdsys.prvt_idx.execute_insert(NULL, NULL, ' VALUES (''TESTUSER'',''MDIDX_INIT'', 0, 0, 64, -1, NLS_UPPER(''MDRT_7844$''), ''I_SDOTEST'', 1, ''TESTUSER'', ''"GEOM"'', 0, 0, 2, 0, ''DEFAULT'', ''DEFAULT'', NULL,NULL, NULL, NULL, NULL, NULL, NULL, 2, ''DEFAULT'', 10, NULL, NULL, NULL, NULL, ''FALSE'', ''VALID'', NULL)', NULL); end;
ORA-13249: Error in Spatial index: insert to metadata failed
ORA-29400: erro no cartucho de dados
ORA-00913: valores demais
ORA-06512: em "MDSYS.PRVT_IDX", line 5
ORA-06512: em line 1
ORA-06512: em "MDSYS.SDO_INDEX_METHOD_9I", line 7
ORA-06512: em line 1
The same error occurs with other database users.
On my notebook (Windows XP) with the same Oracle version installed the index is created succesfully.
What can be wrong on the server ?
Thanks.When I connect through sqlplus it shows:
SQL*Plus: Release 9.2.0.1.0 - Production on Mon Jun 14 17:14:33 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL>
The select on dba_registry returns:
COMP_ID COMP_NAME VERSION STATUS MODIFIED CONTROL SCHEMA PROCEDURE STARTUP PARENT_ID
CATALOG Oracle9i Catalog Views 9.2.0.1.0 VALID 14-JUN-2004 15:59:45 SYS SYS DBMS_REGISTRY_SYS.VALIDATE_CATALOG
CATPROC Oracle9i Packages and Types 9.2.0.1.0 VALID 14-JUN-2004 15:59:45 SYS SYS DBMS_REGISTRY_SYS.VALIDATE_CATPROC
OWM Oracle Workspace Manager 9.2.0.1.0 VALID 14-JUN-2004 15:59:45 SYS WMSYS OWM_VALIDATE
JAVAVM JServer JAVA Virtual Machine 9.2.0.1.0 VALID 12-MAI-2002 16:55:28 SYS SYS
XML Oracle XDK for Java 9.2.0.2.0 VALID 14-JUN-2004 15:59:45 SYS SYS XMLVALIDATE
CATJAVA Oracle9i Java Packages 9.2.0.1.0 VALID 14-JUN-2004 15:59:45 SYS SYS DBMS_REGISTRY_SYS.VALIDATE_CATJAVA
ORDIM Oracle interMedia 9.2.0.1.0 LOADED 12-MAI-2002 17:27:10 SYS ORDSYS
SDO Spatial 9.2.0.1.0 LOADED 12-MAI-2002 17:40:16 SYS MDSYS
CONTEXT Oracle Text 9.2.0.1.0 VALID 12-MAI-2002 17:32:11 CTXSYS CTXSYS
XDB Oracle XML Database 9.2.0.1.0 VALID 14-JUN-2004 15:59:55 SYS XDB DBMS_REGXDB.VALIDATEXDB
WK Oracle Ultra Search 9.2.0.1.0 VALID 12-MAI-2002 17:44:01 WKSYS WKSYS WK_UTIL.VALID
ODM Oracle Data Mining 9.2.0.1.0 LOADED 12-MAI-2002 17:49:36 SYS ODM
APS OLAP Analytic Workspace 9.2.0.1.0 LOADED 12-MAI-2002 17:58:32 SYS SYS
XOQ Oracle OLAP API 9.2.0.1.0 LOADED 12-MAI-2002 17:59:07 SYS SYS
AMD OLAP Catalog 9.2.0.1.0 INVALID 14-JUN-2004 15:59:57 SYS OLAPSYS CWM2_OLAP_INSTALLER.VALIDATE_CWM2_INSTALL
Any ideas ? -
I get a couple of error messages in Spatial Index Advisor when trying to draw indexed geometries. The errors are:
"Server object could not be created: server object could not be initialized: ORA-29902: error in executing ODCIIndexStart() routine", and then;
"Initialization error: server object could not be initialized: ORA-29902: error in executing ODCIIndexStart() routine"
Previously I uploaded a MapInfo table containing polygons using Easyloader, but without generating any indexes. Using DBA Studio, I created a spatial index with the assistance of the Tiling Wizard. I can only assume that the index itself was created OK, as I received no error messages from that process.
Am I missing somthing in my installation of Oracle? What is ODCI? I am using the 8.1.6 version downloaded from technet.
Thanks in advance,
Jon
nullThanks Dan,
I'll try your suggestion as soon as I can. First I just need to clarify a few other issues as well.
1. Does this mean that ODCI Indexing for Spatial is not necessarily incorrectly installed in my case? Put another way, is this just a problem with the Spatial Advisor, or does it go beyond that to the actual implementation of ODCI indexing in Spatial?
2. In one of my messages I alluded to the fact that I'd confirmed the problem using the Java API (meaning the 'SDOAPI'). In short, I formed an SQL statement requesting geometries for a specified window (SDO_FILTER), but got pretty much the same error relating to the 'ODCIIndexStart()' function. I'm not at home at the moment, so can't give you the details at this time. I think SQLPLus also reported the same error, leading me to conclude that it's a problem with the cartridge installation itself. Does the workaround that you suggested fix the problem for just the Spatial Advisor, or the SDO_FILTER operator in general? In essence, are you saying that ODCIIndexStart() (in Spatial) does not understand coordinate systems, or just the Spatial Advisor?
3. Is there a patch to fix this in the interim?
Sorry to be such a pain. It's just that I've been banging my head against the proverbial brick wall with this for a while. I was starting to think it was me not understanding something basic.
Regards,
Jon
null
Maybe you are looking for
-
Cannot send email notification to more than one people
Hi everyone, Hope anyone could help me to solve this. I want to send email notification to two people. First to the staff to alert him that his claim is ready. And also to his supervisor that the claim has been disbursed. Below is the PL/SQL procedur
-
Exit Code 7 during early installation process of Creative Suite 5.5 Design Premium
I'm unable to install this software. I'm getting the errors below. I'm running Win 7 Home Premium 64. Does anyone have an idea what I could do next. I tried Safe Mode installation with the same negative results Thanks. Exit Code: 7 -------
-
My Mastercard was working effectively
My Mastercard was working effectively, suddenly it stopped ! it says my payment method is not accepted ! why I have money in my card but still cann't use it
-
Why doesn't full screen video option work in Captivate 8?
Hi, I have added videos to my Captivate project and have placed the Corona 2 skin on top. When previewing or publishing there is a full screen icon button which can be clicked to make the video full screen. This is not working. When I clink on it, no
-
I was updating my ipad software and it appears to be frozen?
I was updating my ipad software and it appears to be frozen?