A exception like :
"199287 [serious] org.geotools.data.oracle.attributeio.SDOAttributeIO - SQL Exceptio
n reading geometry column
199288 [serious] org.geotools.renderer.lite.StreamingRenderer$DefaultRenderListener
taixingjason ha scritto:
A exception like : "199287 [serious] org.geotools.data.oracle.attributeio.SDOAttributeIO - SQL Exceptio
n reading geometry column
199288 [serious] org.geotools.renderer.lite.StreamingRenderer$DefaultRenderListener
- SQL Exception reading geometry column"
occured when I was using geoserver1.3.2. Please help me.
Ouch... Geoserver 1.3.2 is old, end of life, not supported anymore.
Plus, Oracle data store is not maintained, so probably nobody is going
to try and fix this issue.
Anyways, I have some suggestions:
* always include a full stack trace in your reports (now, I don't know
if Geoserver 1.3.2 did include them, but 1.4.1 should, at least if you
specify a FINE logging level)
* try out Geoserver 1.4.1, it has some fixes compared to 1.3.2 that may
help, and should be able to open old 1.3.x data directories
* try out Geoserver 1.5.0rc2 when it comes out, it has another critical
fix related to CRS management
Finally, we're looking for someone sponsoring Oracle datastore fixes, either by providing some funding, or some programming time. If you depend on Oracle it may be wise to consider that.
Cheers
Andrea