[Geoserver-users] Problem with Oracle 9i FeatureType

[Jukka_Rahkonen]

Hi,

I have Geoserver 1.3.0 PR1 installed on Windows XP.
I have my spatial data on Oracle db (Oracle 9i Enterprise Edition 9.2.0.4.0) and one of the table columns is primary key.
I can make a datastore from my Oracle without problems with Geoserver OCI driver and after that I have tables available for creating a featuretype. I can also create a FeatureType, but my problem is that the featuretype is not working.

In Oracle ALL_SDO_GEOM_METADATA I have the following colums and data for the table I would like to use:
Column Value
OWNER GIS_USER
TABLE_NAME GIS_POLYGONS
COLUMN_NAME GEOLOC
SRID 294914

SRID 294914 is the code that Oracle is using for my reference system and it equals to epsg code 2393.
However, there seems to be something wrong with this code, because when starting Geoserver is prints on the screen the following warning:
12788 [WARNING] org.geotools.data.oracle.OracleDataStore - Could not map SRID
294914 to CRS:java.io.IOException: No CRS for srid 294914

When I am creating featuretype with the Geoserver configuration utility, it gets the columns of the table and shows correct datatypes for them, except for the GEOLOC field which is my geometry field. For that field the utility is not reporting any data type but the box is just empty. The SRS box is also empty and I can not generate the bounding box by pressing the "Generate" button. All I can get by doing that is a message: "The FeatureType 'GIS_POLYGONS' has a NULL extent. HINT: the dataset is empty or has no default geometry attribute."

I can feed manually the SRS value 2393 as well as a bounding box but it does not help me very much.
If I try to use my featuretype through WFS then "getcapabilities" works OK and advertises the featuretype, but
"getfeature" gives me only the following error message:

<ServiceExceptionReport version="1.2.0" xsi:schemaLocation="http://www.opengis.net/ogc http://localhost:8080/geoserver/schemas//wfs/1.0.0/OGC-exception.xsd&quot;&gt;
<ServiceException>
       null error:Translator error </ServiceException>
</ServiceExceptionReport>

I suppose I have now two or three problems: first to make geoserver to recognise GEOLOC as a default geometry attribute, and second to make it use the correct SRS. Possibly there is also something odd with my primary key, because the last error message is the same that is mentioned in Geoserver FAQ in connection with PostGIS database missing the OID field. Should the primary key in Oracle have some fixed column name, or?

Regards,

Jukka Rahkonen

[Luca_Morandini2]

Rahkonen Jukka wrote:

I have Geoserver 1.3.0 PR1 installed on Windows XP.

<cut/>

I suppose I have now two or three problems: first to make geoserver to recognise GEOLOC as a default geometry attribute,

It takes the SDO_GEOMETRY column whatever its name, if more than one is present in table, Geoserver gets confused and refuses to cooperate.

and second to make it use the correct SRS.

Have you created the spatial index on your SDO_GEOMETRY column ?

Possibly there is also something odd with my primary key,
because the last error message is the same that is mentioned
in Geoserver FAQ
in connection with PostGIS database missing the OID field.
Should the primary key in Oracle have some fixed column name, or?

No, just add a PK.

Regards,

--------------------
    Luca Morandini
www.lucamorandini.it
--------------------

[Jukka_Rahkonen]

---

Lähettäjä: geoserver-users-admin@lists.sourceforge.net puolesta: Luca Morandini
Lähetetty: ma 6.3.2006 13:45
Vastaanottaja: geoserver-users@lists.sourceforge.net
Aihe: [Geoserver-users] Re: Problem with Oracle 9i FeatureType

Rahkonen Jukka wrote:

I have Geoserver 1.3.0 PR1 installed on Windows XP.

I suppose I have now two or three problems:
first to make geoserver to recognise GEOLOC as a default geometry attribute,

It takes the SDO_GEOMETRY column whatever its name, if more than one is
present in table, Geoserver gets confused and refuses to cooperate.
I have just one SDO_GEOMETRY column. SQL*Plus gives me with “desc”

GEOLOC MDSYS.SDO_GEOMETRY

However, Geoserver FeatureType Editor shows

GEOLOC: [nothing here, just empty field] nillable:true min:0 max:1

So I think that Geoserver does not recognise my SDO_GEOMETRY column now.

and second to make it use the correct SRS.

Have you created the spatial index on your SDO_GEOMETRY column ?
Yes.

Possibly there is also something odd with my primary key,
because the last error message is the same that is mentioned
in Geoserver FAQ
in connection with PostGIS database missing the OID field.
Should the primary key in Oracle have some fixed column name, or?

No, just add a PK.
I have already primary key, I was just wondering if it makes difference to
have in on a column named “LOHKONRO”

Regards,

---

Luca Morandini
www.lucamorandini.it

---

---

This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

---

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Luca_Morandini2]

Rahkonen Jukka wrote:

However, Geoserver FeatureType Editor shows
GEOLOC: [nothing here, just empty field] nillable:true min:0 max:1
So I think that Geoserver does not recognise my SDO_GEOMETRY column now.

