[Gvsig_english] Issues with Oracle Expatial export

[Diego Guidi]

I'm experiencing a strange issue with layer export from a shapefile to
a Oracle Spatial DB.
When open gvSIG, I launch a export from a shapefile to oracle spatial,
all works OK and I could show correctly the data
If I launch a second export from a different shapefile to oracle
spatial, when I try to open the data, the data generated is corrupted
and the console shows a log message:
ERROR Thread-62
es.prodevelop.cit.gvsig.fmap.drivers.jdbc.oracle.OracleSpatialDriver -
Tablename: SCOTT.ST01TE01CL14PTS. Error while getting main cursor:
ORA-29902: errore durante l'esecuzione della routine ODCIIndexStart()
ORA-13033: Dati non validi nell'oggetto SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY
ORA-06512: a "MDSYS.SDO_INDEX_METHOD_10I", line 286

java.sql.SQLException: ORA-29902: errore durante l'esecuzione della
routine ODCIIndexStart()
ORA-13033: Dati non validi nell'oggetto SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY
ORA-06512: a "MDSYS.SDO_INDEX_METHOD_10I", line 286

	at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
	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.T4CStatement.doOall8(T4CStatement.java:207)
	at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:790)
	at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1031)
	at oracle.jdbc.driver.T4CStatement.executeMaybeDescribe(T4CStatement.java:830)
	at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1124)
	at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1264)
	at es.prodevelop.cit.gvsig.fmap.drivers.jdbc.oracle.OracleSpatialDriver.getViewResultSet(Unknown
Source)
	at es.prodevelop.cit.gvsig.fmap.drivers.jdbc.oracle.OracleSpatialDriver.getFeatureIterator(Unknown
Source)
	at es.prodevelop.cit.gvsig.fmap.drivers.jdbc.oracle.OracleSpatialDriver.getFeatureIterator(Unknown
Source)
	at com.iver.cit.gvsig.fmap.layers.VectorialDBAdapter.getFeatureIterator(Unknown
Source)
	at com.iver.cit.gvsig.fmap.operations.strategies.DBStrategy.draw(Unknown
Source)
	at com.iver.cit.gvsig.fmap.layers.FLyrVect.draw(Unknown Source)
	at com.iver.cit.gvsig.fmap.layers.FLayers.draw(Unknown Source)
	at com.iver.cit.gvsig.fmap.layers.FLayers.draw(Unknown Source)
	at com.iver.cit.gvsig.fmap.MapContext.draw(Unknown Source)
	at com.iver.cit.gvsig.fmap.MapControl$PaintingRequest.paint(Unknown Source)
	at com.iver.cit.gvsig.fmap.MapControl$Drawer2$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)


The best way to do this kind of operations correctly is to stop and
restart gvSIG after any export to Oracle Spatial.

This kind of behavior happens every time I launch a second export, and
looks not related to the data in the shapefile 8from 1 mega to 200
mega).
All shapefiles I'm using are with Z and M, and the generated
SDO_GEMOETRIES are 3D geoms.


-- 
Diego Guidi