Issues addressed with Service Pack 1

Issues addressed with ArcSDE 9.3.1 Service Pack 2:

Administration

• NIM042600 - Command line utilities “sde2shp” cannot encode some Japanese character correctly and resulting error “attribute column does not exist Skip”.
• NIM046720 - Ensure the option to skip the calculation of sdo_geometry layer's MBR when registering it with ArcSDE (if the user already knows the correct MBR - using "-E") is actually used.
• NIM037345 - Cannot alter the grid size of a layer using sdelayer -o alter. Error: Grid Size: nnnnn, must be less than maximum nnnnn.

DB2 and Informix Specific

• NIM054998 - <DB2> The version queries against the SDE XML data model are returning wrong results .
• NIM035936 - <DB2> Improve the implementation for creating new layers.
• NIM043936 - Change Privileges tool can grant privileges to a DB2 user group, but cannot revoke the permissions from the group (only DELETE permission is revoked); "sdelayer -o revoke" returns the wrong error messages.
• NIM045098 - User is not inheriting permissions granted to the domain group of which it is a member; consequently, the user is unable to view data to which the group has been granted select privilege.
• NIM049083 - Contents of a BLOB column is truncated during versioned editing when the BLOB size is greater than 60000 bytes.
• NIM050575 - Enabling archiving before adding GlobalIDs causes incorrect GlobalID to be stored with the archived object.
• NIM052718 - <DB2> Executing the DB2 SDE.NEXT_ROW_ID routine in a federated database environment with DB2_TWO_PHASE_COMMIT set to Y leads to errors because of the COMMIT statements in the SDE.SDE_GET_ROWIDS routine.
• NIM054775 - <DB2> SE_stream_delete_by_id_list fails with -51 error when trying to delete rows from a versioned table with SDE_XML storage type.
• NIM054776 - <DB2> Copy/paste of point data may result in SDE Error(-139) The specified coordinate exceeds the valid coordinate range on AIX 64 Bit platform.
• NIM054803 - The version queries against the SDE XML data model are returning wrong results.
• NIM055063 - Enable archiving crashes the gsrvr if a xml column exists in a layer.
• NIM056155 - <DB2> If a local user account name does not exist on client machine too, direct connect using an account name local to the database server will fail and a misleading error message relating to a table "GDB_RELEASE" will appear.
• NIM056494 - <DB2> Error ‘The specified coordinate exceeds the valid coordinate range’ occurs when using a z-aware/enabled envelope to get an update cursor on a FC.

Non-Database Specific Server

• NIM042008- Attempting to update a set of objects where the user's schema does not have the ability to create the sde logfile tables will cause the ArcSDE gsrvr process to crash. Please see technical article 36168 for more information.
• NIM044174 - The number of system handles associated with the giomgr.exe keeps increasing after closing the ArcSDE Connection.
• NIM044821 - SDE Java and C API's fail to make new direct connect after 267 connections opened (and closed) on Linux.
• NIM047243 - When syncing updates, the queries to find the features to update using the globalid is slow when the feature class has many features.
• NIM048382 - When 32bit ArcGIS client and 64bit ArcSDE server run on the same 64bit server machine, 3-tier connection does not work between the 32bit client and 64bit server.
• NIM048298 - Add new Denmark DKTM Zones 1-4 projected coordinate systems.
• NIM051129 - The error message java.lang.NullPointerException is returned when using the PeCSTransformations.geog1ToGeog2 method with grid-based transformation methods such as HARN, NADCON, and NTv2 methods.
• NIM051155 - PeCSTransformations.geog1ToGeog2 method does not perform the transformation for certain grid-based transformation methods such as HARN, NADCON, and NTv2 methods.
• NIM053100 - Unable to perform Direct Connect with 64-bit Java SDE SDK API's due to the absense of 'sdejavautil' component. 9.3.1 only.
• NIM053997 - asWKB gives wrong output when used against a specific simplified geometry.
• NIM052918 - Rebuild Network command fails against a geometric network where the connected user does not own all the states containing geometric network edits.
• NIM056276 - 9.3.1: Convert any occurrences of the well-known ID 3857 (WGS 1984 Web Mercator Auxiliary Sphere) to its old value, 102100.

Oracle General

