[Geoserver-devel] [jira] (GEOS-5535) Use of SDO_TUNE.EXTENT_OF - doesn't include schema

Jonathan Moules created BugGEOS-5535
Use of SDO_TUNE.EXTENT_OF - doesn’t include schema

Issue Type:

BugBug

Affects Versions:

2.2.3

Assignee:

Andrea Aime

Components:

Oracle

Created:

07/Jan/13 5:02 AM

Description:

Per this thread: http://sourceforge.net/mailarchive/forum.php?thread_name=CA%2BnxMTtNTk50RGzwz4AbS5ZYfn32_SfYPmhoVNxn_AgsTcGQLA%40mail.gmail.com&forum_name=geoserver-users

SDO_TUNE.EXTENT_OF is installed but not functioning. I’ve investigated, there are two issues.

  1. The SDO_TUNE.EXTENT_OF query doesn’t prefix the table name with the schema name. I’m connecting with a user that doesn’t own the data, so the schema name is required. That’s why the error is a “table not found” error.
    SDO_AGGR_MBR does use the schema name, hence why it works. I believe most queries use the schema name.

  2. Not strictly a bug, but what hid this issue for so long - the code catches it and falls back to SDO_AGGR_MBR, which is fine. But are you catching it because you’re not sure SDO_TUNE.EXTENT_OF doesn’t exist? That’s what the error implies to me.
    My suggestion would be to explicitly test for SDO_TUNE.EXTENT of - it’s some simple SQL:
    select * from ALL_procedures where procedure_name = ‘EXTENT_OF’ and OBJECT_NAME = ‘SDO_TUNE’
    Returns two rows for me. If it doesn’t exist, fall back with debug to SDO_AGGR_MBR. If it does exist but still fails, fallback but include an ERROR level event in the logs.
    Just a thought.

Project:

GeoServer

Priority:

MajorMajor

Reporter:

Jonathan Moules

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your [JIRA administrators](https://jira.codehaus.org/secure/ContactAdministrators!default.jspa). For more information on JIRA, see: [http://www.atlassian.com/software/jira](http://www.atlassian.com/software/jira)