Melody oracle spatial index

Similar Questions

• Oracle Spatial Index on a column NOT NULL

  I'm using the Oracle 11 g with data space init.
  
  I have a SDO_GEOM column in a table that has NULL values for some records. I have to run spatial query based on this column so the need of a spatial index on it. Is it possible to create a Spatial Index on a column SDO_GEOM even if some of them have the NULL value and results of spatial query?
  
  
  Thank you
  Alan
  
  Published by: user3883362 on 29 April 2013 05:59

  Alan,

  Is it possible to create a Spatial Index on a column SDO_GEOM even if some of them are NULL

  Yes.

  SQL> CREATE TABLE test (ID NUMBER PRIMARY KEY, geom MDSYS.SDO_GEOMETRY);
  
  Table created.
  
  -- "insert a row with non-NULL geometry"
  SQL> INSERT INTO test VALUES (1, SDO_GEOMETRY('POINT (6000000 2100000)', 40986));
  
  1 row created.
  
  -- "insert a row with NULL geometry"
  SQL> INSERT INTO test VALUES (2, NULL);
  
  1 row created.
  
  SQL> CREATE INDEX test_spx ON test (geom) INDEXTYPE IS MDSYS.SPATIAL_INDEX;
  
  Index created.
  

  .. .and getting results of spatial query

  Yes, assuming that your data is valid.

  -- "Creates a 10' buffer around the point we previsouly inserted then applies SDO_INSIDE"
  SQL> SELECT ID, SDO_INSIDE(geom, SDO_GEOM.SDO_BUFFER(geom, 10, 1)) FROM test;
  1 TRUE --"our point geometry"
  2 FALSE --"our NULL"
  
  2 rows selected.
  

  If you encounter problems here, I think you can use the functions that are choking in NULL values, for example, the conversion of NULL in WKT geometry.

  How do you access data (sqlplus, application, custom, etc.)? What is the query, and we see a few examples of data?

  Kind regards
  Noel