• NIM049776 - Rebuilding a spatial index on an archived feature class (_H class) fails with Trigger does not exist error.
• NIM049777 - When unarchiving a feature class using Binary Storage, FIDs might need to be regenerated to remove duplicates in the archived feature class.
• NIM050318 - Field with VARCHAR2 data type from an ArcSDE child geodatabase involved in a Check-out replica is truncated and/or appended with special characters in the ArcSDE parent geodatabase set with German locale.
• NIM050335 - Archived SDE binary storage feature class is unable to display geometry of the newly added features after archiving spatial index altered.
• NIM052156 - Ora11gR2 APEX* & ORDDATA* tables need to be filtered.
• NIM052197 - Unknown column names should not be returned by ArcSDE when describing a tables indexes.
• NIM055456 - Import Message fails with Error “ORA-01460: Unimplemented unreasonable conversion requested” for an Annotation Feature Class.
• NIM056116 - TSMSYS Oracle objects are not filtered when connected to SDE and the user connected has select any table permissions.

Oracle Spatial

• NIM053444 - SDE2SHP is not excluding the SE_ANNO_CAD_DATA column when exporting SDO_Geometry layers.
• NIM053601 - When querying an SDO_GEOMETRY featureclass that uses a geodetic coordinate system, "db_sqltype_bind_columns::geodetic layer query." gets printed to the error log.

Oracle ST_Geometry

• NIM042325 - Slow performance (full table scan) when statistics present in SDE.ST_GEOMETRY_INDEX table with ST_Geometry.
• NIM045348 - ST_INTERSECTION returns no geometry when ST_SPATIAL_REFERENCES SRID are different.
• NIM046067 - MinZ and MaxZ were reset to the 'Z offset' values if the last edits on ST_Geometry features were attribute edits.
• NIM048113 - Unable to select features from an ArcSDE view using ST_GEOMETRY data that has a joined table.
• NIM048385 - ST_BUFFER function fails with "too many points" message on multipart polygon.
• NIM049191 - ST_Transform returns a "Spatial References are not compatible" error.
• NIM052027 - Spatial type for Oracle: Create index statement for the sp_id attribute on the domain index is not fully qualified with the object owner.
• NIM052748 - Using SQL statements with st_intersect results in Oracle error "ORA-01002: fetch out of sequence".
• NIM053199 - Spatial type for Oracle: Unnecessary looping impacting performance when multiple grid levels are present to delete collections during the termination of spx_util.grid_search_execute. Please see technical article 37528 for more information.
• NIM053342 - ST_Intersects returns the wrong results using the supplied client data when secondary filtering is used.
• NIM053362 - Spatial Type for Oracle: ODCIIndexStart errors caused by extproc failing under specific conditions when multipart features are present.
• NIM056640 - Spatial Type for Oracle: Provide an optimized st_geometry constructor for points which constructs the binary geometry in PL/SQL.
• NIM057155 - Spatial Type for Oracle: Creating spatial data with schema/owner names exceeding twenty plus characters will create an unusable spatial index and encounter an ‘Ora-06502: PL/SQL: numeric or value error: character string buffer too small’ error.
• NIM057453 - Spatial Type for Oracle: st_intersects returning additional rows in the result set with secondary filtering.

PostgreSQL Specific

• NIM046206 - Postgres: Slow performance using st_astext against a relatively large multipolygon features.
• NIM050575 - Enabling archiving before adding GlobalIDs causes incorrect GlobalID to be stored with the archived object.
• NIM053450 - Postgres: Unable to set version with sde.sde_set_current_version when editing multiversion views.
• NIM055461 - Postgres: Topology loaded with PG_GEOMETRY has a NULL dirtyarea which causes an application crash when the dirtyarea is retired.
• NIM055471 - Postgres: Error -112 generating shape when drawing Network Feature Dataset.
• NIM055472 - Postgres: Network I/O errors encountered when registering a feature dataset with a topology as versioned which contains more than 1 participating feature class.
• NIM055581 - Postgres: SDE.ST_Point() function failed to parse WKT text string returns 'invalid type ST_POINT'.
• NIM055582 - Postgres: Loading feature dataset into ArcSDE with PG_GEOMETRY (WKB) fails sometimes with a Network I/O error.
• NIM055583 - Postgres: Generating shape from WKB could fail with -150 "Polygon does not close properly" or -155 "Linestring or poly boundary is self-intersecting" error.
• NIM056156 - Postgres: Spatial queries will return incorrect results in various cases.

SQL Server Specific