It does, but it doesn't show anything for it... I agree it would be nice to have a "SDO_GEOMETRY" or something else shown in there.

I have already primary key, I was just wondering if it makes difference to
have in on a column named "LOHKONRO"

I suppose it doesn't, but I never tried giving a column that name

Regards,

--------------------
    Luca Morandini
www.lucamorandini.it
--------------------

[Luca_Morandini2]

Rahkonen Jukka wrote:

------------------------------------------------------------------------
*Lähettäjä:* geoserver-users-admin@lists.sourceforge.net puolesta: Luca Morandini
*Lähetetty:* ma 6.3.2006 13:45
*Vastaanottaja:* geoserver-users@lists.sourceforge.net
*Aihe:* [Geoserver-users] Re: Problem with Oracle 9i FeatureType

>Rahkonen Jukka wrote:
>> > I have Geoserver 1.3.0 PR1 installed on Windows XP.
<cut/>
>> I suppose I have now two or three problems:

...come (late) to think of it: have you run
execute sdo_migrate.to_current('YOUR_TABLE', 'YOUR_GEOMETRY_COLUM', 100); ?

In some cases (for polygons, I guess) shp2sdo puts the old (8i) gtypes into the geometry column, and this procedure updates them (BTW, change
YOUR_TABLE and YOUR_GEOMETRY_COLUM with your actual values, both in uppercase).

Regards,

--------------------
    Luca Morandini
www.lucamorandini.it
--------------------

[Jukka_Rahkonen]

...come (late) to think of it: have you run
execute sdo_migrate.to_current('YOUR_TABLE', 'YOUR_GEOMETRY_COLUM', 100); ?

In some cases (for polygons, I guess) shp2sdo puts the old (8i) gtypes
into the geometry column, and this procedure updates them (BTW, change
YOUR_TABLE and YOUR_GEOMETRY_COLUM with your actual values, both in
uppercase).

Regards,

--------------------
   Luca Morandini
www.lucamorandini.it
--------------------

My data in Oracle are maintained with some MapInfo tools and new GTYPES like "2003" are used.
You wrote that there should not be any problem in finding the SDO_GEOMETRY column. But still
the FeatureType Editor keeps on saying me "The FeatureType 'GIS_POLYGONS' has a NULL
extent. HINT: the dataset is empty or has no default geometry attribute."
And when starting Geoserver it warns me "12788 [WARNING]
org.geotools.data.oracle.OracleDataStore - Could not map SRID 294914 to
CRS:java.io.IOException: No CRS for srid 294914
Obviously the connection to Oracle works, because I think that this SRID must come
either from SDO_GEOM_METADATA or the SDO_GEOMETRY column itself.

Should this work also with Oracle 9i and not only with 10g? And what should I think about
<ServiceException>
       null error:Translator error </ServiceException>
as a response to "getfeature"

Any suggestions about step by step procedure so I could isolate the problem?

Regards,

Jukka

[Luca_Morandini2]

Rahkonen Jukka wrote:

...come (late) to think of it: have you run
execute sdo_migrate.to_current('YOUR_TABLE', 'YOUR_GEOMETRY_COLUM', 100); ?

My data in Oracle are maintained with some MapInfo tools and new GTYPES like "2003" are used.

Well, I tried

And when starting Geoserver it warns me "12788 [WARNING] org.geotools.data.oracle.OracleDataStore - Could not map SRID 294914 to CRS:java.io.IOException: No CRS for srid 294914

The same happens on my machine, but those data are found and displayed properly (though I have Oracle 10g).

Any suggestions about step by step procedure so I could isolate the problem?

You might try to export those data in a Shapefile and then imports them back via shp2sdo: just to rule out any trouble with the way MapInfo stores data in Oracle tables.

Regards,

--------------------
    Luca Morandini
www.lucamorandini.it
--------------------

[Chris_Holmes1]

Rahkonen Jukka wrote:

...come (late) to think of it: have you run
execute sdo_migrate.to_current('YOUR_TABLE', 'YOUR_GEOMETRY_COLUM', 100); ?

In some cases (for polygons, I guess) shp2sdo puts the old (8i) gtypes
into the geometry column, and this procedure updates them (BTW, change
YOUR_TABLE and YOUR_GEOMETRY_COLUM with your actual values, both in
uppercase).

Regards,

--------------------
  Luca Morandini
www.lucamorandini.it
--------------------

My data in Oracle are maintained with some MapInfo tools and new GTYPES like "2003" are used. You wrote that there should not be any problem in finding the SDO_GEOMETRY column. But still the FeatureType Editor keeps on saying me "The FeatureType 'GIS_POLYGONS' has a NULL extent. HINT: the dataset is empty or has no default geometry attribute." And when starting Geoserver it warns me "12788 [WARNING] org.geotools.data.oracle.OracleDataStore - Could not map SRID 294914 to CRS:java.io.IOException: No CRS for srid 294914
Obviously the connection to Oracle works, because I think that this SRID must come either from SDO_GEOM_METADATA or the SDO_GEOMETRY column itself.

Should this work also with Oracle 9i and not only with 10g? And what should I think about <ServiceException>
       null error:Translator error </ServiceException>
as a response to "getfeature"
Any suggestions about step by step procedure so I could isolate the problem?

In the GeoServer FeatureType editor, could you try putting in 2393, the EPSG code, instead of the 294914 oracle srid? I think we may actually not be using the native oracle srid stuff, and just using an epsg database...

Chris

Regards,
Jukka

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Chris Holmes
The Open Planning Project
thoughts at: http://cholmes.wordpress.com

[Luca_Morandini2]

Chris Holmes wrote:

In the GeoServer FeatureType editor, could you try putting in 2393, the EPSG code, instead of the 294914 oracle srid? I think we may actually not be using the native oracle srid stuff, and just using an epsg database...

Chris, you're off-mark here.
If I tried to issue the Oracle SRID instead of the EPSG code, I wouldn't be even able to create a feature type using the Geoserver management console; hence, the cause for the afore mentioned message should be sought somewhere else.

Regards,

--------------------
    Luca Morandini
www.lucamorandini.it
--------------------

[Chris_Holmes1]

Luca Morandini wrote:

Chris Holmes wrote:

In the GeoServer FeatureType editor, could you try putting in 2393, the EPSG code, instead of the 294914 oracle srid? I think we may actually not be using the native oracle srid stuff, and just using an epsg database...

Chris, you're off-mark here.
If I tried to issue the Oracle SRID instead of the EPSG code, I wouldn't be even able to create a feature type using the Geoserver management console; hence, the cause for the afore mentioned message should be sought somewhere else.

Apologies, should have read the thread more closely. It actually looks like he already tried that...

> I can feed manually the SRS value 2393 as well as a bounding box but
> it does not help me very much.
> If I try to use my featuretype through WFS then "getcapabilities"
> works OK and advertises the featuretype, but
> "getfeature" gives me only the following error message:

> <ServiceExceptionReport version="1.2.0"
> xsi:schemaLocation="http://www.opengis.net/ogc
> http://localhost:8080/geoserver/schemas//wfs/1.0.0/OGC-exception.xsd&quot;&gt;
> <ServiceException>
> null error:Translator error </ServiceException>
> </ServiceExceptionReport>

[snip]

> Possibly there is also something odd with my primary key, because the > last error message is the same that is mentioned in Geoserver FAQ in
> connection with PostGIS database missing the OID field.
Actually this error is more generic, it just means that something went wrong during the process of writing it. Could you go to the admin tool, to Config -> Server -> Verbose Exceptions and set it to true?

Then do the same thing, and you will get a better stack trace in the error report. Give this back to us, and it may help us to solve the problem.

best regards,

Chris

Regards,

--------------------
   Luca Morandini
www.lucamorandini.it
--------------------

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Chris Holmes
The Open Planning Project
thoughts at: http://cholmes.wordpress.com

[Jukka_Rahkonen]

[snip]

Could you go to the admin tool,
to Config → Server → Verbose Exceptions and set it to true?

Hi,

I edited epsg.properties according to
http://docs.codehaus.org/display/GEOSDOC/Custom+projection+definition+in+Geoserver
and created a copy of EPSG:2393 with value 294914. I think I succeeded in that because the new value became available for FeatureType editor. As far as I understood using it did not change anything, though.

Below is what I got on console screen after adding “Verbose exceptions” and making WFS request “getfeature” for my Oracle feature type.

Regards,

-Jukka-

10:17:25.311 EVENT Started HttpContext[/]
438788 [INFO] org.vfny.geoserver.wfs.servlets.WfsDispatcher - req_type is 3
438798 [INFO] org.vfny.geoserver.servlets.AbstractService - Looking for configu
red service responses’ strategy
438798 [INFO] org.vfny.geoserver.servlets.AbstractService - Looking for configu
red service strategy PARTIAL-BUFFER
438798 [INFO] org.vfny.geoserver.servlets.AbstractService - Using service strat
egy class org.vfny.geoserver.servlets.PartialBufferStrategy
438798 [INFO] org.vfny.geoserver.servlets.AbstractService - Set buffer size to
50
438798 [INFO] org.vfny.geoserver.servlets.AbstractService - handling request:
Request: null
output format:GML2
max features:2147483647
version:1.0.0
queries:
Query
feature type: GIS_POLYGONS
[properties: ALL ]