• Cannot create spatial indexes in Oracle 11 g

  Hi all!
  I'm using Oracle 11 g 2 on Windows 2008 (64bitxR2). When I get errors when I create Spatial Index oracle11g2, but it works well with Oracle 10 g. I don't know what I did wrong, or do I need a fix for Oracle Spatial 11 g 2?
  Can you help me? Thanks for any help!
  
  
  ORA-29858: an error has occurred in the execution of the routine ODCIINDEXALTER
  ORA-29400: data cartridge error
  ORA-01403: no data found
  ORA-13249: internal error in the Spatial index: [mdidxrbd]
  ORA-13249: error in the Spatial index: index build failed
  ORA-13249: error in the spatial index: [mdrcrtxfergm]
  ORA-13249: error in the spatial index: [mdpridxtxfergm]
  ORA-13200: internal error [ROWID:AAAUmYAAIAAAJuFAAB] in space indexering.
  ORA-13206: [] internal error creating the spatial index
  ORA-13033: invalid data in the SDO_ELEM_INFO_ARRAY in the SDO_GEOMETRY object
  ORA-06512: vid 'MDSYS. SDO_INDEX_METHOD_10I', line 313
  
  DELETE FROM mdsys.sdo_coord_ref_system WHERE srid = 50632625;
  DELETE FROM mdsys.sdo_coord_op_param_vals WHERE coord_op_id = 50632625;
  DELETE FROM mdsys.sdo_coord_ops WHERE coord_op_id = 50632625;
  
  -COORD_OP_METHOD_ID = 9807: Transverse Mercator
  INSERT MDSYS. () SDO_COORD_OPS
  COORD_OP_ID, COORD_OP_NAME, COORD_OP_TYPE, COORD_OP_METHOD_ID.
  INFORMATION_SOURCE, DATA_SOURCE,
  SHOW_OPERATION, IS_LEGACY, IS_IMPLEMENTED_REVERSE, IS_IMPLEMENTED_FORWARD, REVERSE_OP)
  values)
  50632625, ' ST_74_0_GON_65: op-1 ', 'CONVERSION', 9807,.
  "Digpro AB, [email protected],"Digpro AB. "
  1, 'FALSE', 1, 1, 1);
  
  -Setting for the latitude of origin (0)
  INSERT MDSYS. () SDO_COORD_OP_PARAM_VALS
  COORD_OP_ID, COORD_OP_METHOD_ID, PARAMETER_ID, PARAMETER_VALUE, PARAM_VALUE_FILE_REF, UOM_ID)
  VALUES (50632625, 9807, 8801 0.000000, 9102, NULL);
  
  -Setting for east central meridian 18 ° 03' 28,044 "
  INSERT MDSYS. () SDO_COORD_OP_PARAM_VALS
  COORD_OP_ID, COORD_OP_METHOD_ID, PARAMETER_ID, PARAMETER_VALUE, PARAM_VALUE_FILE_REF, UOM_ID)
  VALUES (50632625, 9807, 8802, 18.05779, NULL, 9102);
  
  -Setting for the scale factor
  INSERT MDSYS. () SDO_COORD_OP_PARAM_VALS
  COORD_OP_ID, COORD_OP_METHOD_ID, PARAMETER_ID, PARAMETER_VALUE, PARAM_VALUE_FILE_REF, UOM_ID)
  VALUES (50632625, 9807, 8805, 0.99999425, NULL, 9201);
  
  -Setting for abscissa
  INSERT MDSYS. () SDO_COORD_OP_PARAM_VALS
  COORD_OP_ID, COORD_OP_METHOD_ID, PARAMETER_ID, PARAMETER_VALUE, PARAM_VALUE_FILE_REF, UOM_ID)
  VALUES (50632625, 9807, 8806, 100178.1808, NULL, 9001);
  
  -Setting for fictitious ordinate
  INSERT MDSYS. () SDO_COORD_OP_PARAM_VALS
  COORD_OP_ID, COORD_OP_METHOD_ID, PARAMETER_ID, PARAMETER_VALUE, PARAM_VALUE_FILE_REF, UOM_ID)
  VALUES (50632625, 9807, 8807,-6500614.7836, NULL, 9001);
  
  -Adds the system projected on top the geodetic system in rt90_dp_geosystem_102.sql
  -COORD_SYS_ID = 4400: CS Cartesian Axes. 2D: abscissa, ordinate (E, N). Directions: East, North. Unit of measure: m.
  -GEOG_CRS_DATUM_ID = 4619: SWEREF99
  INSERT MDSYS. () SDO_COORD_REF_SYSTEM
  SRID, COORD_REF_SYS_NAME, COORD_REF_SYS_KIND, COORD_SYS_ID.
  DATUM_ID, GEOG_CRS_DATUM_ID, SOURCE_GEOG_SRID, PROJECTION_CONV_ID.
  CMPD_HORIZ_SRID, CMPD_VERT_SRID, INFORMATION_SOURCE,
  DATA_SOURCE, IS_LEGACY, LEGACY_CODE, LEGACY_WKTEXT, LEGACY_CS_BOUNDS,
  IS_VALID, SUPPORTS_SDO_GEOMETRY)
  VALUES)
  50632625,'ST_74_0_GON_65:-1 ', 'PROJECTION', 4400,.
  NULL, 6619, 4619, 50632625,.
  NULL, NULL, 'Digpro AB, [email protected],
  'Digpro AB', 'FALSE', NULL, NULL, NULL,
  "TRUE", "TRUE");
  
  sqlplus kranskom/password
  -Update the metadata for the KRANSKOM schema
  Insert values (user_sdo_geom_metadata)
  "BOUCHIHAB", "SHAPE", HE SAID.
  () mdsys.sdo_dim_array
  MDSYS.sdo_dim_element ('Y',-100000, 200000, 0.0005).
  MDSYS.sdo_dim_element ('X',-100000, 200000, 0.0005),
  MDSYS.sdo_dim_element ('Z', -1000, 1000, 0.0005)
  ), 50632625
  );
  
  -Display content in column form (in the table GRAG)
  Insert into GRAG (SHAPE) values (MDSYS. SDO_GEOMETRY (3003,50632625, 'null', MDSYS. SDO_ELEM_INFO_ARRAY (1,5,1,1,2,1), MDSYS. SDO_ORDINATE_ARRAY(276.2339,-179.7433,0,276.2498,-179.7361,0,276.2668,-179.7324,0,276.2842,-179.7325,0,276.6235,-179.7691,0,276.793,-179.7731,0,276.8055,-179.772,0,276.8174,-179.7682,0,276.8281,-179.7619,0,277.073,-179.5793,0,277.2068,-179.4543,0,277.2122,-179.4481,0,277.2162,-179.4408,0,277.2186,-179.4329,0,277.2192,-179.4247,0,277.2159,-179.3107,0,277.3184,-178.9335,0,277.3252,-178.6913,0,277.3265,-178.5765,0,277.3258,-178.5683,0,277.3237,-178.5604,0,277.3201,-178.5531,0,277.3152,-178.5465,0,277.3092,-178.541,0,277.3023,-178.5366,0,277.2947,-178.5337,0,277.2867,-178.5321,0,277.1778,-178.5219,0,277.1731,-178.5219,0,277.1683,-178.5227,0,277.1637,-178.5244,0,277.1595,-178.5268,0,277.1558,-178.5299,0,277.1527,-178.5336,0,277.1503,-178.5378,0,277.1486,-178.5424,0,277.1478,-178.5471,0,277.1478 ,-178.5519,0,277.1536,-178.6151,0,277.1537,-178.6198,0,277.1529,-178.6244,0,277.1515,-178.6289,0,277.0012,-178.9885,0,276.9919,-179.0066,0,276.9797,-179.023,0,276.9651,-179.0373,0,276.2832,-179.6059,0,276.2804,-179.6079,0,276.2773,-179.6093,0,276.274,-179.6101,0,276.2706,-179.6103,0,276.2673,-179.61,0,276.264,-179.609,0,276.2609,-179.6075,0,276.2582,-179.6054,0,276.2559,-179.6029,0,276.2541,-179.6001,0,276.2528,-179.5969,0,276.252,-179.5935,0,276.2476,-179.5581,0,276.247,-179.5555,0,276.2459,-179.5529,0,276.2444,-179.5506,0,276.2425,-179.5485,0,276.2402,-179.5469,0,276.2377,-179.5456,0,276.235,-179.5449,0,276.2322,-179.5446,0,276.2294,-179.5449,0,276.2267,-179.5456,0,276.2242,-179.5468,0,276.2219,-179.5485,0,276.22,-179.5505,0,276.0132,-179.8127,0,276.0105,-179.8169,0,276.0086,- 179.8215,0,276.0076,-179.8263,0,276.0074,-179.8312,0,276.0082,-179.8361,0,276.0099,-179.8408,0,276.0124,-179.845,0,276.0157,-179.8488,0,276.0196,-179.8518,0,276.0239,-179.8541,0,276.0287,-179.8556,0,276.0336,-179.8562,0,276.0385,-179.8558,0,276.0433,-179.8546,0,276.0478,-179.8525,0,276.2339,-179.7433,0)));

  If the 2D, the value of 2002 data. otherwise assign 3002.

  Siva