• NIM043948 - After upgrading a 9.3 Geodatabase from SQL2000 to SQL2005, editing a child version fails with Network I/O error.
• NIM050335 - Archived SDE binary storage feature class is unable to display geometry of the newly added features after archiving spatial index altered.
• NIM050575 - Enabling archiving before adding GlobalIDs causes incorrect GlobalID to be stored with the archived object.
• NIM052174 - Search cursors with spatial filters that include raster columns are failing with an SE_FUNCTION_SEQUENCE_ERROR -113 function called out of sequence in the load_buffer function for SQLServer.
• NIM056641 - sdelayer -o delete is setting spatial column to NULL for Geography layers.




Issues addressed with Service Pack 1

Administration

• NIM031560 - Enhance the sderaster command line tool to update the unicode SE_NSTRING_TYPE name column of a raster catalog created by ArcCatalog.
• NIM036745 - From Japanese Linux, ArcSDE 9.2/9.3 command utility - SDEIMPORT fails to import layers from a SDEEXPORT 9.1 file.
• NIM041346 - Impoting an sdeexport file with -X option in RedHat OS encounters an error:
  
  *** glibc detected *** double free or corruption (!prev): 0x09af1df0 *** Abort
• NIM045468 - From Japanese Linux with locale JA16SJIS. ArcSDE sdeimport command fails to import layer from 9.1 exported sdx file.

DB2 and Informix Specific

• NIM047885 - implement a next_row_id stored procedure.

Non-Database Specific Server

• NIM009659 - Oracle based features stored in feature datasets are not accessible with ArcEngine using direct connect.
• NIM038155 - Migrating a feature class, raster dataset or a raster catalog is not touching the sde_tables_modified table for the layers and raster_columns entry when completing.
• NIM039217 - Editing an archive enabled table with SQL through a multi-versioned view in the DEFAULT version will not maintain the table's archive. (Please see technical article 35645 for more details.)
• NIM045628 - ArcGIS editor stop editing/save operations can encounter database deadlocking situations if two users are saving and have modified the same versioned objectclass.
• NIM046632 - Multi-threaded calls to save_to_base() function is causing the gsrvr to crash.
• NIM047399 - The British National Grid scale factor was changed in version 9.2. While the software now considers both values equivalent, the check to determine that is inefficient. This change improves performance.
• NIM047452 - Java ADF cannot project horizon to WGS84 (4326).
• NIM047565 - Improve performance of opening ArcGIS map documents that contain multiple data sources which cannot be accessed due to certain connection errors.
• NIM047569 - Improve connection time for map documents with connections to a SQL Server Express geodatabase that is shut down by mapping the returned error code to SE_LOST_DBMS_CONNECTION.
• NIM049434 - Java Projection Engine: Retrieving the projection horizon for Mercator Auxiliary Sphere, Hotine, RSO, Gall's Stereographic, Behrmann, or Two Point Equidistant will crash the application.
• NIM049535 - ArcGIS Build Pyramid tool returns Invalid Column Value when building a pyramid against raster data that is JPEG or JPEG 2000 compressed.
• NIM049777 - When unarchiving a feature class using Binary Storage, FIDs might need to be regenerated to remove duplicates in the archived feature class.

Oracle General

• NIM039168 - Oracle Spatial: DB IO error encountered when validating a topology on an 11g DB
• NIM042121 - Warning messages related to 'S_delete_logfile_data_table_by_id() USER Transaction Logfile Delete...' should not be printed to the sde error log.
• NIM043097 - Compressing a geodatabase can lead to blocking conditions in ArcGIS which impact editor user response time. (Please see technical article 36371 for more details.)
• NIM043170 - Optimize queries used by trim against a versioned table's deletes table to reduce i/o and improve performance.
• NIM044630 - Enable Archiving on a topology class failing when archiving class index is built on Oracle Geodatabase.
• NIM044659 - Importing the data changes into replica database in a Disconnected environment fails with "ORA-14452: attempt to create, alter or drop an index on temporary table already in use”
• NIM046549 - Error message '[Fri Jan 23 15:31:42 2009] [12] [mj] db_fetch_attr_row Error - 0 0' should only show up in the sde error log when SDEVERBOSE is set.
• NIM049743 - Gsrvr crash occurs for certain queries where ArcSDE requires additional internal described columns in order to retrieve results.

Oracle Spatial

• NIM043243 - When creating an Oracle Spatial layer using the SDO_SRID parameter, the Oracle Spatial spatial reference WKT is stored. We should be storing the ESRI version.
• NIM045165 - SDO_Geometry objects comprising of only curved segments can no longer be index at Oracle 11.1.0.7 when stored using a multipart triplet.
• NIM046899 - With SDO_SRID paraeters set, invalid metadata is inserted into SDO metadata views.
• NIM047917 - When a SDO_Geometry table is registered to SDE, the A and D table get dupicates of the USER_SDO_GEOM_METADATA row, but the history table does not.
• NIM049887 - When using Oracle 11g, spatial queries against three dimensional feature classes do not return any results.
• NIM049959 - SDE has to insert the L value in the SDO_Geoemtry GTYPE (DLTT), setting it to 0 is not longer enough at 11g.

Oracle ST_Geometry

• NIM034655 - Spatial Type for Oracle: Provide optimized secondary filtering when performing relational operators.
• NIM042228 - Spatial type for Oracle: Disassociate the st_contains operator from the domain index st_spatial_index. (Please see technical article 36195 for more details.)
• NIM042709 - Edits on ST_GEOMETRY produces shape area (shape.area) and shape length (shape.len) field with 0 values if “move edits to base” option is selected to register the feature class as versioned.
• NIM042753 - Add support for SE_ROW_ID column for ST_GEOMETRY type to ensure user’s existing applications can continue to work after migrating from SDEBINARY/SDELOB to ST_GEOMETRY.
• NIM042754 - In Oracle, when performing a migrate to ST_GEOMETRY on a MIXED precision feature class, the feature class remains set to MIXED precision when it should be updated to HIGH. (Please see technical article 36254 for more details.)
• NIM045282 - ArcIMS Spatial query on a versioned featureclass stored as ST_GEOMETRY fails with -51 error (returns error: com.esri.sde.sdk.client.SeException) and does not draw when there is only one state (state zero) in the ArcSDE geodatabase.
• NIM046027 - Identify returns "Nothing found" against features in a spatial view based upon ST_GEOMETRY point feature class.
• NIM046968 - Spatial type for Oracle: ArcGIS should not be explicitly granting privileges on the domain index object. (Please see technical article 37104 for more details.)
• NIM047268 - Unable to view / use geometries when the shape column is ST_GEOMETRY and accessed through a view that uses column aliases and is joined to another table. The exact same workflow works when using SDEBINARY data.
• NIM047285 - Ora-0923 error when attempting to select or identify with an st_geometry point featureclass.
• NIM047307 - Spatial type for Oracle: Objects registered as versioned with the move edits to base option can encounter data inconsistencies if two users edit the same object. (Please see technical article 37102 for more details.)
• NIM047400 - When making a direct connection to a schema (project) gdb using ST_Geometry an error is returned when trying to access the ST_ functions from the project instance.
• NIM047564 - Spatial type for Oracle: Using Oracle datapump with the remap_schema option creates invalid entries in the sde.st_geometry_columns table. (Please see technical article 37103 for more details.)
• NIM048154 - Spatial Type for Oracle: Prevent the migration of layers to st_geometry if they have dependent views.
• NIM049372 - If the operating system is a French or German version of Windows, copy/paste point feature class from file geodatabase to ArcSDE 9.3SP1/9.3.1 with defaults dbtune keyword (ST_GEOMETRY) fails with an error message about creating spatial index.

PostgreSQL Specific

• NIM039417 - Postgres: When loading a multipart polygon shapefile into a PostgreSQL geodatabase as PG_GEOMETRY storage type, using the shp2sde command, all features are not visible.
• NIM045676 - IQueryDef.Evaluate() fails with error, "Invalid parameter value passed to function when joining on two tables.
• NIM047566 - The z-value envelope information is missing in the sde.sde_layers table.

SQL Server Specific

• NIM039409 - When attempting to delete a user defined attribute from a versioned object,the following error message is returned: 'Explicit drop index not allowed on A table index'.
• NIM042206 - Error when saving edits on an Archived Featureclass when using Direct Connect.
• NIM043072 - Inserting a feature with out of bounds geometry changes the feature class extent.
• NIM043242 - When applying a select by attribute query on a FeatureClass with geometry spatial type, it fails with a network i/o error.
• NIM045639 - SQL Server 2000: Users who are members of database or server roles like sysadmin or db_datareader cannot see data that they do not own.
• NIM045726 - Improve performance of spatial queries with definition queries / attribute filters.
• NIM046752 - When creating multiversioned view for feature class with nvarchar(n), n is doubled to 2n thus limiting the maximum nvarchar field length to 2000 if it needs to be incorporated in a multiversioned view.
• NIM047207 - Compress fails with primary key violation on SDE_Geometry CAD side table when duplicate cad element is updated to state_id 0.
• NIM049776 - Rebuilding a spatial index on an archived feature class (_H class) fails with Trigger does not exist error.