ArcGIS 8.1 Service Pack 1 Resolved Issues |
ArcGIS 8.1 Service Pack 1 is an update for existing ArcGIS 8.1 users. Service Pack 1 addresses a number of issues, outlined below, that have been discovered since 8.1 was released, and adds limited new functionality.
Some of the highlights of Service Pack 1 include:
If a user does not have write permission to the index file and tries to create a geocoding service on the same shapefile that uses the same reference data fields as the existing geocoding service, an error occurs indicating that the geocoding index file cannot be accessed.
ESRI Internal Tracking Number: CQ00143759
Coverages containing tolerance values that are not stored in scientific notation will display incorrect values in the Coverage Tolerance property page. For example, a fuzzy tolerance of 29 will be displayed as 0.000000002, in ArcInfo Workstation; the tolerance may read as 29.96.
ESRI Internal Tracking Number: CQ00142321
On copy/paste of a geometric network, the connectivity may become corrupt. This will produce the error "The feature could not be moved" or "The requested feature could not be located". There are also cases where pasting large networks may crash ArcCatalog.
Knowledge Base Article: 18876
ESRI Internal Tracking Number: CQ00142694
ESRI Internal Tracking Number: CQ00140896
After changing the type of an existing domain, on Apply or OK ArcCatalog produces a fatal error.
ESRI Internal Tracking Number: CQ00141948
Knowledge Base Articles: 19845
In some DXF files multi-byte annotation displays incorrectly in ArcCatalog preview and in ArcMap.
ESRI Internal Tracking Number: CQ00141839
When building UML diagrams with Visio, the configuration key words are not being read correctly and the resultant feature class is missing the key words.
ESRI Internal Tracking Number: CQ00143343
Knowledge Base Articles: 19191
OLE DB connections to RDBMS data sources are not correctly returning column indexes. This could result in slow performance for certain operations. ESRI Internal Tracking Number: CQ00143366
Knowledge Base Article: 19193
When reconciling versioned data, certain weight values and attributes may get out of sync with the correct data.
ESRI Internal Tracking Number: CQ00143662
Knowledge Base Articles: 19381
When you copy and paste data between GDBs, the relationship rules are not being copied correctly. This causes incorrect validation in some cases in the resultant database.
ESRI Internal Tracking Number: CQ00144561
Knowledge Base Articles: 19840
In some complex geometric networks, when the feature dataset is copied and pasted into another geodatabase, the application will produce a fatal error.
ESRI Internal Tracking Number: CQ00142694
Knowledge Base Articles: 18876
A nondescript error is reported when building a geometric network, which is assigned to a tablespace that is too small for the network.
ESRI Internal Tracking Number: CQ00141838
Knowledge Base Article: 19036
A network in a personal geodatabase has a weight, which has been assigned, to the Shape_length field on an Edge feature class. On Copy/Paste to ArcSDE, the Edge feature class with the weight cannot be edited. The weight association has not been updated from Shape_length (personal geodatabase) to SHAPE.LEN (ArcSDE).
ESRI Internal Tracking Number: CQ00144237
Knowledge Base Article: 19557
Added a method of reconcile that does not acquire an exclusive lock on the version.
ESRI Internal Tracking Number: CQ00143563
If you convert a point shapefile to a point-Z shapefile using the feature data converter, the application will produce a fatal error.
ESRI Internal Tracking Number: CQ00142153
Knowledge Base Articles: 19403
Raster layer drawing performance within ArcGIS is may seem very slow. Many of these problems are now addressed, specifically RGB and Grayscale raster display. Psuedocolored and 1 bit Raster display performance have not been addressed at this time.
ESRI Internal Tracking Number: CQ00142879
Knowledge Base Article: 19839
>If you create very small buffer areas from points stored in ArcSDE you may get an error and the buffer process will not work.
ESRI Internal Tracking Number: CQ00143253
ArcMap will not import ArcView 3.x projects that contain empty viewframes. In some instances ArcMap may also crash when you choose such a project in Import from the ArcView 3.2 Project dialog.
ESRI Internal Tracking Number: CQ00143059
If the data frame is set to use a projected coordinate system, the clip to shape option allows units to be specified in decimal degrees. The default values for this extent are invalid and if accepted, ArcMap will appear to hang.
ESRI Internal Tracking Number: CQ00143980
Knowledge Base Article: 19425
Adobe illustrator export format has been added to the graphic export options in ArcMap.
Closing the Overview window will cause ArcMap to produce a fatal error. This happens when a raster layer is chosen as the reference layer.
ESRI Internal Tracking Number: CQ00143976
If an IMS map services sub-layers changes, ArcMap will not refresh the layers the next time the map document is opened.
ESRI Internal Tracking Number: CQ00142872
Long field names can be unreadable on the symbology dialogs and property pages.
ESRI Internal Tracking Number: CQ00115304
When a Spatial Bookmark is made from a found feature in the Find dialog, ArcMap produces a fatal Runtime error.
ESRI Internal Tracking Number: CQ00142977
A fatal error is produced if you attempt to dissolve a layer that has NULL shapes or NULL field values from a table join.
ESRI Internal Tracking Number: CQ00141730
If a CAD layer is added, then removed and edited in a CAD package, then read again in ArcMap; the edit changes do not show up. The CAD file is cached and not refreshed.
ESRI Internal Tracking Number: CQ00144118
When editing a curve feature the curve may appear slightly displaced from its actual endpoints and position.
ESRI Internal Tracking Number: CQ00119302
Knowledge Base Article: 18842
If large numbers of feature classes are integrated while using the Editor, the memory usage of ArcMap will continue to increase and will not be released when the process completes.
ESRI Internal Tracking Number: CQ00142464
Knowledge Base Article: 19064
ArcMap may not allow edits to be saved and may crash when editing data that has many vertexes (over 500 per shape). In some cases M values are set on non-M aware features causing a fatal error.
ESRI Internal Tracking Number: CQ00119041
Knowledge Base Article: 19136
If point features without Z values are copied into a feature class that has Z values, ArcMap will produce a fatal error and any edits will be lost.
ESRI Internal Tracking Number: CQ00144017
Knowledge Base Article: 19483
A fatal error is produced if the split command is used on a complex edge in a geodatabase and then the feature class node is selected in the property inspector.
ESRI Internal Tracking Number: CQ00144191
Knowledge Base Article: 19523
If the divide command is used on a multiple simple edge features in a geodatabase and the feature class in the attribute editor is selected, a fatal error will occur.
ESRI Internal Tracking Number: CQ00142686
Knowledge Base Article: 19063
When merging many multipart features into a single multi-part feature with the attribute table open, produces the wrong results.
ESRI Internal Tracking Number: CQ00142261
Knowledge Base Article: 19158
If you select a part of a multipart feature in the Edit Sketch Properties dialog box after editing the vertex of a previous part, a fatal error will occur.
ESRI Internal Tracking Number: CQ00142556
Knowledge Base Article: 19098
When edits are made and there is a raster dataset visible in the display, the entire display will refresh rather than just the expected area around the edit.
ESRI Internal Tracking Number: CQ00143579
Knowledge Base Article: 19485
The editing tools in some cases allow NULL shapes to be inserted in an edit session.
ESRI Internal Tracking Number: CQ00142963
Knowledge Base Article: 19813
When using the trace tool while editing in ArcMap, the memory usage dramatically increases when tracing on a densified curve. This memory is not released when the task is complete and may cause a fatal error in ArcMap.
ESRI Internal Tracking Number: CQ00143301
Knowledge Base Article: 19162
If a multi-point feature is repeatedly cut and pasted within an edit session, ArcMap will eventually become unstable and produce a fatal error.
ESRI Internal Tracking Number: CQ00144100
Knowledge Base Article: 19517
In some editing scenarios, the sketch version of an elliptic arc changes position when the arc is finished.
ESRI Internal Tracking Number: CQ00142810
Knowledge Base Article: 19473
When a polygon is intersected with a polyline, the resultant polyline's direction may be altered left-to-right.
ESRI Internal Tracking Number: CQ00141950
Knowledge Base Article: 19494
In ArcObjects if ITopologicalOperator::Intersect is called and the line passed in to it is null, ArcMap will produce a fatal error.
ESRI Internal Tracking Number: CQ00140825
Knowledge Base Article: 18817
If the geometry constructor in ArcObjects is passed the VB keyword NOTHING, it will cause a fatal error in ArcMap.
ESRI Internal Tracking Number: CQ00141105
Knowledge Base Article: 19320
The unprojecting of data or datum transformations may cause data near the horizons to not display in ArcMap.
ESRI Internal Tracking Number: CQ00143349
Knowledge Base Article: 19188
Graphical interaction with ellipses may produce inconsistent results.
ESRI Internal Tracking Number: CQ00144226
Knowledge Base Article: 19668
IGeometry::GeoNormalizeFromLongitude can only be used on geometry with a spatial reference which is a geographic or projected coordinate system. If used on an unknown spatial reference, the application appears to hang.
ESRI Internal Tracking Number: CQ00143778
In ArcObjects, using the ConstructBearingRadiusAngle command with values of 360 degrees, may fail and produce incorrect results.
ESRI Internal Tracking Number: CQ00143615
Knowledge Base Article: 19289
Using US Streets with Zone address style, users selected City Names for the left and right zone field. If the address contains a city name with more than one word, geocoding fails. It works fine if the zone field is a 5 digit ZIP.
ESRI Internal Tracking Number: CQ00144265
If you cocreate a FindAddresses object, ArcMap will produce a fatal error.
ESRI Internal Tracking Number: CQ00143673
Knowledge Base Article: 19369
The address has a null Address field value. After matching the table it is in, the record is unmatched, but has a score and a point. The point is the same as the point for the record above it in the table.
ESRI Internal Tracking Number: CQ00141922
Knowledge Base Article: 19401
Find Route Locations does not work on ArcSDE data when the route key field is a character type. It is not possible to find route locations on this data.
ESRI Internal Tracking Number: CQ00142207
Knowledge Base Article: 18998
If the route event source in ArcMap is of a different version then the source feature class, ArcMap will produce a fatal error when you attempt to edit it.
ESRI Internal Tracking Number: CQ00141088
Knowledge Base Article: 18999
Route event layers do not honor the setting in ArcMap's options whether to be visible when added or not.
ESRI Internal Tracking Number: CQ00138917
Knowledge Base Article: 18529
When splined annotation is converted from ArcInfo coverage annotation to geodatabase annotation, it does not spline exactly as coverage annotation does.
ESRI Internal Tracking Number: CQ00143208
Knowledge Base Article: 19352
Some ArcInfo splined coverage annotation draws shifted from where they should draw.
ESRI Internal Tracking Number: CQ00140545
Knowledge Base Article: 18090
If using the decimal number separator (1.234, 00 verses 1,234.00), it will not be possible to display the flow direction on networks.
Knowledge Base Article: 18650
ESRI Internal Tracking Number: CQ00142538
Datum transformation may not work correctly when the transformation is from one geographic coordinate system to another. The result is the transformation is not applied and the data appears shifted.
ESRI Internal Tracking Number: CQ00140957
Knowledge Base Article: 19169
When unprojecting data or performing a geographic (datum) transformation, data greater than +180 disappears (i.e., if central meridian is 100, data between -180 and -80).
ESRI Internal Tracking Number: CQ00143665
Knowledge Base Article: 19328
Long lines near the poles can disappear after an unprojection. This occurs with map projections where the pole is a point or a line that is much shorter than the equator. Examples are Sinusoidal and Robinson.
ESRI Internal Tracking Number: CQ00143664
Knowledge Base Article: 19326
If the map has a datum transformation when data from a different datum is edited, the data is placed in the wrong location.
ESRI Internal Tracking Number: CQ00141823
Knowledge Base Article: 19105
Depending on the data, some data of Antarctica causes ArcMap to have a fatal error when drawing the data. Other data may draw correctly or may not draw Antarctica.
ESRI Internal Tracking Number: CQ00144396
Knowledge Base Article: 19597
If you create a custom geographic (datum) transformation for two geographic coordinate systems that use different units, all of the data may not display.
ESRI Internal Tracking Number: CQ00141550
Knowledge Base Article: 19106
Using the Behrmann projection may cause some data not to display in ArcMap.
ESRI Internal Tracking Number: CQ00139190
Knowledge Base Article: 17399
The following map projections were added:
Aitoff
Craster Parabolic
Flat Polar Quartic
Gnomonic
Hammer-Aitof
Orthographic
Times
Vertical Near-side Perspective
Winkel Tripel
ESRI Internal Tracking Number: CQ00142547
Knowledge Base Article: 19810
Selections, Tables, and Table Joins
If an attribute query on ArcSDE for Coverage data includes multiple spaces, no data is returned, for instance [name] = "Test" will not work but [name] = "Test" will.
ESRI Internal Tracking Number: CQ00142165
Knowledge Base Article: 18629
When spatially joining a layer based on an event source to another layer, and the event table does not have object ids, ArcMap will crash. This applies to both xy event sources and route event sources.
ESRI Internal Tracking Number: CQ00140879
Knowledge Base Article: 19519
If a layer, which has a joined table, also has some fields not visible (in the field properties tab), an error is produced when the data is exported and no data is exported.
ESRI Internal Tracking Number: CQ00141638
Knowledge Base Article: 18961
If a table is composed of multiple tables across databases (i.e. a DBF table joined to a geodatabase), the Find and Replace dialogs will produce an error when they are used with this data.
ESRI Internal Tracking Number: CQ00141030
Knowledge Base Article: 19673
When data is joined together, the queries may return all records when only a subset of records should be selected. This seems to happen only for certain queries that involve fields from more than one table in the join.
ESRI Internal Tracking Number: CQ00141023
Knowledge Base Article: 19609
If you have a series of joined tables and join the results, you may get incorrect results or a fatal error. An example of this would be Joining A to B to create A_B, then joining A_B to C .
ESRI Internal Tracking Number: CQ00142077
Knowledge Base Article: 18879
The display of date fields in the table window is incorrect when the day value is under 12 and the computer's region date setting is not set to DD/MM/YYYY.
ESRI Internal Tracking Number: CQ00143341
Knowledge Base Article: 19387
When event layers are used as part of a spatial join, incorrect results may be returned.
ESRI Internal Tracking Number: CQ00140801
Knowledge Base Article: 19582
When using some layers based on an XY event source, it is not possible to perform attribute or interactive selection on that table.
ESRI Internal Tracking Number: CQ00141209
Knowledge Base Article: 17582
The 'Add Field' command is available on read-only tables when looking at only the selected records. Using this command appears to work but will produce potentially fatal errors.
ESRI Internal Tracking Number: CQ00144120
Knowledge Base Article: 19617
ESRI Internal Tracking Number: CQ00141027
If the tableview window is used in a standalone Visual Basic application programmatically, using the context menus will fatal the Visual Basic application.
ESRI Internal Tracking Number: CQ00142172
Knowledge Base Article: 19672
Using ArcObjects, if a raster layer is included in the selection environment, when clear selection is called, custom-built applications will produce a fatal error. ESRI Internal Tracking Number: CQ00143367
Knowledge Base Article: 19843
ArcMap will crash, if you perform a join then add a field to the joined layer or table, and then use the summarize command.
ESRI Internal Tracking Number: CQ00141033
Knowledge Base Article: 19610
If you use the table window to edit geodatabase data, field defaults defined in a subtype will not be applied when the subtype is changed. This may be inconsistent with the attributes dialog box.
ESRI Internal Tracking Number: CQ00141027
Knowledge Base Article: 19611
The SDTS Point to Coverage and SDTS Raster to Grid Tools cause ArcToolbox to freeze. A 'flexlm' error message appears after trying to use either of the two tools.
ESRI Internal Tracking Number: CQ00142674
Knowledge Base Article: 19260
If a feature class table has blob fields and is exported to a shapefile, a "General Function Error" is reported and the file cannot be exported.
ESRI Internal Tracking Number: CQ00117388
Knowledge Base Article: 198907
When using ArcSDE for Coverages, you may get 'Invalid SQL syntax' when you attempt to export features from ArcSDE for Coverages into a geodatabase.
ESRI Internal Tracking Number: CQ00141955
Knowledge Base Article: 18624
If you connect to ArcSDE as user A, right click a feature class and select export to geodatabase, then select a connection as another user and create a new feature dataset and click OK. The new dataset will generate an error "must be owner to perform this operation."
ESRI Internal Tracking Number: CQ00141497
Knowledge Base Article: 19744
No datum transformations are listed when you are converting data between geographic coordinate systems. Two datasets can have the same coordinate systems. One will work and the other one won't.
ESRI Internal Tracking Number: CQ00142086
Knowledge Base Article: 19185
When tabbing in the buffer dialog it is easy to enter the wrong values in the fields (i.e., text where numbers should go), which would create an error when the command is executed.
ESRI Internal Tracking Number: CQ00141107
Knowledge Base Article: 19745
When an erase polygon is added to an existing TIN, the application may crash. After the application crashes, the applications document (MXD or SXD) may be invalid.
ESRI Internal Tracking Number: CQ00141785
ArcMap and ArcScene may crash if two large tins (each with 500,000+ nodes) are built consecutively in the same session.
Knowledge Base Article: 19499
ESRI Internal Tracking Number: CQ00144061
The TIN building process is slow when using densely sampled point data that is spatially sorted (e.g. north to south). Typical data that exhibits this quality is LIDAR.
ESRI Internal Tracking Number: CQ00143685
Knowledge Base Article: 19336
In ArcScene, Some 3D polyface based CAD data displays flat, as if there are no Z values. Additionally, some polymesh based entities do not display at all.
ESRI Internal Tracking Number: CQ00143660
Knowledge Base Article: 19574
In ArcScene, if a non-spatial table is added to the document and then the document is saved (to an SXD file), the document will become corrupt and cannot be opened.
ESRI Internal Tracking Number: CQ00141215
Knowledge Base Article: 19226
When an ArcScene document is opened and some of the layers need repair (i.e., the data sources cannot be found), many of the ArcScene commands will cause a fatal error if they are used before all the layers are repaired.
ESRI Internal Tracking Number: CQ00141801
Knowledge Base Article: 19225
When a TIN is built using the Create TIN commands, there is an option to assign tag values to the TIN. This option is ignored and tag values are always assigned to the TIN features.
ESRI Internal Tracking Number: CQ00141565
Knowledge Base Article: 19223
The Create Tin from Features command will produce a fatal error, which will crash the application if the input data contains points and the data source has a spatial reference. If the input data is a layer in the document, it will work correctly, but will crash if the data is chosen from disk.
ESRI Internal Tracking Number: CQ00140778
Knowledge Base Article: 19209
In ArcScene, if a raster is draped over a surface and is made partially transparent, a seam is visible running across the image. This seam comes from the internal tiling of the images.
ESRI Internal Tracking Number: CQ00141512
In ArcScene, after an image catalog is added, the property pages for the catalog do not show the Display tab.The Display tab is visible in ArcMap.
ESRI Internal Tracking Number: CQ00142528
ArcCatalog can preview image catalogs, but cannot show Image Catalogs in 3D mode in the preview window.
ESRI Internal Tracking Number: CQ00141991
In ArcScene, if you select the zoom in/out tool before adding data, ArcScene will produce a fatal error.
ESRI Internal Tracking Number: CQ00140906
Knowledge Base Article: 19210
When the Steepest Path tool is used on a TIN the resultant path will backtrack on itself along a horizontal TIN edge resulting in incorrect output.
ESRI Internal Tracking Number: CQ00140736
Knowledge Base Article: 19228
ArcScene reports an error when a scene is printed and no output is sent to the printer.
ESRI Internal Tracking Number: CQ00141993
When exporting VRML from ArcScene the resultant VRML may not look the same as the scene as the VRML file has the optional headlight turned on in the output.
ESRI Internal Tracking Number: CQ00139878
Knowledge Base Article: 19221
In many cases the default navigation speed within the VRML file exported from ArcScene is set to an inappropriate value causing difficulties in navigating the VRML.
ESRI Internal Tracking Number: CQ00139935
Knowledge Base Article: 19219
When VRML files are exported, there is an option to use the VRML type ElevationGrid for rasters in ArcScene.This option does not work. As a result, the VRML file is unnecessarily large.
ESRI Internal Tracking Number: CQ00141858
Knowledge Base Article: 19547
If you press Esc to halt a TIN layer from drawing, the triangles stop drawing but control is not returned to the user for some time. This occurs for TINs that have no breaklines.
ESRI Internal Tracking Number: CQ00144329
If you remove a large number of layers or choose 'New Scene' from a scene with a large number of layers, the existing layers are removed very slowly from the TOC.
ESRI Internal Tracking Number: CQ00138617
Knowledge Base Article: 19243
If you export a Geostatistical layer to a raster dataset and the raster dataset has a space in the pathname ArcMap will produce a fatal error.
ESRI Internal Tracking Number: CQ00141520
Semivariogram/Covariance Surface does not print and the cloud of points is not printed accurately.
ESRI Internal Tracking Number: CQ00141965
If you choose the detrending option on the last dataset, it will not be used unless the detrending option is set on the first dataset as well.
ESRI Internal Tracking Number: CQ00143471
When using Spatial Analyst, a fatal error occurs when obtaining a histogram for a numeric field that isn't the default "Value" field.
ESRI Internal Tracking Number: CQ00144475
Knowledge Base Article: 19809
The environment settings for Spatial Analyst include the ability to set a MaxOf setting for extent and cell size (Union of inputs). Some of the Spatial Analyst commands do not honor this setting.
ESRI Internal Tracking Number: CQ00142413
Knowledge Base Article: 19028
If a shapefile is used as a mask for an analysis operation, an error "The cell size value is either invalid or not defined" is returned when using the Raster Calculator.
ESRI Internal Tracking Number: CQ00139959
Knowledge Base Article: 19825
If you select an area of a raster and attempt to show a histogram based on the selected data using a text field, the results may not represent the field you specified.
ESRI Internal Tracking Number: CQ00140715
Knowledge Base Article: 18418
The default search radius for Density is always shown in the units for the data frame's spatial reference. It should only be in the units for the data frame when the output spatial reference is set to the same reference as the data frame. If the output spatial reference is set to same as input then the units for the default search radius should be in the units of the input's spatial reference.
ESRI Internal Tracking Number: CQ00140700
Knowledge Base Article: 18422
The INFODBASE and ARCSHAPE commands add a null character at the end of character fields for each record. This shows up as a box in Excel and a vertical line in FoxPro.
ESRI Internal Tracking Number: CQ00141522
Knowledge Base Article: 18783
The CONTROLPOINTS command aborts when attempting to delete a link.The link file is not saved unless you have saved it first. This happens running ARC in the Command Window
ESRI Internal Tracking Number: CQ00143593
Knowledge Base Article: 19283.
Labels are not created after running the REGIONPOLY command without the {out table} option when the input does not have labels. Labels are supposed to be created in this case but are not.
ESRI Internal Tracking Number: CQ00130167
Knowledge Base Article: 19261
Connecting to ArcSDE with a user name that has embedded spaces hangs the server. Here is an example from the command line:
sdelayer -o describe -u "sd e" -p sde
Notice the space between the "d" and the "e" in the username "sde". If this happens, the following symptoms may be experienced:
1. The client hangs until the giomgr is killed with the killp command.
2. The ArcSDE server cannot be stopped with command line or from Services Control Panel.
3. The command line utilities will hang if executed afterwards.
4. No new connections to the server are allowed. (Existing connections continue to function.)
ESRI Internal Tracking Number: CQ00141680
When a 1-bit raster has been loaded to Geodatabase and an attempt is made to mosaic another 1-bit raster to the same Geodatabase, the operation may fail with the following message: "invalid raster data."
ESRI Internal Tracking Number: CQ00143661
Knowledge Base Article: 19826
If a version is renamed to longer than 70 characters, then the vrgsrs in ArcSDE will produce a fatal error.
ESRI Internal Tracking Number: CQ00140123
The sderaster command has been added to the suite of ArcSDE administration tools. This command is available on the following platforms:
The command provides a way to load BSQ and TIFF format raster data into an ArcSDE geodatabase. Documentation for this command is in the Service Pack 1 version of the ArcSDE Developer Help under the Administration Command References topic.
This can be a serious problem if an incorrect dbtune table is created. An indicator of such a problem includes the inability to load data. This fix makes it more readily apparent that the dbtune table has a problem when you run the sdesetup command for each database.
ESRI Internal Tracking Number: CQ00142581
Knowledge Base Article: 19073
Only users loading very large shapefiles with rejected shapes would be affected by this problem. Currently, the reject file cannot be opened until load operation is complete and the spatial index is created.The fix in SP1 closes the reject file allowing users to begin to inspect the list of rejected shapes without having to wait for the shapefile to be fully loaded.
ESRI Internal Tracking Number: CQ00131855
If you run the sdeservice -o create command and specify the "-u" option with the "\" (back slash) instead of an "/" (forward slash), you get an application error - memory overwrite error.
ESRI Internal Tracking Number: CQ00135549
Usage for the sdelayer -o register command does not show the Spatial Index option and is hence inconsistent with what shows up for this command when you type sdelayer -h.This can be confusing for those that try this command without specifying the Spatial Index. However, the complete usage does show up when you type sdelayer -h or sdelayer -?.
ESRI Internal Tracking Number: CQ00122991
When the user enters a column that does not exist, ArcSDE returns the following error message:
Error: Attribute column not found (-38).
Error: Unable to create view <name of view>
The user must then determine which column they specified is incorrect.
ESRI Internal Tracking Number: CQ00135707
Knowledge Base Article: 18967
With Service Pack 1 installed, the SE_instance_get_version_locks command will return the appropriate information.
ESRI Internal Tracking Number: CQ00140562
An unresolved external symbol error is returned when trying to link to the following functions:
SE_layerinfo_is_storage_lob()
pe_objedithome_setfunc()
ESRI Internal Tracking Number: CQ00143582
When the primary shape is a donut polygon and the secondary shape is a polygon that matches the interior ring of the primary, the SE_shape_difference function returns a three-part polygon that includes the primary polygon and the secondary polygon. It should return only the primary polygon.
ESRI Internal Tracking Number: CQ00138296
Knowledge Base Articles: 18970
If you call the SE_shape_generate_buffer function and try to buffer on a line that has 3 points where the first and third points exist in the same coordinate space (they have the same coordinate values), the buffer method on that line will not return an object.
ESRI Internal Tracking Number: CQ00139054
Knowledge Base Articles: 18989
The SE_shape_generate_buffer function returns a "-1" when the xyunits are set to a value of 1 million.
ESRI Internal Tracking Number: CQ00125912
Knowledge Base Articles: 18991
In specific cases, polygons created using the SE_shape_generate_polygon function may produce incorrect polygons after importing the data.
ESRI Internal Tracking Number: CQ00133446
Knowledge Base Articles: 18973
Applying the expression RELATE('TTTTTTTTT') to two overlapping polygons currently returns FALSE because the SE_shape_evaluate_CBM function is currently not comparing the boundary/interior and interior/boundary of the two shapes.
ESRI Internal Tracking Number: CQ00141173
Knowledge Base Articles: 18971
The SE_shape_clip misses the second extent when it compares the clipping window.
ESRI Internal Tracking Number: CQ00141357
Knowledge Base Articles: 18972
If the SE_shape_is_disjoint function is used to compare two linestrings and one of them partially surrounds one end of the other, it will return FALSE even though the lines intersect.
ESRI Internal Tracking Number: CQ00137929
Knowledge Base Articles: 18969
The SE_shape_union function does not correctly compare miscompares rings that are touching when two polygons are compared. Therefore, SE_shape_union can sometimes return results that are inconsistent with the SE_shape_is_overlapping function.
ESRI Internal Tracking Number: CQ00132074
This problem can also be seen if creating an index via ArcCatalog. Service Pack 1 fixes both of these occurrences.
ESRI Internal Tracking Number: CQ00143783
All operations with versioned data should have their performance improved with this change.
ESRI Internal Tracking Number: CQ00143330
Example: Load a shapefile using Spatial Extender's Control Center. Register it with the geodatabase and then register it as versioned. Add the featureclass to ArcMap. Click on the sketch tool, create a new feature and try adding it. It fails with the following error message:
Create:An unexpected failure occured.
Underlying DBMS error CLI0100E Wrong number of parameters.
SQLSTATE=07001::07001][SDESPICE.DB2ADMIN.CNTRY94]
ESRI Internal Tracking Number: CQ00143518
Adding a new complex edge on a SimpleNetwork fails with an underlying DBMS error "Wrong number of parameters".
ESRI Internal Tracking Number: CQ00143528
This fix returns a more informative message if the grid size specified is too small.
ESRI Internal Tracking Number: CQ00136487
Example: Load data and create a geocoding service. Locate the address in ArcMap using the geocoding service and find an address. If the data is not registered as versioned, the address can be located, but if the data is registered as versioned, then ArcMap will hang.
ESRI Internal Tracking Number: CQ00141558
You'll get the error:
Error: DBMS table not found (-37).
Error: Unable to create view testview
ESRI Internal Tracking Number: CQ00142313
If you use the sdelayer -o alter command to alter a feature class' spatial index grid size to an invalid grid size, then put the layer into load_only_io, you cannot put it back into normal_io, even if you reset the grid size correctly.
ESRI Internal Tracking Number: CQ00141394
Alter the spatial index and assign an invalid number. It crashes the gsrvr the first time you do this producing a NETWORK I/O error message. A second attempt results in successfully modifying the layer. If you were then to try to change the layer from load_only_io to normal_io mode (to rebuild the spatial index), you would get an underlying DBMS error.
ESRI Internal Tracking Number: CQ00141393
An error inside the DB_sp_states_def_delete function causes the compression to fail when SDE.STATES table has exactly 202 states (also fails for 402, 602, etc. 200xN+2 in general).>
ESRI Internal Tracking Number: CQ00143092
If you use sdelayer -o register to register a non-ArcSDE layer with ArcSDE, it will fail. Example: Load a shapefile with the DB2 Control Center. In order for ArcSDE client applications to see it, you must register it with sdelayer -o register.After it is registered, the data cannot be viewed with ArcCatalog (or any other ArcSDE client).
ESRI Internal Tracking Number: CQ00141782
Cutting 99 or less features works correctly.
ESRI Internal Tracking Number: CQ00142065
Test with 900 states and a state_lineages table up to 450,000. The first edit is taking 0.7 seconds and the last (900th) takes 13 seconds.
ESRI Internal Tracking Number: CQ00142071
Cutting 99 or less features works correctly.
ESRI Internal Tracking Number: CQ00142065
This adversely affects performance and has bee resolved in Service Pack 1.
ESRI Internal Tracking Number: CQ00141822
Users will see an improvement when loading data into blob columns. Annotation, for example, is loaded into a blob column.
ESRI Internal Tracking Number: CQ00142067
If you create a view in Informix with the sdetable command:
sdetable -o create_view -T con130_v -t contourline -c shape, se_row_id, elevation -w "elevation = 130" -i informix_sde -u topodba -p gisadmin
it completes successfully. However, if you attempt to then delete that view with sdetable:
sdetable -o delete -t con130_v -i informix_sde -u topodba -p gisadmin
the following error occurs:
ArcSDE 8.1Build 564 Mon Apr 23 12:01:41 PDT 2001
Attribute Administration Utility
-----------------------------------------------------
Delete table con130_v! Are you sure? (Y/N): y
Error: Underlying DBMS error (-51).
Error: Unable to delete table con130_v.
Underlying DBMS error
ESRI Internal Tracking Number: CQ00143791
ESRI Internal Tracking Number: CQ00143092
In order to transmit the coordsys of the coordinate reference, the Java API in Service Pack 1 has an implementation of pe_coordsys_from_string() and pe_coordsys_to_string() from the C-API, written in pure Java code. A new Java class was created for each of the projection objects, and each one has a constructor that takes a String (from_string equivalent), as well as a toString() method. These classes implement only the methods to support coordsys transmission of a coordinate reference to the Java API. The rest of the PE functionality in Java is available through the Geodesy Package from ArcIMS.
These are the new public classes added:
The M and Z values of a feature in a layer could not be read because the Shape's "hasZ" and "hasM" flags were set to false even though the shape had Z and M values.
ESRI Internal Tracking Number: CQ00142271
Knowledge Base Article: 18366
When the connection is changed, to operate on another database (SqlServer, DB2, Informix), the function to retrieve the database name would retrieve the name of the database that was connected to when creating the connection instead of the database currently connected to.
ESRI Internal Tracking Number: CQ00138999
Knowledge Base Article: 18992
There is a difference in the output from the SeVersion get methods; getName returns the name in the format <version_name> and getParentName returns the name in the format <owner>.<version_name>, while the corresponding C_API methods return the name in the same format: <owner>.<version_name>.
ESRI Internal Tracking Number: CQ00140082
When null values are passed as parameters to SeLog methods addIds, addId and deleteId, the program throws a network I/O error instead of an invalid parameter error.
ESRI Internal Tracking Number: CQ00138604
An error occurs in the SeShape.getAllPoints method when the wantSubPartOffsets option is set to false. The method was not written to handle this option.
ESRI Internal Tracking Number: CQ00142479
Knowledge Base Article: 18990
In Service Pack 1, an enhancement to the SeTable function was made so that the user can create a table without having to specify a configuration keyword for the table (the default keyword is used).
ESRI Internal Tracking Number: CQ00141307
ArcExplorer hangs when using the QueryBuilder to select features from a layer that has annotation.
ESRI Internal Tracking Number: CQ00142511
Knowledge Base Article: 18691
The gsrvr processes occasionally remain orphaned on the ArcSDE server after the client program that created the process has finished running.
ESRI Internal Tracking Number: CQ00139542
Knowledge Base Article: 19414
If the SeDate constructor is created with a java.util.Date object with a time zone setting different from the default time zone setting of the JVM, the SeDate.toWhereStr() changes the time to the local time zone. It should use the GMT time zone by default to avoid confusion.
ESRI Internal Tracking Number: CQ00140943
Knowledge Base Article: 18985
Arbitrary (wrong) date values are returned when reading the date column from an ArcSDE for coverages server.
ESRI Internal Tracking Number: CQ00141670
Knowledge Base Article: 19414
An extra call to locatorAsString.append(hexDigits[len & 0xF])was causing the Locator properties to be read incorrectly. Service Pack 1 remedies this problem.
ESRI Internal Tracking Number: CQ00142230
The SeLayer.getQualifiedName when executed against an ArcSDE 3.0.2 Informix server returns the table names in the format <ownername>.<table name> instead of the format <database>:<ownername>.<table name> from the ArcSDE 8.1 server.
ESRI Internal Tracking Number: CQ00142700
Incorrect results are experienced when doing a comparison between numbers with precision greater than 15. Since C only supports precision up to 15 digits, comparison between doubles in the SeExtent.isEmpty method should ignore the digits after the 15th to get the correct result.
ESRI Internal Tracking Number: CQ00142491
When SeDelete.fromTable is called, the delete operation is not committed to the database. It has now been fixed so that the delete operation is committed when SeConnection.close() is called.
ESRI Internal Tracking Number: CQ00141579
Knowledge Base Article: 18097
If the GDB_OBJECTCLASSES EXTPROPS column is set to a long raw (the default), will not occur.
ESRI Internal Tracking Number: CQ00142866
Knowledge Base Articles: 18958
When a logfile is created using a selection set of points from a LOB layer a load buffer is generated due to an ORA-01008 error: not all variables bound.
ESRI Internal Tracking Number: CQ00143373
ESRI Internal Tracking Number: CQ00142274
This is for a general performance improvement.
ESRI Internal Tracking Number: CQ00142434
Not having the Oracle server thread-safe will cause problems in the direct connect driver. Making the server thread-safe was required so that users can use concurrent direct connects within an application.
ESRI Internal Tracking Number: CQ00127008
If you connect to Oracle as "Joe" and attempt to create a join to a table owned by "Bill," you'll get this error.
ESRI Internal Tracking Number: CQ00140194
A general performance improvement has been made in Service Pack 1 to fix this situation.
ESRI Internal Tracking Number: CQ00139946
A general performance improvement has been made in Service Pack 1 to fix this situation.
ESRI Internal Tracking Number: CQ00142394
This fix allows terminal servers to be used with ArcSDE for Oracle and SQL Server, as you would expect to be able to.
ESRI Internal Tracking Number: CQ00142286
Compress time before fix was 16 hours. Compress time after fix is about 30 minutes. This only affects compress operations with very large state_lineages tables.
ESRI Internal Tracking Number: CQ00142395
Knowledge Base Articles: 19069
A 3rd party table is one created by a non-ArcSDE client and then registered to ArcSDE. Service Pack 1 has added checks to appropriately deal with 3rd party tables.
ESRI Internal Tracking Number: CQ00140461
Example:
1. Use ArcMap to connect to an Oracle Spatial polygon feature class that is registered as versioned.
2. Start editing.
3. Add new polygon vertices.
ESRI Internal Tracking Number: CQ00143278
If connected with direct-connect, ArcMap crashes.
ESRI Internal Tracking Number: CQ00143278
ESRI Internal Tracking Number: CQ00140461
Oracle allows application specific elements identified by an ETYPE of 0. ArcSDE is failing to handle the case where these exist. ArcSDE needs to skip the element, and process the geometry as if it didn't contain the ETYPE 0. See the Knowledge Base entry and the updated Appendix D in the ArcSDE Configuration and Tuning Guide for Oracle (config_tuning_guide_oracle.pdf) for more information.
ESRI Internal Tracking Number: CQ00144006
Knowledge Base Articles: 19091. 19092, 19093
Error handling for this case has been improved.
ESRI Internal Tracking Number: CQ00132067
Knowledge Base Article: 19836
Rolling back a transaction using either the Defined Layers command "Dataset Transaction rollback" or ArcObjects' ITransactions method "AbortTransaction" will fail and return no error.
ESRI Internal Tracking Number: CQ00139649
Knowledge Base Article: 18299
Service Pack 1 now caches row ids and a general performance improvement will be experienced in editing data.
ESRI Internal Tracking Number: CQ00138034
Knowledge Base Article: 19841
This has been fixed with Service Pack 1.
ESRI Internal Tracking Number: CQ00141792
Knowledge Base Article: 19842
When you query on a cross-database layer and do not include the spatial column in the select list, and if there are spatial filters applied, the query will fail with the error: ATTRIBUTE COLUMN NOT FOUND.
ESRI Internal Tracking Number: CQ00140622
Knowledge Base Article: 19844
Service Pack 1 enables names to now exceed 32 characters in length.
ESRI Internal Tracking Number: CQ00142315
Knowledge Base Article: 18898
If using direct connect with the ArcSDE administration commands and an error is encountered, the error message is either non-existent or poor. Service Pack 1 addresses this need and provides better error messages.
ESRI Internal Tracking Number: CQ00133787
Knowledge Base Article: 19847
ESRI Internal Tracking Number: CQ00136160
Knowledge Base Article: 19848
This fix allows terminal servers to be used with ArcSDE for Oracle and SQL Server.
ESRI Internal Tracking Number: CQ00142286
Knowledge Base Article: 17811
ESRI Internal Tracking Number: CQ00133687
Knowledge Base Article: 19849
If you connect to the sde database but mismatch the case of 'sde' to 'SDE', the connection will fail and use tempdb.
ESRI Internal Tracking Number: CQ00142438
Knowledge Base Article: 19850
Service Pack 1 addresses and resolves this problem.
ESRI Internal Tracking Number: CQ00144397
Knowledge Base Articles: 19851
This is a problem when the ArcSDE server and the client are running on the same machine.
ESRI Internal Tracking Number: CQ00144517
Knowledge Base Article: 19852
Some of the help files (Editor, ArcMap, ArcCatalog) contain dynamic graphics, which will not display correctly under IE 5.5.
KBuilder doc #: 18913
ESRI Internal Tracking Number: CQ00142612
The help for Remap for Spatial Analyst is incorrect.
ESRI Internal Tracking Number: CQ00142325
ESRI Internal Tracking Number: CQ00142946
ESRI Internal Tracking Number: CQ00141259
ESRI Internal Tracking Number: CQ00142293
ESRI Internal Tracking Number: CQ00141545
ESRI Internal Tracking Number: CQ00143820
ESRI Internal Tracking Number: CQ00142593
ESRI Internal Tracking Number: CQ00142633
ESRI Internal Tracking Number: CQ00141259
ESRI Internal Tracking Number: CQ00144214