APEX and the question: Where have remained my metadata?
Anyone who has ever created a small or large APEX Geo-application, described in the following situation may have experienced before. Wednesday, September 29, 2010
Best Way To Remove Fat From Sausage
table_name, column_name
,
diminfo, ,
srid)
values (
'GEOTAB'
'geometry',
sdo_dim_array (sdo_dim_element ('X', -180,180,0.005)
sdo_dim_element ('Y', -90,90,0.005)),
8307 );
Expanding an application in APEX and used for registering the SDO_GEOMETRY column in the metadata of the SQL Workshop and then as far as running without problems.
will then ordinarily be applied also still the same the spatial index and you get the error message ORA-00942: table or view does not exist.
A short 
returns no results. 
SQL> select * from USER_SDO_GEOM_METADATA where table_name = 'GEOTAB';
What happened? Where the entry remains in the metadata?With DBA rights, it is easy to search in the table of the user MDSYS.
SQL> select * from mdsys.sdo_geom_metadata_table;
There is in the column SDO_OWNER then find instead of the expected user (in this example SPATIAL) according to the Web listener used by APEX to either ANONYMOUS, APEX_PUBLIC_USER or HTMLDB_PUBLIC_USER. This is the username of the APEX session, then in the scheme also SDO_GEOMETRY the metadata is registered.
How can this be cleaned up now? There is in the column SDO_OWNER then find instead of the expected user (in this example SPATIAL) according to the Web listener used by APEX to either ANONYMOUS, APEX_PUBLIC_USER or HTMLDB_PUBLIC_USER. This is the username of the APEX session, then in the scheme also SDO_GEOMETRY the metadata is registered.
Ask your DBA to your users UPDATE privileges for the table MDSYS SDO_GEOM_METADATA_TABLE blame.
SQL> grant update on mdsys.sdo_geom_metadata_table;
SDO_OWNER Then change the entry as follows:
SQL> update MDSYS.SDO_GEOM_METADATA_TABLE
set sdo_owner = 'SPATIAL'
where sdo_table_name = ' GEOTAB 'and sdo_owner =' ANONYMOUS ';
where sdo_table_name = ' GEOTAB 'and sdo_owner =' ANONYMOUS ';
if you check the metadata should now all be alright.
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment