[Geoserver-users] Failed to use SDO_TUNE.EXTENT

Angelo · April 10, 2013, 7:55pm

*Hello List
I reinstalled GeoServer rel. 2.2.4, when creating a layer when I make the bounding boxes I find the following error:*

    2013-04-10 18:39:52,570 WARN [geotools.jdbc] - Failed to use
    SDO_TUNE.EXTENT_OF, falling back on envelope aggregation
    java.sql.SQLException: ORA-44003: nome SQL non valido
    ORA-06512: a "MDSYS.SDO_TUNE", line 571
    ORA-06512: a line 1

         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395)
         at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802)
         at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
         at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
         at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)
         at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:194)
         at
    oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:853)
         at
    oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1145)
         at
    oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1267)
         at
    oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1469)
         at
    oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:389)
         at
    org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
         at
    org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
         at
    org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
         at
    org.geotools.data.oracle.OracleDialect.getOptimizedBounds(OracleDialect.java:749)
         at
    org.geotools.jdbc.JDBCDataStore.getBounds(JDBCDataStore.java:1123)
         at
    org.geotools.jdbc.JDBCFeatureSource.getBoundsInternal(JDBCFeatureSource.java:501)
         at
    org.geotools.data.store.ContentFeatureSource.getBounds(ContentFeatureSource.java:426)
         at
    org.geotools.data.store.ContentFeatureSource.getBounds(ContentFeatureSource.java:363)
         at
    org.vfny.geoserver.global.GeoServerFeatureSource.getBounds(GeoServerFeatureSource.java:591)
         at
    org.geoserver.catalog.CatalogBuilder.getNativeBounds(CatalogBuilder.java:556)
         at
    org.geoserver.catalog.CatalogBuilder.getNativeBounds(CatalogBuilder.java:538)
         at
    org.geoserver.web.data.resource.BasicResourceConfig$1.onSubmit(BasicResourceConfig.java:115)

*Do you know where is the problem? Our software environment is:**
*

  * *Tomcat 7.0.25*
  * *Geoserver 2.2.4 (war)*
  * * Geoserver-2.2.4-oracle-plugin
    *
  * *Oracle 11G (11.2)*

*Thank you very much!

Angelo
*

Andrea_Aime4 · April 11, 2013, 6:04am

On Wed, Apr 10, 2013 at 9:55 PM, Angelo <angelo.digiorgio@anonymised.com>wrote:

*Hello List
I reinstalled GeoServer rel. 2.2.4, when creating a layer when I make the bounding
boxes I find the following error:*

2013-04-10 18:39:52,570 WARN [geotools.jdbc] - Failed to use
SDO_TUNE.EXTENT_OF, falling back on envelope aggregation
java.sql.SQLException: ORA-44003: nome SQL non valido
ORA-06512: a "MDSYS.SDO_TUNE", line 571
ORA-06512: a line 1

    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395)
    at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802)
    at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
    at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
    at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)
    at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:194)
    at
oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:853)
    at
oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1145)
    at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1267)
    at
oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1469)
    at
oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:389)
    at
org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
    at
org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
    at
org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
    at
org.geotools.data.oracle.OracleDialect.getOptimizedBounds(OracleDialect.java:749)
    at org.geotools.jdbc.JDBCDataStore.getBounds(JDBCDataStore.java:1123)
    at
org.geotools.jdbc.JDBCFeatureSource.getBoundsInternal(JDBCFeatureSource.java:501)
    at
org.geotools.data.store.ContentFeatureSource.getBounds(ContentFeatureSource.java:426)
    at
org.geotools.data.store.ContentFeatureSource.getBounds(ContentFeatureSource.java:363)
    at
org.vfny.geoserver.global.GeoServerFeatureSource.getBounds(GeoServerFeatureSource.java:591)
    at
org.geoserver.catalog.CatalogBuilder.getNativeBounds(CatalogBuilder.java:556)
    at
org.geoserver.catalog.CatalogBuilder.getNativeBounds(CatalogBuilder.java:538)
    at
org.geoserver.web.data.resource.BasicResourceConfig$1.onSubmit(BasicResourceConfig.java:115)

As you can see, it's a WARN, not an ERROR. It means the fast path for
computing an envelope was tried,
and failed. Not fatal, it will just take longer to compute the bbox.
You might be affected by this one: http://jira.codehaus.org/browse/GEOS-5535

Cheers
Andrea

--

GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

Jonathan_Moules2 · April 11, 2013, 11:28am

Hi Angelo,
I picked up on this a few months ago, which is the ticket Andrea is pointing to. Its fixed in 2.2.5 and 2.3 (thanks again Andrea ).
Its not much of an issue with small datasets (few thousand features), but 100,000 plus and it’ll lock up the GeoServer admin interface for noticeable periods of time. Get into the millions and it can be several hours!
So if you have larger datasets, its worth upgrading.
Cheers,

Jonathan

···

Hello List
I reinstalled GeoServer rel. 2.2.4, when creating a layer when I make the bounding boxes I find the following error:

2013-04-10 18:39:52,570 WARN [geotools.jdbc] - Failed to use SDO_TUNE.EXTENT_OF, falling back on envelope aggregation
java.sql.SQLException: ORA-44003: nome SQL non valido
ORA-06512: a “MDSYS.SDO_TUNE”, line 571
ORA-06512: a line 1

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:194)
at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:853)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1145)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1267)
at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1469)
at oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:389)
at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
at org.geotools.data.oracle.OracleDialect.getOptimizedBounds(OracleDialect.java:749)
at org.geotools.jdbc.JDBCDataStore.getBounds(JDBCDataStore.java:1123)
at org.geotools.jdbc.JDBCFeatureSource.getBoundsInternal(JDBCFeatureSource.java:501)
at org.geotools.data.store.ContentFeatureSource.getBounds(ContentFeatureSource.java:426)
at org.geotools.data.store.ContentFeatureSource.getBounds(ContentFeatureSource.java:363)
at org.vfny.geoserver.global.GeoServerFeatureSource.getBounds(GeoServerFeatureSource.java:591)
at org.geoserver.catalog.CatalogBuilder.getNativeBounds(CatalogBuilder.java:556)
at org.geoserver.catalog.CatalogBuilder.getNativeBounds(CatalogBuilder.java:538)
at org.geoserver.web.data.resource.BasicResourceConfig$1.onSubmit(BasicResourceConfig.java:115)

As you can see, it’s a WARN, not an ERROR. It means the fast path for computing an envelope was tried,
and failed. Not fatal, it will just take longer to compute the bbox.
You might be affected by this one: http://jira.codehaus.org/browse/GEOS-5535