459015 [INFO] org.vfny.geoserver.servlets.PartialBufferStrategy - OutputStream
was successfully aborted.
467576 [WARNING] org.vfny.geoserver.ServiceException - encountered error: null
error:Translator error
StackTrace: javax.xml.transform.TransformerException: Translator error
at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:122)
at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:97)
at org.vfny.geoserver.wfs.responses.GML2FeatureResponseDelegate.encode(G
ML2FeatureResponseDelegate.java:225)
at org.vfny.geoserver.wfs.responses.FeatureResponse.writeTo(FeatureRespo
nse.java:131)
at org.vfny.geoserver.servlets.AbstractService.doService(AbstractService
.java:510)
at org.vfny.geoserver.servlets.AbstractService.doGet(AbstractService.jav
a:276)
at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doResponse(WfsDispatche
r.java:284)
at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doGet(WfsDispatcher.jav
a:213)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358
)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApp
licationHandler.java:342)
at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCha
racterEncodingFilter.java:122)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApp
licationHandler.java:334)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicati
onHandler.java:286)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:5
67)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplication
Context.java:525)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:790)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:961)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
197)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:276)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:511)
Caused by: java.lang.ArithmeticException: / by zero
at org.geotools.data.oracle.sdo.SDO.coordinates(SDO.java:2081)
at org.geotools.data.oracle.sdo.SDO.create(SDO.java:2295)
at org.geotools.data.oracle.sdo.GeometryConverter.asGeometry(GeometryCon
verter.java:105)
at org.geotools.data.oracle.attributeio.SDOAttributeIO.read(SDOAttribute
IO.java:98)
at org.geotools.data.jdbc.QueryData.read(QueryData.java:183)
at org.geotools.data.jdbc.JDBCFeatureReader.readFeature(JDBCFeatureReade
r.java:106)
at org.geotools.data.jdbc.JDBCFeatureReader.next(JDBCFeatureReader.java:
86)
at org.geotools.data.MaxFeatureReader.next(MaxFeatureReader.java:55)
at org.geotools.data.DefaultFeatureResults.getBounds(DefaultFeatureResul
ts.java:200)
at org.geotools.gml.producer.FeatureTransformer$FeatureTranslator.encode
(FeatureTransformer.java:388)
at org.geotools.xml.transform.TransformerBase$XMLReaderSupport.parse(Tra
nsformerBase.java:603)
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:463)
at org.geotools.xml.transform.TransformerBase$Task.run(TransformerBase.j
ava:285)
at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:118)
… 25 more

java.lang.ArithmeticException: / by zero
at org.geotools.data.oracle.sdo.SDO.coordinates(SDO.java:2081)
at org.geotools.data.oracle.sdo.SDO.create(SDO.java:2295)
at org.geotools.data.oracle.sdo.GeometryConverter.asGeometry(GeometryCon
verter.java:105)
at org.geotools.data.oracle.attributeio.SDOAttributeIO.read(SDOAttribute
IO.java:98)
at org.geotools.data.jdbc.QueryData.read(QueryData.java:183)
at org.geotools.data.jdbc.JDBCFeatureReader.readFeature(JDBCFeatureReade
r.java:106)
at org.geotools.data.jdbc.JDBCFeatureReader.next(JDBCFeatureReader.java:
86)
at org.geotools.data.MaxFeatureReader.next(MaxFeatureReader.java:55)
at org.geotools.data.DefaultFeatureResults.getBounds(DefaultFeatureResul
ts.java:200)
at org.geotools.gml.producer.FeatureTransformer$FeatureTranslator.encode
(FeatureTransformer.java:388)
at org.geotools.xml.transform.TransformerBase$XMLReaderSupport.parse(Tra
nsformerBase.java:603)
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:463)
at org.geotools.xml.transform.TransformerBase$Task.run(TransformerBase.j
ava:285)
at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:118)
at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:97)
at org.vfny.geoserver.wfs.responses.GML2FeatureResponseDelegate.encode(G
ML2FeatureResponseDelegate.java:225)
at org.vfny.geoserver.wfs.responses.FeatureResponse.writeTo(FeatureRespo
nse.java:131)
at org.vfny.geoserver.servlets.AbstractService.doService(AbstractService
.java:510)
at org.vfny.geoserver.servlets.AbstractService.doGet(AbstractService.jav
a:276)
at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doResponse(WfsDispatche
r.java:284)
at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doGet(WfsDispatcher.jav
a:213)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358
)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApp
licationHandler.java:342)
at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCha
racterEncodingFilter.java:122)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApp
licationHandler.java:334)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicati
onHandler.java:286)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:5
67)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplication
Context.java:525)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:790)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:961)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
197)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:276)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:511)

org.vfny.geoserver.ServiceException: null error:Translator error
at org.vfny.geoserver.wfs.responses.GML2FeatureResponseDelegate.encode(G
ML2FeatureResponseDelegate.java:234)
at org.vfny.geoserver.wfs.responses.FeatureResponse.writeTo(FeatureRespo
nse.java:131)
at org.vfny.geoserver.servlets.AbstractService.doService(AbstractService
.java:510)
at org.vfny.geoserver.servlets.AbstractService.doGet(AbstractService.jav
a:276)
at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doResponse(WfsDispatche
r.java:284)
at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doGet(WfsDispatcher.jav
a:213)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358
)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApp
licationHandler.java:342)
at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCha
racterEncodingFilter.java:122)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApp
licationHandler.java:334)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicati
onHandler.java:286)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:5
67)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplication
Context.java:525)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:790)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:961)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
197)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:276)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:511)
Caused by: javax.xml.transform.TransformerException: Translator error
at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:122)
at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:97)
at org.vfny.geoserver.wfs.responses.GML2FeatureResponseDelegate.encode(G
ML2FeatureResponseDelegate.java:225)
… 23 more
Caused by: java.lang.ArithmeticException: / by zero
at org.geotools.data.oracle.sdo.SDO.coordinates(SDO.java:2081)
at org.geotools.data.oracle.sdo.SDO.create(SDO.java:2295)
at org.geotools.data.oracle.sdo.GeometryConverter.asGeometry(GeometryCon
verter.java:105)
at org.geotools.data.oracle.attributeio.SDOAttributeIO.read(SDOAttribute
IO.java:98)
at org.geotools.data.jdbc.QueryData.read(QueryData.java:183)
at org.geotools.data.jdbc.JDBCFeatureReader.readFeature(JDBCFeatureReade
r.java:106)
at org.geotools.data.jdbc.JDBCFeatureReader.next(JDBCFeatureReader.java:
86)
at org.geotools.data.MaxFeatureReader.next(MaxFeatureReader.java:55)
at org.geotools.data.DefaultFeatureResults.getBounds(DefaultFeatureResul
ts.java:200)
at org.geotools.gml.producer.FeatureTransformer$FeatureTranslator.encode
(FeatureTransformer.java:388)
at org.geotools.xml.transform.TransformerBase$XMLReaderSupport.parse(Tra
nsformerBase.java:603)
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:463)
at org.geotools.xml.transform.TransformerBase$Task.run(TransformerBase.j
ava:285)
at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:118)
… 25 more

Luca Morandini wrote:

Chris Holmes wrote:

In the GeoServer FeatureType editor, could you try putting in 2393,
the EPSG code, instead of the 294914 oracle srid? I think we may
actually not be using the native oracle srid stuff, and just using an
epsg database…

Chris, you’re off-mark here.
If I tried to issue the Oracle SRID instead of the EPSG code, I wouldn’t
be even able to create a feature type using the Geoserver management
console; hence, the cause for the afore mentioned message should be
sought somewhere else.
Apologies, should have read the thread more closely. It actually looks
like he already tried that…

I can feed manually the SRS value 2393 as well as a bounding box but
it does not help me very much.
If I try to use my featuretype through WFS then “getcapabilities”
works OK and advertises the featuretype, but
“getfeature” gives me only the following error message:

null error:Translator error

[Jukka_Rahkonen]

Hello,

I have had no time to work on this problem lately, despite that I created anothet datastore from my Oracle database by using "Oracle" connection instead of "Oracle (OCI)". As far as I understand the situation remained the same. I could make a new featuretype and "getcapabilities" works but "getfeature" returns me nothing an error. Geoserver works fine with shapefiles, but our native data is in Oracle so I am about jammed now.

Regards,

Jukka Rahkonen

________________________________

Lähettäjä: geoserver-users-admin@lists.sourceforge.net puolesta: Rahkonen Jukka
Lähetetty: ti 7.3.2006 10:36
Vastaanottaja: geoserver-users@lists.sourceforge.net
Aihe: Re: [Geoserver-users] Re: Problem with Oracle 9i FeatureType

[snip]

Could you go to the admin tool,
to Config -> Server -> Verbose Exceptions and set it to true?

Hi,

I edited epsg.properties according to
http://docs.codehaus.org/display/GEOSDOC/Custom+projection+definition+in+Geoserver
and created a copy of EPSG:2393 with value 294914. I think I succeeded in that because the new value became available for FeatureType editor. As far as I understood using it did not change anything, though.

Below is what I got on console screen after adding "Verbose exceptions" and making WFS request "getfeature" for my Oracle feature type.

Regards,

-Jukka-

10:17:25.311 EVENT Started HttpContext[/]
438788 [INFO] org.vfny.geoserver.wfs.servlets.WfsDispatcher - req_type is 3
438798 [INFO] org.vfny.geoserver.servlets.AbstractService - Looking for configu
red service responses' strategy
438798 [INFO] org.vfny.geoserver.servlets.AbstractService - Looking for configu
red service strategy PARTIAL-BUFFER
438798 [INFO] org.vfny.geoserver.servlets.AbstractService - Using service strat
egy class org.vfny.geoserver.servlets.PartialBufferStrategy
438798 [INFO] org.vfny.geoserver.servlets.AbstractService - Set buffer size to
50
438798 [INFO] org.vfny.geoserver.servlets.AbstractService - handling request:
Request: null
output format:GML2
max features:2147483647
version:1.0.0
queries:
  Query
   feature type: GIS_POLYGONS
   [properties: ALL ]