• The details of the max/min for the spatial index

  Hello

  I am new to Oracle Spatial and perhaps this is a stupid question, but when I create an index for a table of geo, I always manually insert a line into the USER_SDO_GEOM_METADATA table. The DIMINFO table contains the bounding box, which are in my case X min/max / coordinated full geo (Lat/Long) of the table.

  The SDO_GEOMETRY column in my table of geo contains some polygons. How can I automatically query the table of geo to return the desired max/min X / Y coordinates? I'm looking for something like maxX (geo_data) SELECT... OF geo_table. Is this possible?

  Thank you!

  Hello Hans,.

  Well, I think that the old gods of Oracle Spatial of ages had intended a workflow by which metadata records were filled with knowledge not stored in the database or the spatial column.  Thus, for example the tolerance whence?  He comes to your head or your documentation that you hold outside the database, etc..  I mean that you put in this recording in order to enter the database.  So I would say that generally metadata was never intended to be created from the data.

  Now, we must know that the values stored in USER_SDO_GEOM_METADATA min/max are largely informative to my knowledge.  You can insert values garbage if you love without worrying much Oracle Spatial.  The only function I can think of who actually reads these values is the MD without papers. HHENCODE (everyone knows others?).  But that being said its always a good idea to avoid the garbage and properly document your spatial layers.

  So, in terms of generation of these values. I would say that your DIMINFO values should ideally include the size of your current data more any new data you could insert as part of your workflow.  So I would not shake this until your min/max values accurate unless your data is very, very static.  It could well be.  Still, usually I if I had a layer of data to the United States mainland that the values that run in the South enough to cover all the Florida keys, etc. (with some tampons too).  Even if I have no data for Florida keys in that exact moment.  It's rather subjective, to deduce the data, it must come from your documentation and your needs.

  But you probably still want something.  Good then, voila.

  SELECT
  a.bef || a.dim_xy || a.dim_3 || a.aft AS dim_info
  FROM (
    SELECT
     'MDSYS.SDO_DIM_ARRAY(' AS bef
    ,'MDSYS.SDO_DIM_ELEMENT(''X'',' || MDSYS.SDO_GEOM.SDO_MIN_MBR_ORDINATE(aa.shape,1) || ',' || MDSYS.SDO_GEOM.SDO_MAX_MBR_ORDINATE(aa.shape,1) || ',0.05)'
     ||
     ',MDSYS.SDO_DIM_ELEMENT(''Y'',' || MDSYS.SDO_GEOM.SDO_MIN_MBR_ORDINATE(aa.shape,2) || ',' || MDSYS.SDO_GEOM.SDO_MAX_MBR_ORDINATE(aa.shape,2) || ',0.05)'
     AS dim_xy
    ,CASE
     WHEN aa.shape.get_dims() > 2
     AND  aa.shape.get_lrs_dim() = 0
     THEN
        ',MDSYS.SDO_DIM_ELEMENT(''Z'',' || MDSYS.SDO_GEOM.SDO_MIN_MBR_ORDINATE(aa.shape,3) || ',' || MDSYS.SDO_GEOM.SDO_MAX_MBR_ORDINATE(aa.shape,3) || ',0.001)'
     ELSE
        NULL
     END AS dim_3
    ,')' AS aft
    FROM (
       SELECT
       MDSYS.SDO_AGGR_MBR(a.shape) AS shape
       FROM
       my_table a
    ) aa
  ) a;
  

  Note again once the tolerances must be hard-coded.

  And also it will not work for the LRS geometries.

  I respect the old gods and not go this route.

  See you soon,.

  Paul

