An Oracle datastore with a custom SRS will not work in GeoServer if the SRS does not match a native one
-------------------------------------------------------------------------------------------------------
Key: GEOS-2806
URL: http://jira.codehaus.org/browse/GEOS-2806
Project: GeoServer
Issue Type: Bug
Components: Oracle
Affects Versions: 1.7.3
Environment: Windows, Oracle 9i, Oracle NG Jars for GS, Loose BBox set to false in Oracle to get around another issue (JIRA 2383)
Reporter: Graham Davis
Assignee: Andrea Aime
Attachments: bcalbersSRS.sql, metadata_view.sql, table.sql
Oracle didn't include SRS 3005 in the 9i release, so we creatured a custom SRS for it (1000003005). The SRS definition we used in Oracle is attached. GeoServer is not able to pick this up. We tried leaving the SRS "UNKNOWN" and when we generate the BB this error appears:
Could not find an SRS Authority that understands your SRS. Please verify
that your SRS is correct - you might need to consult the SRS authority
plug ins to ensure that your SRS is listed.
No code "EPSG:UNKNOWN" from authority "European Petroleum Survey Group"
found for object of type "IdentifiedObject".
EPSG:UNKNOWN
When we try entering EPSG 3005 on the FeatureType config page, we get this error when trying to view the data on a map (using the OpenLayers demo in GS):
Caused by: java.sql.SQLException: ORA-29902: error in executing
ODCIIndexStart() routine
ORA-13208: internal error while evaluating [window SRID does not match
layer SRID] operator
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 368
ORA-06512: at line 1
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:11
2)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
at
oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.jav
a:216)
at
oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedSt
atement.java:799)
at
oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.
java:1037)
at
oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPrepared
Statement.java:839)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.
java:1132)
at
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrepare
dStatement.java:3316)
at
oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedSt
atement.java:3361)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(Delegat
ingPreparedStatement.java:93)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(Delegat
ingPreparedStatement.java:93)
at
org.geotools.jdbc.JDBCFeatureReader.<init>(JDBCFeatureReader.java:153)
at
org.geotools.jdbc.JDBCFeatureSource.getReaderInternal(JDBCFeatureSource.
java:514)
... 65 more
27 Mar 11:16:41 WARN [geotools.jdb] - There is code leaving feature
readers/iterators open, this is leaking statements and connections!
27 Mar 11:16:41 WARN [geotools.jdbc] - Error occurred closing statement
27 Mar 11:16:41 WARN [geotools.jdbc] - Error occurred closing connection
27 Mar 11:18:00 INFO [geoserver.action] - setting session and user
ftConfig to : FeatureTypeConfig[name: PLG_PHOTOLOG_OUTLINE_V alias: null
schemaName: PLG_PHOTOLOG_OUTLINE_V_Type SRS: 3005 schemaAttributes:
[org.vfny.geoserver.config.AttributeTypeInfoConfig@anonymised.com,
org.vfny.geoserver.config.AttributeTypeInfoConfig@anonymised.com,
org.vfny.geoserver.config.AttributeTypeInfoConfig@anonymised.com,
org.vfny.geoserver.config.AttributeTypeInfoConfig@anonymised.com] schemaBase
null]
27 Mar 11:18:00 WARN [geotools.jdbc] - No primary key found for
PLG_PHOTOLOG_OUTLINE_V.
rest based on schemaBase: null
27 Mar 11:18:00 WARN [geotools.jdbc] - No primary key found for
PLG_PHOTOLOG_OUTLINE_V.
It seems that a custom SRS in Oracle won't work in GS (even when the SRS is the same definition as a native EPSG one, but has a different ID). I've attached the Oracle table SQL and the metadata and view SQL as well. Let me know if you need more info to recreate this problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira