English

Bug: Encountering an underlying DBMS error when using the sdeexport command with the -O option and st_geometry tables

Description

When using the 'sdeexport' command with the -O option when the layer is using st_geometry in Oracle, the following underlying DBMS error is encountered:

Code:
sdeexport -o create -l cntry,shape -O -f cntry_exp -u gdb -p gdb -s laurel -i esri_gdb

ArcSDE 9.3 for Oracle10g Build 440 Sun Jan 6 12:00:15 2008
SDEX File Export Administration Utility
-----------------------------------------------------
Exporting ArcSDE object to "cntry_exp" in SDEX export format ...
Exporting table "cntry".
Spatial column "SHAPE"
SDE Code (-51)= Underlying DBMS error
Extended DBMS error code: 904
ORA-00904: "S_"."GY": invalid identifier
SELECT CNTRY.SHAPE.area, NAME, ABBREVNAME, FIPS_CODE, WB_CNTRY, 1 SHAPE, OBJECTID, CNTRY.SHAPE.points,CNTRY.SHAPE.numpts,CNTRY.SHAPE.entity,CNTRY.SHAPE.minx,CNTRY.SHAPE.miny,CNTRY.SHAPE.maxx,CNTRY.SHAPE.maxy,CNTRY.rowid
FROM GDB.CNTRY CNTRY WHERE ST_EnvIntersects(CNTRY.SHAPE,:1,:2,:3,:4) = 1 AND s_.rn =1
order by s_.gx, s_.gy
Error in stream fetch.
SDE Code (-1): Operation Failed
Error in exporting SDE feature/attribute data.

Error exporting SDE export file.
sdeexport error.
1 features converted.
0 features exported.


Cause

There is an invalid binding specification within the 'sdeexport' command; therefore the SQL statement cannot fetch the data in the order of the spatial index, which results in the underlying DBMS error.

Workaround

To avoid the error and work around the problem, do not specify the -O option when executing the command. The features will be successfully exported, but will not be exported in the order of the spatial index.