• How to rebuild a spatial index partition that is marked 'INPROGRS '.

  I'm on 12.1.0.1 Enterprise Edition.

  I have a very large table of sdo_geometry objects that I divided it into several partitions.  I have create a spatial index on this table as UNUSABLE and then rebuild the partitions across a few different sessions.

  In total, the construction of index takes a few days.  Last week during the construction of the index, the database crashed completely.  This left me with most of the scores with a USER_IND_PARTITIONS. USABLE STATUS, some with UNUSABLE and a couple with INPROGRS.

  I can rebuild the UNUSABLE partitions as usual, but when I try to build a INPROGRS partition I get:

  ERROR at line 1:
  ORA-29952: cannot issue DDL on a domain index partition marked as LOADING
  

  The mistake is understandable, given that the index partition was INPROGRS when the database crashed.  The question is how to recover from it.  The doco says:

  Expect that the index partition operation complete question GOLD FORCE INDEX DROP to remove question OR index an ALTER TABLE DROP PARTITION to delete the partition.

  None of these options are good for me.  I don't want to let down the entire index as most of it is built.  It doesn't seem to be an option to recover a partition of index construction which is blocked at INPROGRS.

  
  

  Support Doc ID 557600.1 addresses this issue says in the context of the Oracle text index.  Sa dit :

  Sometimes, if CREATE INDEX or ALTER INDEX fails, an index can be left with the status of LOADING or INPROGRS and let the context index in an unusable state.

  Any attempt to retrieve using SUMMARY INDEX is blocked. The only recourse is to drop and re-create the index.

  In this case, use CTX_ADM. MARK_FAILED to force LOADING failure index status so that you can retrieve the index with the INDEX of CURRICULUM VITAE.

  If the suggestion is to use CTX_ADM. MARK_FAILED ( http://docs.oracle.com/database/121/CCREF/cadmpkg.htm#CCREF0500 ). 

  There is a similar option for spatial indexes?

  Thank you

  John

  Hi John,.

  Have you tried mdsys.reset_inprog_index (owner IN varchar2, varchar2 IN index_name)?

  This procedure will erase INPROGRS and to FAIL if index or index partition is INPROGRS.

  Thank you

  Ying

• bypassing the spatial index

  Hello

  Could someone please answer questions? :

  I was reading the book 'Pro Oracle Spatial' and it has the following about phase two of filtering when using space operators:

  «In some cases, however, the optimizer to decide to bypass the spatial index.» She then calls the secondary filter (i.e., the function of geometry engine) directly on the rows in the table. (This can happen for various reasons... »

  My questions:

  (1) where can I find more information on the "variety of patterns" when this happens?

  (2) is it possible to force Oracle Spatial not use filter primary and go directly to the secondary filter? The reason why I want to do this is that I'm doing my own prior filtering that corresponds to the primary filter and I have a condition of additional query (with spatial condition), which allows to select only those that are previously filtered.

  (3) or is there another Oracle Spatial function exactly like SDO_ANYINTERACT, but applies only the secondary filter (and therefore does not require an spatial index)?

  Any help is greatly appreciated.

  Upendra

  (1) for example, select * tab where c1 = 1 and sdo_anyinteract (...) = "TRUE";

  If "c1 = 1" is very selective, say only a single line or for very little is returned.

  sdo_anyinteract (...) cannot pass through the spatial index.

  (2) you can always use the / * + full * / reference as:

  Select / * + full (a) * / * from tab where sdo_anyinteract (...) = "TRUE";

  (3) SDO_GEOM. RELATE() seems to be what you are looking for.

• spatial index and normal index

  Hi space specialists,.

  I have a question for spatial index performance and how Oracle manages queries that have a space and regular condition combined. We are on the Oracle 10 g Enterprise Edition Release 10.2.0.4.0 database

  Take a query like this one (not a real query but based on the type of query that is generated by ArcGIS):

  Select objectid

  attribute

  geometry

  table

  where mdsys.sdo_filter (geometry, mdsys.sdo_geometry (: gtype1,: srid1, null,: elem_info1,: ordinates1), 'querytype = window') = 'TRUE '.

  and attribute = value

  In our scenario, we have a lot of rows in the table (2 million), but we have only a few lines (2000) where attribute = value.

  It seems that there is a scenario where the performance is really bad. It takes 5 seconds for the query to return the results and you're just too slow for our needs. There is a spatial index on a geometry and a normal index on the field for the attribute. The plan of the explain command shows that both the spatial index and the index of the attribute are used.

  Of course, we can break to the top of the table in separate tables by object type. This would make the index space datamodel much more efficient, but at the expense of our current simple, abstract.

  Do you have suggestions on how we can improve performance without too much impact on our datamodel? Oracle for example has an option where you can create a spatial index on a subset of the data in a table?

  Thank you!

  Rob

  Do not know whether or not the following works for your case:

  use the column range-key attribute to create a partitioned table Beach and then create a local spatial index.

• ORACLE spatial 11g and GRS 80

  Hello
  I'm working on a project that will require projected and geographical coordinates for different in product files. I have no problem, define, store, extract or corresponding point coordinates. My columns for these coordinates with the SRID 8307 are defined in user_sdo_geom_metadata table as follows:
  INSERT INTO
  USER_SDO_GEOM_METADATA (TABLE_NAME, COLUMN_NAME, DIMINFO, SRID)
  VALUES
  ('INVENTORYGEOMETRY', 'INVGEO', MDSYS. SDO_DIM_ARRAY (MDSYS. SDO_DIM_ELEMENT ('Longitude',-180, 180,.05), MDSYS. SDO_DIM_ELEMENT('Latitude',-90, 90,.05)), 8307);
  
  the index:
  creating index 'MYDB '. "' INVGEO_IDX ' on 'MYDB '. "INVENTORYGEOMETRY"("INVGEO") indextype is MDSYS. SPATIAL_INDEX;
  
  However, I'm confused as to how I'm going to have a column that has both geographic and coordinated projected. Am I allowed to set longer SDO_DIM_ELEMENT (s) FRO the SDO_DIM_ARRAY with min/max different values. For example, I'd be able to always use an SRID of 8307 times WGS 84 and data GRS80 (ellipsoid), something like the following:
  INSERT INTO
  USER_SDO_GEOM_METADATA (TABLE_NAME, COLUMN_NAME, DIMINFO, SRID)
  VALUES
  ('INVENTORYGEOMETRY', 'INVGEO', MDSYS. SDO_DIM_ARRAY (MDSYS. SDO_DIM_ELEMENT ('Longitude',-180, 180,.05), MDSYS. SDO_DIM_ELEMENT ("' North latitude-90, 90,.05").
  (MDSYS. SDO_DIM_ELEMENT('FIXEDGRID_.5Resolution', 0, 26916,.5)), 8307);
  
  Is that possible or do I have to create a new column in the database?
  
  In addition, I don't know the relationship between the SDO_ELLIPSOIDS and SDO_GEOMETRY tables. You you please explain it to me?
  
  Thank you for any help you can give. I'm confused as to how I'm going to make this work for both geographic and projected coordinates, or if I'll be able to make it work.
  
  Thank you
  Erica

  Erica,

  You have geodetic and projected data in a single column of a table BUT you cannot index in space because the index does not work on the two projections.

  You have, says Bryan, create two columns:

  create table INVENTORYGEOMETRY (
    fid integer,
    INVGEO sdo_geometry, /* For the geodetic data */
    INVPROJ sdo_geometry /* for the projected data */
  );
  

  If you do this, you must create two user_sdo_geom_metadata entries. As you have already done and one for projected data:

  INSERT INTO
   USER_SDO_GEOM_METADATA (TABLE_NAME, COLUMN_NAME, DIMINFO, SRID)
   VALUES ('INVENTORYGEOMETRY','INVPROJ',
   MDSYS.SDO_DIM_ARRAY(MDSYS.SDO_DIM_ELEMENT('X',0,1000, .05),MDSYS.SDO_DIM_ELEMENT('Y',0,1000, .05)),XXXXX);
  

  Where you replace 0,1000 ranges with your actual data range and XXXXX by your actual SRID projected (for example, 28355 as in the example below).

  Now, assuming that this table Gets the INVGEO column populated first (by some external dynamic flow) you could synchronize the column projected via a trigger as follows:

  create trigger inventorygeometry_proj_bi
  before insert
  on inventorygeometry
  FOR EACH ROW
  begin
     if (:new.invgeo is not null) then
       :new.invproj := mdsys.sdo_cs.transform(:new.invgeo,28355);
     end if;
  end;
  /
  

  Finally...

  In addition, I don't know the relationship between the SDO_ELLIPSOIDS and SDO_GEOMETRY tables. You you please explain it to me?

  The SDO_ELLIPSOIDS table is part of the implementation of the projections in the package Oracle Spatial. When you use a SRID in a SDO_GEOMETRY, Oracle uses the SRID to interrogate the underlying tables (which SDO_ELLIPSOIDS is only one member) to get the properties of the projection for example the definition of the ellipsoid being a.

  I hope this helps at all.

  Don't forget to assign the points you like if our responses are considered correct or useful.

  concerning
  Simon

• Index - Rtree spatial indexing

  Hello
  
  I have a spatial table. I created indexes. If I keep on inserting data in my table I rebuilt the index or data are automatically indexed?

  Hi 951616,

  Now this is interesting. Initially, I was going to say that you need the quality of your spatial index yourself, but when I lifted up the documentation for 11R2 I found a note that [url http://docs.oracle.com/cd/E11882_01/appdev.112/e11830/sdo_objtune.htm#CACHEDCG] SDO_TUNE. QUALITY_DEGRADATION has been deprecated because

  You should not use this function. It is not needed because Spatial indexes are self-tuning.
  

  Which are new in 11R2 I guess? I have used to set up a job to keep an eye on the index for frequently changing tables, but that seems not to be necessary. So your answer is: no, you do not have :-)

  You learn something new every day :-)

  See you soon,.
  Stefan

• Error creating the Spatial Index for SRID 8307 on newly hardened database

  Oracle 11g Rel2, Windows 2003 platform
  
  Help, please...
  
  Meeting with error message:
  ERROR on line 1:
  ORA-29855: an error has occurred in the execution of routine ODCIINDEXCREATE
  ORA-13249: internal error in the Spatial index: [mdidxrbd]
  ORA-13249: geodetic initialization error turn
  ORA-13249: SRID 8307 does not exist in the table MDSYS.CS_SRS
  ORA-29400: data cartridge error
  ORA-04063: package body 'MDSYS. SDO_CS"contains errors
  ORA-06512: at the 'MDSYS. SDO_INDEX_METHOD_10I', line 10
  
  After running the command
  
  INSERT INTO USER_SDO_GEOM_METADATA VALUES
  ("PointGeometry",
  "pointGeom,"
  MDSYS.sdo_dim_array (mdsys.sdo_dim_element ('Longitude',-180, 180, 1),
  mdsys.sdo_dim_element('Latitude',-90,90,1)),
  8307
  );
  
  CREATE the INDEX IDX_POINTGEOMETRY on PointGeometry (pointGeom) indextype is mdsys.spatial_index parameters('LAYER_GTYPE=POINT');
  
  When I ask mdsys.sdo_cs I see that there are actually SRID 8307. This index was created in this schema without problem. The problem only arises once the hardened customer database and we tried to recreate the schema (and index).
  
  Probably not coincidentally, I also get error:
  ORA-29855: an error has occurred in the execution of routine ODCIINDEXCREATE
  ORA-04063: package body "CTXSYS. DRIXMD' has errors
  ORA-06508: PL/SQL: called program unit is not found: 'CTXSYS. DRIXMD ".
  ORA-06512: at "CTXSYS. DRUE", line 145
  ORA-06512: at "CTXSYS. TEXTINDEXMETHODS', line 366
  ORA-04063: package body "CTXSYS. DRIXMD' has errors
  ORA-06508: PL/SQL: called program unit is not found: 'CTXSYS. DRIXMD ".
  
  When attempting to create and index Oracle Text context.
  
  Your help is greatly appreciated.

  Then, that's the problem.

  MDSYS user now has not run, and select privileges on the dbms_lob package.

  You must grant privileges on this package in MDSYS.

  Note that you can run into other issues of privilege package like this, so you must correct all by the granting of the
  required privileges for MDSYS.

  Siva

• Oracle Spatial

  I and new to Oracle Spatial.
  If I download Oracle database 11.2
  Does include Oracle Spatial? Can I install spatial data?

  Welcome to YOU

  Each version of the database allows the storage of spatial data with a minimum feature set space under license as the Oracle index

  http://download.Oracle.com/docs/CD/E11882_01/AppDev.112/e11830/sdo_locator.htm#i632018.

  The Oracle Spatial license covers the full use of the functionality.

  In order to start learning here are some good starting points:

  Pro space book of Oracle 11 g

  http://www.Amazon.com/Oracle-Spatial-database-experts-voice/DP/1590598997

  and documentation of the user:

  http://www.Oracle.com/pls/db112/portal.portal_db?selected=7&frame=#oracle_spatial_and_location_information

  specifically Spatial Developer's Guide:

  http://download.Oracle.com/docs/CD/E11882_01/AppDev.112/e11830/TOC.htm

  Concerning

  Luke

• Data Modeler - cannot create a spatial index

  Good day, colleagues!
  
  I have a version 584 of the Modeler of Dala.
  
  Here is her quote Guide of Modeler of Oracle SQL Developer data:
  
  "Properties of spatial definition 3.82.
  ...
  Benchmark ID: Value Oracle Spatial SRID. ...
  + Create Spatial Index: Determines if a spatial index is created. +
  Name of the spatial Index: name of the spatial index.
  ..."
  
  I have a SDO_GEOMETRY column in my table and want to create the spatial index.
  
  The problem is that there is no option "Create Spatial Index" in my space definition properties window. There is only 'The Spatial Index name' option. When I am creating the spatial index manually, I can't, because the option 'Space' for index creation is not active. I checked the table option 'Save as space Table', but it also did not help.
  
  So, I have no way to create a spatial index. How can I do?

  Hello usamytch,

  create spatial index is confusing. We will improve it in future releases. Here are the steps:
  (1) creation of index - no need to add columns
  (2) create the spatial column definition ('space properties' in the dialog table)
  (3) in the definition of the spatial column, you can select the size of the spatial column, coordinate ID system, and you can select one of the existing indexes to be used as a space.
  (4) after this index appear as space and you can define the spatial properties in the index dialog box
  (5) you must check 'Save as space Table' in order to get meta-space data generated by DDL

  There are additional space properties, that you can set in the physical model.

  Philippe

• Given Oracle Spatial are stored in the database tables?

  Given Oracle Spatial are stored in the database tables?

  Oracle spatial is DBMS oracle server functionality. It allows you in NATIVE mode, store and manage all standard types of spatial data and their attributes and metadata in the oracle database enterprise, in the way that you are quite familiar with. on top of standard oracle database features, adds types of geographic data, spatial index, geometric operators and queries, functions, spatial and analytical, to name a few.

  MapViewer is a feature of Oracle Fusion Middleware, which makes cards using spatial data managed by Oracle Spatial. That's what you called "generator of maps. but of course, it's not just a map generator, he has much more to offer, such as MapBuilder, WMS, Oracle cards.

  For more information, please see the technical details:

  http://www.Oracle.com/technology//products/spatial/index.html
  http://www.Oracle.com/technology/products/MapViewer/index.html

• Spatial index error while creating an index for a column GeoRaster

  Hi all
  
  Several months ago, I inserted 12 map PNG Raster files in Oracle as GeoRaster data. I then looked into MapBuilder to verify that they have been charged, and as they appear, it seems to suggest that they were.
  
  Today, however, I realized that I had not created an entry for USER_SDO_GEOM_METADATA or a spatial index. That's why I tried to do it by using the code below. When I made an entry in USER_SDO_GEOM_METADATA, I didn't add .spatialextent after the column name, web_raster_map. But while reading the manual MapViewer I decided that it was necessary to create a new entry. However, the error message displayed at the end, was the same in each case. If anyone has any ideas on what I can hurt, I would be grateful.
  
  Is the entries abscissa-x and the ordered is wrong? Should this be X and Y, and if that resolves the errors? I've been using a script I created previously to vector data and adapting.
  

  INSERT INTO USER_SDO_GEOM_METADATA
  (TABLE_NAME,
  COLUMN_NAME,
  DIMINFO,
  SRID)
  VALUES (
  'WEB_RASTER_MAP_FILE',
  'web_raster_map.spatialextent',
  SDO_DIM_ARRAY( -- full grid size goes here
  SDO_DIM_ELEMENT('eastings-x', -3273.58473839662, -8471.66, 0.005),
  SDO_DIM_ELEMENT('northings-y', -9694.76, -1632.88473839662, 0.005)),
  96163497); -- this is a user created srid
  commit;
  
  CREATE INDEX WEB_RASTER_MAP_FILE_IDX ON WEB_RASTER_MAP_FILE (web_raster_map)
     INDEXTYPE IS MDSYS.SPATIAL_INDEX;
  commit;

  Error message was:

  Error starting at line 14 in command:
  CREATE INDEX WEB_RASTER_MAP_FILE_IDX ON WEB_RASTER_MAP_FILE (web_raster_map)
     INDEXTYPE IS MDSYS.SPATIAL_INDEX
  Error at Command Line:14 Column:13
  Error report:
  SQL Error: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
  ORA-13200: internal error [Unsupported Type] in spatial indexing.
  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.
  commit succeeded.

  Kind regards
  
  Tim
  
  Published by: user467357 on March 23, 2009 17:45
  To add an additional comment.

  Tim,
  You must create the index on web_raster_map.spatialextent.
  The create index must therefore:

  CREATE the INDEX WEB_RASTER_MAP_FILE_IDX ON WEB_RASTER_MAP_FILE (web_raster_map.spatial_extent)
  INDEXTYPE IS MDSYS. SPATIAL_INDEX;

• Electrodes for Oracle spatial 11.2.0.4.0

  What patches are needed for Oracle spatial 11.2.0.4.0?

  I don't know what kind of response you expect an open question...

  Simply apply the last power supply and go from there.

  Bryan