We have a large number of Oracle Spatial "features" defined (900+). I cannot get Bentley Map or GeoSpatial Administrator to "connect" to the Oracle database. It just "hangs", Using the operability option to establish a "read-only" connection type for importing data works fine, just somewhat slow (due probably to the large number of features). However, trying to establish a "read/write" type of connection, it just sits, and sits, and sits. I've got the 11g client, going to a 10g database. I've tried to "spy" on the SQL being passed to Oracle to see if an Oracle error is occuring and just not being reported, but I can't seem to get a "sensible" trace (it also just "hangs" reporting on the SQL strings.)
Questions: Is there a way to "narrow" the results (ie limit the results to a schema or a set of schemas instead of everything in ALL_SDO_GEOM_METADATA table)?
Is there any way to turn on logging for the Oracle connection part, so I can figure out why the connection "hangs" and never returns any results?
I would say, at a minumum, that one ought to be able to limit data returned to only the currently logged-in schema account. The "utlimate" control should be done at the DB level, with the DB permissions/grants. However, it would also be helpful to maybe have a variable that would contain a list of schemas that you would like to geta dat from. Maybe the thing to do is by default, only return layers in your current schema, and utilize a variable (MSGEO_SCHEMAS ??) to list additional schema to be investigated. If you wanted all schemas in the DB, then set that variable to "ALL" or "EVERYONE". Then the DB access control would take over.
That being said, is there any way to turn on SQL tracing from inside MAP so I can try and determine why the discover process "hangs".
Bruce
...unfortunately, at this time I don't believe there is a way to restrict the discovery process, but I will do some additional checking to verify that. While we're discussing this topic, how would you as an "Administrator" or "User" prefer to control the feature discovery process (e.g. define the "list" of schemas to be ignored)?
Regards,
Jeff Bielefeld [Bentley]
...to limit the scope of feature classes discovered during the "Register Features" process, use a user account that does not have DBA privileges. For example, using the following privilege assignments...
GRANT DELETE ON MYSCHEMA.MYTABLE TO MYUSER; GRANT INSERT ON MYSCHEMA.MYTABLE TO MYUSER; GRANT SELECT ON MYSCHEMA.MYTABLE TO MYUSER; GRANT UPDATE ON MYSCHEMA.MYTABLE TO MYUSER;
...should allow MYUSER (non DBA privileged account) to access the MYSCHEMA.MYTABLE object during the "Register Features" process.
Bentley Map/GSA - 8.11.5.49
MicroStation - 8.11.5.17