GeoServer

WMS query fails with ORA-13208 and ORA-06512 exceptions

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Not A Bug
  • Affects Version/s: 2.0-RC2
  • Fix Version/s: None
  • Component/s: Oracle, WMS
  • Labels:
    None
  • Environment:
    Windows XP, Oracle 11g, Oracle NG drivers for GeoServer.
  • Number of attachments :
    7

Description

In an Oracle database I have created two views from attached GSML_MAPPEDFEATURE_SIMPLE.sql and ER_TEST.sql and added corresponding records into USER_SDO_GEOM_METADATA:

SELECT * FROM USER_SDO_GEOM_METADATA;

TABLE_NAME COLUMN_NAME DIMINFO SRID
-------------------------- --------------------- -------------------------------------------------------------------------------------------------------------------------- ----
ER_TEST LOCATION MDSYS.SDO_DIM_ELEMENT(MDSYS.SDO_DIM_ELEMENT(longitude,-180,180,0.000001),MDSYS.SDO_DIM_ELEMENT(latitude,-90,90,0.000001)) 8311
GSML_MAPPEDFEATURE_SIMPLE LOCATION MDSYS.SDO_DIM_ELEMENT(MDSYS.SDO_DIM_ELEMENT(longitude,-180,180,0.000001),MDSYS.SDO_DIM_ELEMENT(latitude,-90,90,0.000001)) 8311

In fact, ER_TEST view is a simplified version of the GSML_MAPPEDFEATURE_SIMPLE and exposes just two fields (ID and SDO_GEOMETRY). In both cases the data is coming from the same table, the same filter conditions and joins are applied.

Then I have successfully created two layers in GeoServer with absolutely the same settings. Simple GetFeature WFS requests like http://localhost:9090/geoserver/wfs?request=GetFeature&typeName=pirsa:ER_TEST&maxFeatures=10 work perfectly in both cases. But for some reason the WMS is only producing correct output for GSML_MAPPEDFEATURE_SIMPLE feature type. When attempting to query WMS for ER_TEST (http://localhost:9090/geoserver/wms?service=WMS&version=1.1.0&request=GetMap&layers=pirsa:ER_TEST&styles=&bbox=129.102,-38.058,141.0,-26.003&width=505&height=512&srs=EPSG:4283&format=image/png) GeoServer generates an error (see Exception.txt).

What is so different in these two so similar views that causes this unexpected behaviour?

  1. ER_TEST.sql
    20/Oct/09 2:39 AM
    0.5 kB
    Pavel Golodoniuc
  2. Exception.txt
    20/Oct/09 2:39 AM
    16 kB
    Pavel Golodoniuc
  3. GSML_MAPPEDFEATURE_SIMPLE.sql
    20/Oct/09 2:39 AM
    1 kB
    Pavel Golodoniuc
  4. Oracle-SRIDnoMatchSteps.txt
    14/Dec/10 9:43 AM
    4 kB
    steve gorman
  5. SimpleOracleGeoExample.sql
    14/Dec/10 4:17 PM
    4 kB
    steve gorman
  6. SimpleOracleGeoExample.sql
    14/Dec/10 3:17 PM
    3 kB
    steve gorman
  7. ThisFixedItForMe.sql
    15/Dec/10 9:53 AM
    5 kB
    steve gorman

Activity

Hide
Andrea Aime added a comment -

I honestly have no idea, you seem to have declared the view metadata properly for both columns so GeoServer should be able to pick it up.
Have you tried with more recent versions of GeoServer, is the problem still reproducable?

If so I guess I'll need a sql script allowing me to setup the same situation on my Oracle XE install so that I can debug it step by step, or else, a VPN connection to your database.

Show
Andrea Aime added a comment - I honestly have no idea, you seem to have declared the view metadata properly for both columns so GeoServer should be able to pick it up. Have you tried with more recent versions of GeoServer, is the problem still reproducable? If so I guess I'll need a sql script allowing me to setup the same situation on my Oracle XE install so that I can debug it step by step, or else, a VPN connection to your database.
Hide
Peter Spry added a comment -

I have the same situation. Two oracle tables with SDO_GEOMETRY, connected to GeoServer202 via Oracle NG. One works fine, the other returns the SRID error.
java.lang.RuntimeException: java.io.IOException java.io.IOException null 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

P.S. both geometries are using the custom spatial reference refered to in http://jira.codehaus.org/browse/GEOS-2806

Show
Peter Spry added a comment - I have the same situation. Two oracle tables with SDO_GEOMETRY, connected to GeoServer202 via Oracle NG. One works fine, the other returns the SRID error. java.lang.RuntimeException: java.io.IOException java.io.IOException null 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 P.S. both geometries are using the custom spatial reference refered to in http://jira.codehaus.org/browse/GEOS-2806
Hide
steve gorman added a comment -

I have this same problem with 10g. See atached Oracle-SRIDnoMatchSteps.txt

Show
steve gorman added a comment - I have this same problem with 10g. See atached Oracle-SRIDnoMatchSteps.txt
Hide
steve gorman added a comment -

Simple way to reproduce my env. This guy has me pretty much brought me to a full stop. For this example my Hardware/Software is 11g with Dec14 snapshot of Oracle extension and Geoserver.

Show
steve gorman added a comment - Simple way to reproduce my env. This guy has me pretty much brought me to a full stop. For this example my Hardware/Software is 11g with Dec14 snapshot of Oracle extension and Geoserver.
Hide
steve gorman added a comment -

Adds an entry into USER_SDO_GEOM_METADATA for the view but still no luck.

Show
steve gorman added a comment - Adds an entry into USER_SDO_GEOM_METADATA for the view but still no luck.
Hide
steve gorman added a comment -

I am guessing this is a dead issue or at least a know one but since it took me a while to figure this out I figured I would post the labor for someone else to use. The problem was that I was using an Oracle View (I think any view would produce the problem) to create a GS Layer. Views don't have primary keys and thus when you try to use one as a layer you get a message from Geoserver saying as much and then when you try to preview the layer it throws the ORA errors. This link explains the fix...

http://old.nabble.com/postgresql-postgis-views-and-primary-keys-td28616028.html

and the attachment is a simple example of a working view

Show
steve gorman added a comment - I am guessing this is a dead issue or at least a know one but since it took me a while to figure this out I figured I would post the labor for someone else to use. The problem was that I was using an Oracle View (I think any view would produce the problem) to create a GS Layer. Views don't have primary keys and thus when you try to use one as a layer you get a message from Geoserver saying as much and then when you try to preview the layer it throws the ORA errors. This link explains the fix... http://old.nabble.com/postgresql-postgis-views-and-primary-keys-td28616028.html and the attachment is a simple example of a working view
Hide
Andrea Aime added a comment -

Mass transition all resolved issue that did not see any further comment in the last month to closed status

Show
Andrea Aime added a comment - Mass transition all resolved issue that did not see any further comment in the last month to closed status

People

Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: