Hi All,
Our production spatial database is Oracle 10g (yet), and there are some public table exported via DBLink to Oracle XE 11.2. GeoServer can connect correctly both type of Oracle, and it serves WMS layers as usual. But when I try the KML service on Oracle XE the service is very slow in case of big (600 000 records) table.
I’ve realized that in case of Oracle 10g, before the spatial filter a ‘SELECT SDO_TUNE.EXTENT_OF (‘My_table’, ‘My_geom’) FROM DUAL’ statement called.
In case of Ora XE: SELECT SDO_AGGR_MBR (MyGeom) FROM My_Table
Why differs?
I’ve tried also to CREATE TABLE GEOMETRY_COLUMNS as written in http://docs.geoserver.org/latest/en/user/data/database/oracle.html, But it’s still the same.
How can I make fast GoogleEarth kml service on OracleXE with GeoServer?
Why should DB always want to aggregate the whole table’s geometry to filter a portion of it? Why not use the MBR of the ALL_SDO_GEOM_METADATA view?
Any advice and suggestions will be greatly appreciated!
Thanks for advance!
Zsolt Magyar