459015 [INFO] org.vfny.geoserver.servlets.PartialBufferStrategy - OutputStream
was successfully aborted.
467576 [WARNING] org.vfny.geoserver.ServiceException - encountered error: null
error:Translator error
StackTrace: javax.xml.transform.TransformerException: Translator error
        at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:122)
        at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:97)
        at org.vfny.geoserver.wfs.responses.GML2FeatureResponseDelegate.encode(G
ML2FeatureResponseDelegate.java:225)
        at org.vfny.geoserver.wfs.responses.FeatureResponse.writeTo(FeatureRespo
nse.java:131)
        at org.vfny.geoserver.servlets.AbstractService.doService(AbstractService
.java:510)
        at org.vfny.geoserver.servlets.AbstractService.doGet(AbstractService.jav
a:276)
        at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doResponse(WfsDispatche
r.java:284)
        at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doGet(WfsDispatcher.jav
a:213)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358
)
        at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApp
licationHandler.java:342)
        at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCha
racterEncodingFilter.java:122)
        at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApp
licationHandler.java:334)
        at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicati
onHandler.java:286)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:5
67)
        at org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
        at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplication
Context.java:525)
        at org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
        at org.mortbay.http.HttpServer.service(HttpServer.java:879)
        at org.mortbay.http.HttpConnection.service(HttpConnection.java:790)
        at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:961)
        at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807)
        at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
197)
        at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:276)
        at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:511)
Caused by: java.lang.ArithmeticException: / by zero
        at org.geotools.data.oracle.sdo.SDO.coordinates(SDO.java:2081)
        at org.geotools.data.oracle.sdo.SDO.create(SDO.java:2295)
        at org.geotools.data.oracle.sdo.GeometryConverter.asGeometry(GeometryCon
verter.java:105)
        at org.geotools.data.oracle.attributeio.SDOAttributeIO.read(SDOAttribute
IO.java:98)
        at org.geotools.data.jdbc.QueryData.read(QueryData.java:183)
        at org.geotools.data.jdbc.JDBCFeatureReader.readFeature(JDBCFeatureReade
r.java:106)
        at org.geotools.data.jdbc.JDBCFeatureReader.next(JDBCFeatureReader.java:
86)
        at org.geotools.data.MaxFeatureReader.next(MaxFeatureReader.java:55)
        at org.geotools.data.DefaultFeatureResults.getBounds(DefaultFeatureResul
ts.java:200)
        at org.geotools.gml.producer.FeatureTransformer$FeatureTranslator.encode
(FeatureTransformer.java:388)
        at org.geotools.xml.transform.TransformerBase$XMLReaderSupport.parse(Tra
nsformerBase.java:603)
        at org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:463)
        at org.geotools.xml.transform.TransformerBase$Task.run(TransformerBase.j
ava:285)
        at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:118)
        ... 25 more
---------
java.lang.ArithmeticException: / by zero
        at org.geotools.data.oracle.sdo.SDO.coordinates(SDO.java:2081)
        at org.geotools.data.oracle.sdo.SDO.create(SDO.java:2295)
        at org.geotools.data.oracle.sdo.GeometryConverter.asGeometry(GeometryCon
verter.java:105)
        at org.geotools.data.oracle.attributeio.SDOAttributeIO.read(SDOAttribute
IO.java:98)
        at org.geotools.data.jdbc.QueryData.read(QueryData.java:183)
        at org.geotools.data.jdbc.JDBCFeatureReader.readFeature(JDBCFeatureReade
r.java:106)
        at org.geotools.data.jdbc.JDBCFeatureReader.next(JDBCFeatureReader.java:
86)
        at org.geotools.data.MaxFeatureReader.next(MaxFeatureReader.java:55)
        at org.geotools.data.DefaultFeatureResults.getBounds(DefaultFeatureResul
ts.java:200)
        at org.geotools.gml.producer.FeatureTransformer$FeatureTranslator.encode
(FeatureTransformer.java:388)
        at org.geotools.xml.transform.TransformerBase$XMLReaderSupport.parse(Tra
nsformerBase.java:603)
        at org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:463)
        at org.geotools.xml.transform.TransformerBase$Task.run(TransformerBase.j
ava:285)
        at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:118)
        at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:97)
        at org.vfny.geoserver.wfs.responses.GML2FeatureResponseDelegate.encode(G
ML2FeatureResponseDelegate.java:225)
        at org.vfny.geoserver.wfs.responses.FeatureResponse.writeTo(FeatureRespo
nse.java:131)
        at org.vfny.geoserver.servlets.AbstractService.doService(AbstractService
.java:510)
        at org.vfny.geoserver.servlets.AbstractService.doGet(AbstractService.jav
a:276)
        at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doResponse(WfsDispatche
r.java:284)
        at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doGet(WfsDispatcher.jav
a:213)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358
)
        at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApp
licationHandler.java:342)
        at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCha
racterEncodingFilter.java:122)
        at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApp
licationHandler.java:334)
        at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicati
onHandler.java:286)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:5
67)
        at org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
        at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplication
