With a spatial db where users share the same set of MDSYS tables, just wonder if the tables store user information along with data in a row? That is, if I do an datapump export for a schema, would the export dmp file contains rows in MDSYS tables that belong to the specified schema?The only user data that is stored in the MDSYS schema is the spatial metadata that describes the data held in an sdo_geometry column in a table. This is needed for when creating an RTree spatial index.
Import and Export (including data pump versions) simply export and import tables. If the table contains an sdo_geometry column then it is handled automatically (as is any sdo_geom_metadata that describes the column. So, there is nothing for you to worry about.
create table foo ( foo_id integer, create_date date, modified_date date, geom sdo_geometry); -- Now describe the data in the geom column... INSERT INTO USER_SDO_GEOM_METADATA ( Table_Name, Column_Name, Diminfo, SRID ) VALUES ( 'FOO', 'GEOM', SDO_DIM_ARRAY( SDO_DIM_ELEMENT('X', 5900000, 6100000, .05), -- Range of x/longitude ordinates SDO_DIM_ELEMENT('Y', 2000000, 2200000, .05)), -- Range of y/latitude ordinates 2872); -- Spatial Reference Identifier see mdsys.cs_srs commit; -- Now we have created the table and metadata we can create a 2D spatial index on points create index foo_geom on foo(geom) indextype is mdsys.spatial_index parameters('sdo_indx_dims=2,layer_gtype=point');
Sorry about the basic question, but I plan to read and play with Oracle spatial to understand it more.Best way to learn.
Strictly speaking this is not true. When you create a table with one or more SDO_GEOMETRY colum(s), only that table is created.
when you create a table with an sdo_geometry column a number of secondary tables are created.
This, however, is very very true. Do NOT mess with the MDRS_#####$ sequence and the MDRT_#####$ table.
Ignore them at all times.