User_sdo_geom_metadata view

I am running into a problem I have not seen before. I have a table with oracle spatial geometry that I am trying to index and do spatial queries on. The spatial column is of type MDSYS.SDO_GEOMETRY. The table is in the user1 schema.
As user1, I attempt to select/insert from user_sdo_geom_metadata table and i get a "ORA-01031: insufficient privileges error". Is there a grant that needs to be done for the schema owner to have access to this view?
Any thoughts would be helpful.

try to
grant select on table1 to schema2....
Once you have granted the access to teh schema...you should be able to access the MDSYS schema.
This should be OK.

Similar Messages

Spatial or locator / USER_SDO_GEOM_METADATA view missing on XE

Hi,
I would like to use locator on an Oracle XE instance. I can not seem to find USER_SDO_GEOM_METADATA view. Is this included in the Spatial option only? I suppose on XE i do not have to install Locator, it is installed automatically. Isn't it?
TIA.
Regards, Tamas

Hi Tamas.
You should find your awnser here.
http://www.spatialdbadvisor.com/oracle_spatial_tips_tricks/55/oracle-locator-vs-enterprise-licensing-the-sdogeom-package
Please let me know if it solved your problem.
Regards,

ORA-13203: failed to read USER_SDO_GEOM_METADATA view

when I create spatial index, it return an error：
create index harbin_images_index on harbin_images (image.spatialextent indextype is mdsys.spatial_index;
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13203: failed to read USER_SDO_GEOM_METADATA view
ORA-13203: failed to read USER_SDO_GEOM_METADATA view
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
ORA-06512: at line 1
Please help me , thanks !

Hi,
Before creating spatial index you need to insert metadata about your table into MDSYS.SDO_GEOM_METADATA table.
Regards,
Andrejus

Locator: failed to read USER_SDO_GEOM_METADATA view

Hi again,
i tried the step-by-step explanation about oracle locator, published on http://www.oracle.com/pls/xe102/to_toc?pathname=appdev.102%2Fb28004%2Ftoc.htm&remark=portal+%28Getting+Started%29 (thx to roberto)
i don't know how to explain this simple, but i will try:
1) creating the tables work fine (stores, customers)
2) creating the metadata didn't give an error
3) creating the spatial index gave me this error
|ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
|ORA-13203: failed to read USER_SDO_GEOM_METADATA view
|ORA-13203: failed to read USER_SDO_GEOM_METADATA view
solution found on the internet: "This error occurs if the table you are trying to index does not have any metadata in the USER_ SDO_GEOM_METADATA"
so i tried to do step 2 again (creating a metadata-row for my table). the error i get now:
|ORA-13223: duplicate entry for CUSTOMERS.CUST_GEO_LOCATION in SDO_GEOM_METADATA
|ORA-06512: at "MDSYS.MD", line 1723
|ORA-06512: at "MDSYS.MDERR", line 17
|ORA-06512: at "MDSYS.SDO_GEOM_TRIG_INS1", line 48
|ORA-04088: error during execution of trigger 'MDSYS.SDO_GEOM_TRIG_INS1'1. INSERT INTO USER_SDO_GEOM_METADATA (TABLE_NAME, COLUMN_NAME, |DIMINFO, SRID)
|2. VALUES ('CUSTOMERS', 'CUST_GEO_LOCATION',
|3. SDO_DIM_ARRAY
from this, i understand that there is already a record within the metadata view??
next, i tried to delete the specifiek record in user_sdo_geom_metadata. answer:
|0 records deleted
from here, i don't know if the record was created in the user_sdo_geom_metadata, and if it is still there!?
the weird part of all: i tried all these steps in the SQL-command-bar, which is on my database home page.(home >sql>sql commands) that's also where i get the errors.
when i try the same steps in SQL plus, the record is added to user_sdo_geom_metadata and i can create spatial indexes?!
can someone explain me what i do wrong, and why i can't create spatial indexes on my database home page?
I hope I explained my problem clear enough, if not, please ask me some questions.
thx,
Ine

Greetings - I found the excerpt below in the Locator documentation (the link was provided in your previous post), in the first chapter. It doesn't describe why you can't use the Express Edition SQL Commands, only that you must use SQL Plus. Anyway, I thought you might be interested in seeing it, as it appears to confirm your experience ...
"Note:
You cannot use the Express Edition SQL Commands or SQL Scripts features to run a SQL script or enter a SQL statement that creates or requires a spatial index. You must instead use SQL*Plus, such as by selecting Run SQL Command Line from the Express Edition menus, and connect as a database user that has the Create Table privilege."
Regards -
Gail

Failed to read USER_SDO_GEOM_METADATA view

Hello,
I'm trying to add a geometry column to an oracleXE table.
commands issued are:
1) alter table specimen add (geom mdsys.sdo_geometry);
2) update specimen set geom = mdsys.sdo_geometry(2001,8307,mdsys.sdo_point_type(dec_long,dec_lat,null),null,null);
3) insert into mdsys.user_sdo_geom_metadata (table_name,column_name,diminfo,srid) values ('specimen','geom',mdsys.sdo_dim_array(mdsys.sdo_dim_element('longitude',-180,180,1), mdsys.sdo_dim_element ('latitude',-90,90,1)),8307);
all above seem to work correctly and if I list user_sdo_geom_metadata I get:
TABLE_NAME
COLUMN_NAME
DIMINFO(SDO_DIMNAME, SDO_LB, SDO_UB, SDO_TOLERANCE)
SRID
SPECIMEN
GEOM
SDO_DIM_ARRAY(SDO_DIM_ELEMENT('longitude', -180, 180, 1), SDO_DIM_ELEMENT('latit
ude', -90, 90, 1))
8307
TABLE_NAME
COLUMN_NAME
DIMINFO(SDO_DIMNAME, SDO_LB, SDO_UB, SDO_TOLERANCE)
SRID
which also looks correct.
However, when I try to create a spatial index with:
create index specimen_sidx on specimen(geom) indextype is mdsys.spatial_index;
I get the error:
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13203: failed to read USER_SDO_GEOM_METADATA view
ORA-13203: failed to read USER_SDO_GEOM_METADATA view
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
Does anyone have a fix or any idea why it fails?
Any help appreciated,
Dave

Sorry, I forgot about the triggers on the user_sdo_geom_metadata:
Do these as well (again while connected as SYSDBA).
alter session set current_schema=MDSYS;
CREATE OR REPLACE TRIGGER SDO_GEOM_TRIG_INS1
INSTEAD OF INSERT ON user_sdo_geom_metadata
REFERENCING NEW AS n
FOR EACH ROW
declare
tname varchar2(32);
stmt varchar2(2048);
vcount INTEGER;
dimcount INTEGER;
tolerance NUMBER;
dimelement MDSYS.SDO_DIM_ELEMENT;
idx number;
BEGIN
EXECUTE IMMEDIATE
'SELECT user FROM dual' into tname;
if ( (instr(:n.table_name, ' ') > 0 ) OR
(instr(:n.table_name, '''') > 0 ) ) then
mderr.raise_md_error('MD', 'SDO', -13223,
:n.table_name||'.'||:n.column_name);
end if;
if ( (instr(:n.column_name, ' ') > 0 ) OR
(instr(:n.column_name, '''') > 0 ) ) then
mderr.raise_md_error('MD', 'SDO', -13223,
:n.table_name||'.'||:n.column_name);
end if;
stmt := 'SELECT count(*) FROM SDO_GEOM_METADATA_TABLE ' ||
'WHERE sdo_owner = :tname AND sdo_table_name = :table_name '||
' AND sdo_column_name = :column_name ';
EXECUTE IMMEDIATE stmt INTO vcount
USING upper(tname), upper(:n.table_name), upper(:n.column_name);
IF vcount = 0 THEN
dimcount := :n.diminfo.count;
FOR idx in 1 .. dimcount LOOP
dimelement := :n.diminfo(idx);
tolerance := dimelement.SDO_TOLERANCE;
if ( (tolerance is NULL) OR (tolerance <= 0) ) then
mderr.raise_md_error('MD', 'SDO', -13224,
:n.table_name||'.'||:n.column_name);
end if;
END LOOP;
INSERT INTO sdo_geom_metadata_table values
(tname,
upper(:n.table_name), upper(:n.column_name), :n.diminfo,
:n.srid);
ELSE
mderr.raise_md_error('MD', 'SDO', -13223,
:n.table_name||'.'||:n.column_name);
END IF;
END;
show errors;
CREATE OR REPLACE TRIGGER SDO_GEOM_TRIG_DEL1
INSTEAD OF DELETE ON user_sdo_geom_metadata
REFERENCING OLD AS n
FOR EACH ROW
declare
tname varchar2(32);
stmt varchar2(2048);
vcount INTEGER;
BEGIN
EXECUTE IMMEDIATE
'SELECT user FROM dual' into tname;
DELETE FROM sdo_geom_metadata_table
WHERE SDO_OWNER = tname
AND SDO_TABLE_NAME = upper(:n.table_name)
AND SDO_COLUMN_NAME = upper(:n.column_name);
END;
show errors;
CREATE OR REPLACE TRIGGER SDO_GEOM_TRIG_UPD1
INSTEAD OF UPDATE ON user_sdo_geom_metadata
REFERENCING OLD AS old NEW AS n
FOR EACH ROW
declare
tname varchar2(32);
stmt varchar2(2048);
vcount INTEGER;
BEGIN
EXECUTE IMMEDIATE
'SELECT user FROM dual' into tname;
UPDATE sdo_geom_metadata_table
SET (SDO_TABLE_NAME, SDO_COLUMN_NAME, SDO_DIMINFO, SDO_SRID) =
(SELECT upper(:n.table_name), upper(:n.column_name), :n.diminfo,
:n.srid FROM DUAL)
WHERE SDO_OWNER = tname
AND SDO_TABLE_NAME = upper(:old.table_name)
AND SDO_COLUMN_NAME = upper(:old.column_name);
END;
show errors;

Is it mandatory to populate USER_SDO_GEOM_METADATA for each spatial column ?

Hello,
I would like to know if we HAVE to populate the metadata table for a geometry column that will never be indexed.
(I know that in the documentation it is said "For each spatial column,
you must insert an appropriate row into the USER_SDO_GEOM_METADATA view.")
Thanks
Hugues

Hi Hugues,
There are many spatial operations that make use of the user_sdo_geom_metadata table, not all of them index related (operators).
If your data hasn't been migrated to 8.1.6 format then not much will work if user_sdo_geom_metadata is not populated.
If your data is migrated:
You won't be able to validate your data (we check the data to the bounds of the coordinate system).
You won't be able to use linear referencing (also known as dynamic segmentation).
You won't be able to use any spatial operators (which require a spatial index).
You won't be able to use coordinate systems (or least some parts of coordinate systems).
The above might only be a partial list.
hope this helps, and regards,
dan

Out of memory when reading USER_SDO_GEOM_METADATA

Hi,
I'm running a plsql procedure from sqldeveloper against a Oracle10g (Spatial) server.
The procedure mainly performs a SDO_NN search.
I was expecting the procedure processing time to be about 48h (due to the huge tables involved)
But I always get this same kind of errors, breaking the process when six hours elapsed :
ORA-29902: error in executing ODCIIndexStart() routine
ORA-13203: failed to read USER_SDO_GEOM_METADATA view
ORA-13203: failed to read USER_SDO_GEOM_METADATA view
ORA-29400: data cartridge error
ORA-04030: out of process memory when trying to allocate 16396 bytes. (QERHJ hash-joi,QERHJ Bit vector)
extending memory could be a workaround
but it wouldn't explain why the read of USER_SDO_GEOM_METADATA always causes the "out of memory".
Thanks for your advice or explanation
Clem

but it wouldn't explain why the read of USER_SDO_GEOM_METADATA always causes the "out of memory".Reading USER_SDO_GEOM_METADATA wouldn't be the cause of 'out of memory'. It is more likely that some rogue process caused you to run out of memory and the next thing that was supposed to happen was a read of USER_SDO_GEOM_METADATA. This read failed as there was no memory left for the query to perform.
So the failed read of USER_SDO_GEOM_METADATA is the symptom rather than the cause.
A few general points:
- What exact version of the 10g are you on? There were several memory related bugs fixed over the life of 10g. Ensure you are on the very latest patchset before spending any more time on this.
- Try to ensure your data is valid. i.e. it passes SDO_GEOM.VALIDATE_LAYER_WITH_CONTEXT(). If you've a very big table, then it could be tricky to get all the data valid, but be aware that invalid data can lead to all sorts of problems including memory leaks.
- Follow the general guidelines for ORA-04030 errors. In particular, ensure you have a sensible PGA_AGREGATE_TARGET value.
Following that, I'd recommend posting the key parts of your pl/sql procedure here in case you're doing something in the code that is causing this error.

Trouble with creating Spatial Indexes and "user_sdo_geom_metadata"

G'day All,
I've encountered a weird issue while playing around with SDO_GEOMETRY objects under Oracle Apex v3.0.1 on Oracle XE running on Windows Vista.
The issue started when I attempted to create the spatial index :
create index geotag_sdx on geotag(location)
indextype is mdsys.spatial_index;
and I got the following error:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13203: failed to read USER_SDO_GEOM_METADATA view
ORA-13203: failed to read USER_SDO_GEOM_METADATA view
I scratched my head for a sec and thought WTF ? my metadata insert worked... well I was sure it did. However when I ran a select from "user_sdo_geom_metadata" there was no rows, so I tried again and I got an error "name is already used by an existing object", again I thought WTF ?
After getting the source for the "updatable" view "MDSYS.user_sdo_geom_metadata" I could see that the view was filter by CURRENT_SCHEMA:
SELECT SDO_TABLE_NAME TABLE_NAME, SDO_COLUMN_NAME COLUMN_NAME, SDO_DIMINFO DIMINFO, SDO_SRID SRID
FROM SDO_GEOM_METADATA_TABLE
WHERE sdo_owner = sys_context('userenv', 'CURRENT_SCHEMA')
I ran SELECT sys_context('userenv', 'CURRENT_SCHEMA') FROM DUAL and it correctly returned the SCHMEA name.
So from sqlplus and logged in a sys/sysdba I ran a select statement from MDSYS.SDO_GEOM_METADATA_TABLE and i saw the problem, the record was inserted with a SDO_OWNER value of "ANONYMOUS".
When I logged as the SCHEMA via sqlplus and ran the metadata insert statement it worked fine an d the index could be created.
Has anyone ran into this issue and how did you fix it as I'm concerned or know what I might be doing wrong ?
Any help would be most appreciated ?
Regards
Mark

Hi Marks,
Had a quick look at the stored procedure I'm using and there it is. We don't insert into user_sdo_geom_metadatas but in mdsys.sdo_geom_metadata_table and specify the owner ourselves. Of course, you need a direct grant on mdsys.sdo_geom_metadata_table to be able to do this from a stored procedure.
Seems we had the problem you are facing even without Apex. Our application has a special admin user that has execute privs on certain packages. But when running the spatial index creation procedure we ran into this "owner" problem.
Here they use all_sdo_geom_metadata:
Re: Metadata Error
Message was edited by:
renewestenberg

Error reading User_SDO_Geom_Metadata when validating geometry

Hello,
I am having an error when running SDO_GEOM.VALIDATE_LAYER_WITH_CONTEXT on an Oracle 10.2.0.4 DB running on Windows. Below is a code snippet and response with errors. (I think during the investigation of this problem that I saw similar errors when attempting to build a spatial index but not with this example)
There is the correct entry into ALL_SDO_GEOM_METADATA also.
If anyone can offer any suggestions?
Thanks!
CODE
CREATE TABLE "TABLE1"
( "COL" VARCHAR2(20 BYTE),
"GEOM" "MDSYS"."SDO_GEOMETRY"
DELETE FROM USER_SDO_GEOM_METADATA
WHERE TABLE_NAME = 'TABLE1' AND COLUMN_NAME = 'GEOM' ;
INSERT INTO USER_SDO_GEOM_METADATA (TABLE_NAME, COLUMN_NAME, DIMINFO, SRID)
VALUES
('TABLE1', 'GEOM',
MDSYS.SDO_DIM_ARRAY
(MDSYS.SDO_DIM_ELEMENT('X', 100000, 200000, 0.005000000),
MDSYS.SDO_DIM_ELEMENT('Y', 100000, 200000, 0.005000000)
), null
COMMIT;
SELECT * FROM USER_SDO_GEOM_METADATA;
INSERT INTO TABLE1 VALUES('TEST',SDO_GEOMETRY
(2003,null,null,SDO_ELEM_INFO_ARRAY(1, 1003, 1),
SDO_ORDINATE_ARRAY
(180000.00,120000.00,
185000.00,120000.00,
185000.01,125000.00,
180000.00,125000.00,
180000.00,120000.00)));
COMMIT;
CREATE INDEX TABLE1_SX ON TABLE1 ( GEOM ) INDEXTYPE IS MDSYS.SPATIAL_INDEX;
CREATE TABLE VALIDATION_RESULTS (
SDO_ROWID ROWID,
STATUS VARCHAR2(2000)
PROMPT #############################
CALL SDO_GEOM.VALIDATE_LAYER_WITH_CONTEXT('TABLE1','GEOM','VALIDATION_RESULTS');
RESULTS
CREATE TABLE succeeded.
0 rows deleted
1 rows inserted
COMMIT succeeded.
TABLE_NAME COLUMN_NAME DIMINFO SRID
TABLE1 GEOM MDSYS.SDO_DIM_ELEMENT(MDSYS.SDO_DIM_ELEMENT(X,100000,200000,0.005),MDSYS.SDO_DIM_ELEMENT(Y,100000,200000,0.005))
1 rows selected
1 rows inserted
COMMIT succeeded.
CREATE INDEX succeeded.
CREATE TABLE succeeded.
Error starting at line 36 in command:
CALL SDO_GEOM.VALIDATE_LAYER_WITH_CONTEXT('TABLE1','GEOM','VALIDATION_RESULTS')
Error report:
SQL Error: ORA-13203: failed to read USER_SDO_GEOM_METADATA view
ORA-13205: internal error while parsing spatial parameters
ORA-13249: Stmt-Execute Failure: SELECT DBMS_ASSERT.SCHEMA_NAME( :1 ) FROM DUAL
ORA-29400: data cartridge error
ORA-44001: invalid schema
ORA-06512: at "SYS.DBMS_ASSERT", line 243
ORA-06512: at "MDSYS.SDO_3GL", line 665
ORA-06512: at "MDSYS.SDO_GEOM", line 3770
ORA-06512: at line 1
13203. 00000 - "failed to read USER_SDO_GEOM_METADATA view"
*Cause:    An error encountered while trying to read the USER_SDO_GEOM_METADATA
view.
*Action:   Check that USER_SDO_GEOM_METADATA has an
entry for the current geometry table.

Works for me on Windows XP 11.1.0.7
You should contact Oracle support about this type of error.
SQL> CALL SDO_GEOM.VALIDATE_LAYER_WITH_CONTEXT('TABLE1','GEOM','VALIDATION_RESULTS');
Call completed.
SQL> select * from VALIDATION_RESULTS;
SDO_ROWID     STATUS
Rows Processed <1>
1 row selected.

Selecting tolerance from user_sdo_geom_metadata

I have trouble selecting tolerance from the USER_SDO_GEOM_METADATA view.
The problem is that DIMINFO is VARRAY of 4 elements in sqlplus. I used the same logic like getting sdo_gtype from the geometry data but that did not work.
SQL> select diminfo.sdo_dim_array from user_sdo_geom_metadata
2 where table_name = 'OCF_LANDMARKS';
select diminfo.sdo_dim_array(1) from user_sdo_geom_metadata
ERROR at line 1:
ORA-00932: inconsistent datatypes: expected UDT got NUMBER
I tried second sql but that does not work either.
select diminfo.sdo_dim_array from user_sdo_geom_metadata
ERROR at line 1:
ORA-00904: "DIMINFO"."SDO_DIM_ARRAY": invalid identifier
My question is if we can retrive just the tolerance value by specifying table name and geometry column from USER_SDO_GEOM_METADATA table usinf SQL query or we have to write pl sql program to parse the DIMINFO data.
Thank you very much
Jaishri

Try this query
SELECT sdo_dimname,sdo_tolerance FROM TABLE(select DIMINFO from user_sdo_geom_metadata WHERE ROWNUM=1)
instead of "ROWNUM=1" you can place any clause to select any specific metadata

Problem with USER_SDO_GEOM_METADATA

The USER_SDO_GEOM_METADATA view will not allow rows to be inserted. The error message is:
"ORA-01779: cannot modify a column which maps to a non key-preserved table".
This error occurs whether I try to insert a row myself in SQL Plus, or Easyloader tries to insert a row, etc.
I have previously dropped this view and re-created it in other forms in order to try to get around the MapInfo problems with opening views, but I believe I have put it back to what it was originally. The View Text is as follows:
SELECT SDO_TABLE_NAME TABLE_NAME,
SDO_COLUMN_NAME COLUMN_NAME,
SDO_DIMINFO DIMINFO,
SDO_SRID SRID
FROM SDO_GEOM_METADATA_TABLE,
(select username from user_users)
WHERE sdo_owner = username
There are no options set on the view (i.e. there is no CHECK OPTION, READ ONLY etc).
I should be grateful for any suggestions and a solution asap!

I got this information, which I am passing on to you:
There are two triggers associated with the user_sdo_geom_metadata view which will be dropped when the view is dropped. So they need to be recreated with the view for the inserts/deletes on the view to work again.
The names of the triggers:
TRIGGER SDO_GEOM_TRIG_DEL1 and SDO_GEOM_TRIG_INS1 (both need to be created as MDSYS).
The PL/SQL code for creating these two triggers is in prvtgmd.plb under ($ORACLE_HOME/md/admin).
null

Null MBR in Map Builder 10.1.3.1 for raster

Dear all,
I'm building a custom loader for a raster data format. I have the sdo_georaster row populated including the geographic extent including the SRID, and the sdo_raster table populated including the blockmbr which is in row/column coordinates. Also in the user_sdo_geom_metadata, the geographic extent of the image.
When I try to preview the image by selectng the georaster table in map viewer, I get messages:
WARN [oracle.sdovis.theme.grtp] GeoRaster SRID can not be 0.
WARN [oracle.sdovis.MapMaker] null MBR resulted from buildDataMBR.
What am I still missing? Or does this message indicate I still have something wrong with my raster data?
Thanks very much,
Jim Greetham

Hi Jim,
take a look at the GeoRaster theme section on User's Guide where you will all the steps needed for a GeoRaster to be rendered with MapViewer. The error shows your SRID equal 0. Verify if you have georeferenced your image, and also if you have registered <georaster_column>.spatialextent on the user_sdo_geom_metadata view.
Joao

MapViewer metadata problem - accessing spatial data in a different schema.

I have a MapViewer application that uses data from three different schemas.
1. Dynamic Themes come from schema A.
2. Static Themes come from schema B.
3. A newly added static theme in B whose data comes from schema C.
The mapviewer datasource points to schema B where the static themes, data and metadata are defined while the dynamic themes have their own datasource specified as part of addJDBCTheme(...).
To get the newly added map to work I've had to add a view in schema B that points to C instead of referencing directly the table and I've had to add the metadata twice, once for schema B and once for schema C.
If I put the metadata in just one of the two schemas I get the following errors.
08/11/21 13:58:57 ERROR [oracle.sdovis.ThemeTable] cannot find entry in ALL_SDO_GEOM_METADATA table for theme: AMBITOS_REST
08/11/21 13:58:57 ERROR [oracle.sdovis.ThemeTable] java.sql.SQLException: Invalid column index
OR
08/11/21 13:53:39 ERROR [oracle.sdovis.theme.pgtp] java.sql.SQLException: ORA-29902: error in executing ODCIIndexStart() routine
ORA-13203: failed to read USER_SDO_GEOM_METADATA view
It's not a big deal but I'd like to know if anyone else has has similar problems.
Saludos,
Lew.
Edited by: Lew2 on Nov 21, 2008 6:42 AM

Hi Lew,
if you are using a recent version (10.1.3.1 or later) there is no need to use a view and to create the metadata in both schemas.
You need to grant selection on tables between the schemas.
You can try the following. Assume you have the MVDEMO schema (from MapViewer kit) and SCOTT schema.
1) grant select on MVDEMO Counties table to SCOTT
SQL> grant select on counties to scott;
2) Now you are ready to create a predefined theme in schema SCOTT using the MVDEMO Counties table.
- Open MapBuilder and loads the SCOTT schema.
- On the Data navigator (bottom left tree), go to Geometry tables and you should see the MVDEMO node and the COUNTIES node inside it.
- Start a wizard to create a geometry theme based on this Counties table.
- At the end you should see that the base table name is MVDEMO.COUNTIES. Therefore MapViewer will use the metadata in MVDEMO schema and there is no need to replicate it in SCOTT schema.
Joao

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 off

Sir! 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 creating spatial index

Hi all.
I have a problem during the creation of a spatial index for a table column.
The metadata is in the USER_SDO_GEOM_METADATA VIEW, but Oracle throws the message:
ORA-29855: se ha producido un error en la ejecución de la rutina ODCIINDEXCREATE
ORA-13203: fallo al leer la vista USER_SDO_GEOM_METADATA
ORA-13203: fallo al leer la vista USER_SDO_GEOM_METADATA
ORA-06512: en "MDSYS.SDO_INDEX_METHOD_10I", línea 10
The code that i use to create the index is:
DELETE FROM USER_SDO_GEOM_METADATA;
INSERT INTO USER_SDO_GEOM_METADATA
VALUES (
'E011_CIUDADES',
'F011_GEO',
MDSYS.SDO_DIM_ARRAY(
MDSYS.SDO_DIM_ELEMENT('Longitud', -180, 180, 10), -- 10 meters tolerance
MDSYS.SDO_DIM_ELEMENT('Latitud', -90, 90, 10) -- 10 meters tolerance
8307 -- SRID for 'Longitude / Latitude (WGS 84)' coordinate system
CREATE INDEX IX_SPATIAL_011_GEO
ON SYSTEM.E011_CIUDADES(F011_GEO)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS ('tablespace=ASOUSU');
I will apreciate any help. Thanks.

This is very bad:
CREATE INDEX IX_SPATIAL_011_GEO ON SYSTEM.E011_CIUDADES(F011_GEO)
INDEXTYPE IS MDSYS.SPATIAL_INDEX PARAMETERS ('tablespace=ASOUSU');It means you've stored spatial data in the SYSTEM user's schema, which, as noted, is mucho malo. Either that, or it is a typo and that is why you got: fallo al leer la vista USER_SDO_GEOM_METADATA

User_sdo_geom_metadata view

Similar Messages

Maybe you are looking for