Context.java:525)
        at org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
        at org.mortbay.http.HttpServer.service(HttpServer.java:879)
        at org.mortbay.http.HttpConnection.service(HttpConnection.java:790)
        at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:961)
        at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807)
        at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
197)
        at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:276)
        at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:511)

org.vfny.geoserver.ServiceException: null error:Translator error
        at org.vfny.geoserver.wfs.responses.GML2FeatureResponseDelegate.encode(G
ML2FeatureResponseDelegate.java:234)
        at org.vfny.geoserver.wfs.responses.FeatureResponse.writeTo(FeatureRespo
nse.java:131)
        at org.vfny.geoserver.servlets.AbstractService.doService(AbstractService
.java:510)
        at org.vfny.geoserver.servlets.AbstractService.doGet(AbstractService.jav
a:276)
        at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doResponse(WfsDispatche
r.java:284)
        at org.vfny.geoserver.wfs.servlets.WfsDispatcher.doGet(WfsDispatcher.jav
a:213)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358
)
        at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApp
licationHandler.java:342)
        at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCha
racterEncodingFilter.java:122)
        at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApp
licationHandler.java:334)
        at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicati
onHandler.java:286)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:5
67)
        at org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
        at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplication
Context.java:525)
        at org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
        at org.mortbay.http.HttpServer.service(HttpServer.java:879)
        at org.mortbay.http.HttpConnection.service(HttpConnection.java:790)
        at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:961)
        at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807)
        at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
197)
        at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:276)
        at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:511)
Caused by: javax.xml.transform.TransformerException: Translator error
        at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:122)
        at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:97)
        at org.vfny.geoserver.wfs.responses.GML2FeatureResponseDelegate.encode(G
ML2FeatureResponseDelegate.java:225)
        ... 23 more
Caused by: java.lang.ArithmeticException: / by zero
        at org.geotools.data.oracle.sdo.SDO.coordinates(SDO.java:2081)
        at org.geotools.data.oracle.sdo.SDO.create(SDO.java:2295)
        at org.geotools.data.oracle.sdo.GeometryConverter.asGeometry(GeometryCon
verter.java:105)
        at org.geotools.data.oracle.attributeio.SDOAttributeIO.read(SDOAttribute
IO.java:98)
        at org.geotools.data.jdbc.QueryData.read(QueryData.java:183)
        at org.geotools.data.jdbc.JDBCFeatureReader.readFeature(JDBCFeatureReade
r.java:106)
        at org.geotools.data.jdbc.JDBCFeatureReader.next(JDBCFeatureReader.java:
86)
        at org.geotools.data.MaxFeatureReader.next(MaxFeatureReader.java:55)
        at org.geotools.data.DefaultFeatureResults.getBounds(DefaultFeatureResul
ts.java:200)
        at org.geotools.gml.producer.FeatureTransformer$FeatureTranslator.encode
(FeatureTransformer.java:388)
        at org.geotools.xml.transform.TransformerBase$XMLReaderSupport.parse(Tra
nsformerBase.java:603)
        at org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:463)
        at org.geotools.xml.transform.TransformerBase$Task.run(TransformerBase.j
ava:285)
        at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.
java:118)
        ... 25 more

Luca Morandini wrote:

Chris Holmes wrote:

In the GeoServer FeatureType editor, could you try putting in 2393,
the EPSG code, instead of the 294914 oracle srid? I think we may
actually not be using the native oracle srid stuff, and just using an
epsg database...

Chris, you're off-mark here.
If I tried to issue the Oracle SRID instead of the EPSG code, I wouldn't
be even able to create a feature type using the Geoserver management
console; hence, the cause for the afore mentioned message should be
sought somewhere else.

Apologies, should have read the thread more closely. It actually looks
like he already tried that...

> I can feed manually the SRS value 2393 as well as a bounding box but
> it does not help me very much.
> If I try to use my featuretype through WFS then "getcapabilities"
> works OK and advertises the featuretype, but
> "getfeature" gives me only the following error message:

> <ServiceExceptionReport version="1.2.0"
> xsi:schemaLocation="http://www.opengis.net/ogc
> http://localhost:8080/geoserver/schemas//wfs/1.0.0/OGC-exception.xsd&quot;&gt;
> <ServiceException>
> null error:Translator error </ServiceException>
> </ServiceExceptionReport>

[Luca_Morandini2]

Rahkonen Jukka wrote:

I have had no time to work on this problem lately, despite that I created anothet datastore from my Oracle database by using "Oracle" connection instead of "Oracle (OCI)". As far as I understand the situation remained the same. I could make a new featuretype and "getcapabilities" works but "getfeature" returns me nothing an error. Geoserver works fine with shapefiles, but our native data is in Oracle so I am about jammed now.

Do you mind posting a sample of your data, so I can have a look at it ?

A shapefile with projection metadata (the prj file) would be enough to have a go for it.

Regards,

--------------------
    Luca Morandini
www.lucamorandini.it
--------------------

[Jukka_Rahkonen]

Hi Luca,

