Opened 19 years ago
Closed 14 years ago
#659 closed defect (fixed)
Oracle Loading DIM=2 with 3D geometries.
Reported by: | warmerdam | Owned by: | ilucena |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | OGR_SF | Version: | unspecified |
Severity: | normal | Keywords: | oracle oci |
Cc: |
Description (last modified by )
1 2 3 4 5 6 7 8 9 10 11 12 red@seitzr > ogr2ogr.exe -f OCI OCI:userid/passwd@englink_staging -nln usbr_dams -lco OVERWRITE=YES -lco DIM=2 -lco SRID=8307 damsgeo.shp ERROR 1: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine ORA-13249: internal error in Spatial index: [mdidxrbd] ORA-13249: Error in Spatial index: index build failed ORA-13249: Error in spatial index: [mdrcrtxfergm] ORA-13249: Error in spatial index: [mdpridxtxfergm] ORA-13200: internal error [ROWID:AAAPjuAAeAABNKiAAA] in spatial indexing. ORA-13206: internal error [] while creating the spatial index ORA-13364: Layer Dimensionality does not match geometry dimensions ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 7 ORA-06512: at line 1 in CREATE INDEX "USBR_DAMS_IDX" ON USBR_DAMS("ORA_GEOMETRY") INDEXTYPE IS MDSYS.SPATIAL_INDEX The problem seems to be that the layer type is forced to 2D by the DIM=2, but 3D geometries are still produced.
Change History (6)
comment:2 by , 16 years ago
Keywords: | oracle oci added |
---|
comment:3 by , 16 years ago
Frank,
Should I append this ticket to my Oracle queue and reassign to myself?
comment:4 by , 15 years ago
Hello,
I think you should consider the code I sumit with the problem #1960. It will probably also resolve this problem.
Nicolas
comment:5 by , 14 years ago
Description: | modified (diff) |
---|---|
Owner: | changed from | to
Status: | assigned → new |
comment:6 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
That was fixed on ticket #1960.
Note:
See TracTickets
for help on using tickets.