I was about to send the data for you but started to play with by myself first. I loaded the shapefile to Oracle with shp2sdo and did all the manouvres needed after that. Geoserver behaved exactly as it used to, and my new data remained unaccessible.

But then I updated the Oracle tables, both my geometry table and the ALL_SDO_GEOM_METADATA table with SRID 2393 and then everything seems to work both with Geoserver and my WFS client. I remember that Chris Holmes suggested this already couple of weeks ago, but I did not bother to test it until now.

What I find extremely inconvenient is that the data comes useless for our main applications because 2393 is the EPSG code, and not Oracle code for Finnish KKJ. But maybe there will some day exist a kind of conversion table to tie the equivalent EPSG and Oracle SRID codes together so both the Oracle and Geoserver could feel good at the same time?

Regards,

-Jukka-

________________________________

Lähettäjä: geoserver-users-admin@lists.sourceforge.net puolesta: Luca Morandini
Lähetetty: ke 15.3.2006 19:10
Vastaanottaja: geoserver-users@lists.sourceforge.net
Aihe: [Geoserver-users] Re: Problem with Oracle 9i FeatureType

Rahkonen Jukka wrote:

I have had no time to work on this problem lately, despite that
I created anothet datastore from my Oracle database by using
"Oracle" connection instead of "Oracle (OCI)". As far as
I understand the situation remained the same. I could
make a new featuretype and "getcapabilities" works but
"getfeature" returns me nothing an error. Geoserver works
fine with shapefiles, but our native data is in
Oracle so I am about jammed now.

Do you mind posting a sample of your data, so I can have a look at it ?

A shapefile with projection metadata (the prj file) would be enough to
have a go for it.

Regards,

--------------------
    Luca Morandini
www.lucamorandini.it
--------------------

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Luca_Morandini2]

Rahkonen Jukka wrote:

Hi Luca,

I was about to send the data for you but started to play with by
myself first. I loaded the shapefile to Oracle with shp2sdo and did
all the manouvres needed after that. Geoserver behaved exactly as it
used to, and my new data remained unaccessible.

But then I updated the Oracle tables, both my geometry table and the
ALL_SDO_GEOM_METADATA table with SRID 2393 and then everything seems
to work both with Geoserver and my WFS client.

Does it work ? SRID 2393 doesn't even exist in CS_SRS.

By the way, I left my data in the proper Oracle SRID and told Geoserver to use the EPSG code instead, and this "double-code" arrangment it is working smoothly.

Therefore, I presume your problem may not lay in the use of a SRID code different from the EPSG one: could you investigate further into this ?

Regards,

--------------------
    Luca Morandini
www.lucamorandini.it
--------------------

[Jukka_Rahkonen]

-----Original Message-----
From: geoserver-users-admin@lists.sourceforge.net on behalf of Luca Morandini

Does it work ? SRID 2393 doesn't even exist in CS_SRS.

Do you mean Oracle or Geoserver? Actually it seems to be so that our production system does not use Oracle SRID at all. It does not care whatever value there is for SRID and itself it lets it be null. So I think that updating it to 2393 does not ruin anything. I hope I remember the code right from my head because I do not have any documents available just now, but anyway I mean the valid EPSG code for the Finnish KKJ. That was the one I inserted into the data I loaded to Oracle with shp2sdo. My Geoserver understood it correctly and I was able to use those data with deeJUMP client through Geoserver WFS, so quite a lot is in a promising phase. However, I could not update the data in Oracle, but there might be other issues to make WFS-T to work with my combination.

Next step I would like to take is to get my native data available through Geoserver WFS. I was not lucky with it yesterday even I think I did all the same tricks I did with the shp2sdo data. I am going to start from the beginning next week and make a more controlled test by loading new data to Oracle with shp2sdo and so on. I will report about my experience later.

Changing to 10g is an alternative for me, the production will remain in 9i for more than a year at least.

-Jukka-

By the way, I left my data in the proper Oracle SRID and told Geoserver
to use the EPSG code instead, and this "double-code" arrangment it is
working smoothly.

Therefore, I presume your problem may not lay in the use of a SRID code
different from the EPSG one: could you investigate further into this ?

[Luca_Morandini2]

Rahkonen Jukka wrote:

-----Original Message----- From:
geoserver-users-admin@lists.sourceforge.net on behalf of Luca
Morandini

Does it work ? SRID 2393 doesn't even exist in CS_SRS.

Do you mean Oracle or Geoserver?

Oracle, of course (CS_SRS is an Oracle table).

Actually it seems to be so that our
production system does not use Oracle SRID at all. It does not care
whatever value there is for SRID and itself it lets it be null. So I
think that updating it to 2393 does not ruin anything.

Hmmm... don't know Oracle Spatial so well as to point out possible errors due to putting an EPSG code as SRID... but I fear anomalies there will be.

Changing to 10g is an alternative for me, the production will remain
in 9i for more than a year at least.

This is a pity.

Regards,

--------------------
    Luca Morandini
www.lucamorandini.it
--------------------