English

ArcGIS 10.2.2 for (Desktop, Engine, Server) Geodatabase and Feature Service Sync Optimization Patch

Summary

This patch addresses several issues related to sync performance and concurrency, grid-based spatial indexes, versioned views, geometry storage migration, ST_Geometry (Oracle), network datasets and general geodatabase performance.

Description

Introduction

Esri® announces the ArcGIS 10.2.2 for (Desktop, Engine, Server) Geodatabase and Feature Service Sync Optimization Patch. This patch addresses several issues related to sync performance and concurrency which are particularly significant when there is a large number of sync replicas in the system, or when using SQL Server enterprise geodatabases to host your services. Additionally it addresses issues related to the creation of grid-based indexes in pre-10.1 geodatabases, the creation of versioned views, geometry storage migration, ST_Geometry on Oracle, network datasets and general geodatabase performance. It deals specifically with the issues listed below under Issues Addressed with this patch.


Issues Addressed with this patch


  • NIM086295 - On Oracle ST_OrderingEquals is always returning the same value as ST_Equals.
  • NIM088321 - User defined spatial index grids are not honored by ArcGIS when using the Add Spatial Index tool, even though the tool runs successfully.
  • NIM089682 - The following error message is returned when editing data that has been migrated from SDEBINARY to ST_GEOMETRY: "ORA-20085: Insert Spatial Reference SRID # does not match <schema.A###.SHAPE> registered Spatial Reference SRID 0".
  • NIM091900 - After applying SP5 for ArcSDE 10, adding a new partition on a ST_Geometry table that contains a spatial index returns the following error: "ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine."
  • NIM094929 - In ArcMap, panning on a feature class created with a partitioned keyword for the ST_Geometry table returns the error "ORA-01000".
  • NIM097633 - The traveltime/distance returned by the OD Cost Matrix solver is occasionally excessively high when using a hierarchy compared to when not using a hierarchy.
  • NIM097983 - Optimize the opening of map documents by augmenting the geodatabase schema cache to include the properties of the sde metadata.
  • NIM098475 - Spatial indexes are not created when creating a feature class on an ArcSDE 10 database from an ArcGIS Desktop 10.2 Client.
  • NIM098917 - When the Network Dataset is allowed to build successfully, if a dirty area remains, an HRESULT must be returned so the user knows they are in this unique state.
  • NIM099080 - ArcCatalog does not return an error when the versioned view name has over 30 characters, and fails to be created during Register As Versioned process in an Oracle geodatabase due to Oracle's 30 character limitation.
  • NIM099085 - In ArcObjects 10.2, the CreateVersionedView method on the IVersionedView interface does not set the versioned view name to the string passed in. This works in ArcObjects 10.1.
  • NIM099098 - ST_ASTEXT Function is failing when the result set contains more than one record, and when the NUMPOINTS is ~2000 (or more).
  • NIM099162 - Use the schema cache when loading map services to improve map service start time performance.
  • NIM099198 - Use the schema cache when loading map documents in Engine applications to improve load performance.
  • NIM100049 - The OD Cost Matrix solver is slow when trying to solve from many orders to a single distribution center.
  • NIM100141 - Missing index on the SDE versions table results in full table scan.
  • NIM100273 - Views get overwritten during register as versioned if a view / versioned view of same name exists.
  • NIM100503 - Loading a very large shape (>15k points) followed by small shape results in ORA-28579: error.
  • NIM100692 - Filter out multi-versioned views from the list of objects returned by SE_table_list_tables().
  • NIM100697 - Change the "_VW" suffix to "_EVW" when versioned views are created, in order to be consistent the EVW naming convention when we create MV views.
  • NIM100941 - Improve the Performance and Scalability of Creating and Syncing replicas by more efficiently caching database information.
  • NIM100942 - Deadlocks can happen on SQL server when multiple processes are creating and syncing replicas.
  • NIM101191 - Create and Sync replica should only activate schema cache if the replica has 10 or more datasets
  • NIM101804 - Do not return feature datasets in which the connecting user has no access to feature classes within.
  • NIM101806 - Provide a mechanism to log what release a client is using when connecting to a geodatabase.
  • NIM102077 - ArcGIS reports that an Oracle SDELOB or WKB feature class created in a pre-10.1 geodatabase does not have a spatial index when it does exist.
  • NIM102230 - Do not return the Documentation field on joined queries for Geodatabase internal metadata.
  • NIM102516 - Syncing where more than 1000 edits are downloaded with more than one client at the same time will cause one client to error.
  • NIM102517 - Decrease the size of the delta being downloaded to improve performance of download time on sync.
  • NIM102761 - When the Migrate Relationship Class gp tool is run on an attachment relationship class, attachments are no longer attached to the features.
  • NIM102762 - When the Migrate Relationship Class gp tool is run on an attributed composite relationship class, the composite relationship is not maintained when an origin feature is deleted.
  • NIM102848 - Creating a spatial index will pass values gathered from existing enterprise feature classes that may be invalid instead of passing correct values.
  • NIM102883 - When using a newer client (10.1+) against an older SQL server geodatabase (pre-10.1) through an application server connection, creation of a spatial index will fail on GEOMETRY or GEOGRAPHY feature classes with "This SDE server does not support this client or operation".
  • NIM102996 - After dropping a spatial index on a binary feature class through an application server connection to a pre-10.1 geodatabase in SQL Server, ArcGIS is unable to determine the index is gone.
  • NIM103073 - Inserting a row into a table that has a column data type of VARCHAR (4001) will fail with "Invalid precision value".

Installing this patch on Windows


Installation Steps:


ArcGIS 10.2.2 for Desktop, Engine or Server must be installed before installing this patch.

  1. Download the appropriate file to a location other than your ArcGIS installation location.

  2.     Checksum (Md5)
    ArcGIS Desktop
    Background Geoprocessing (64-bit)
    ArcGIS-1022-BGDT-GFFSO-Patch.msp 1A5A20C88302DD861FCE6C92C4254D25
         
    ArcGIS Engine
    Background Geoprocessing (64-bit)
    ArcGIS-1022-BGE-GFFSO-Patch.msp 2C040A78B6691837B14B1C42C9736B57
         
    ArcGIS for Desktop ArcGIS-1022-DT-GFFSO-Patch.msp D2D69A5060F78BCA89B1B4E3CFE78117
         
    ArcGIS Engine ArcGIS-1022-E-GFFSO-Patch.msp AFFDCF77F18BA25A26EFB714017C245E
         
    ArcGIS for Server ArcGIS-1022-S-GFFSO-Patch.msp 4248A87412328DECD49F9A8B88914FC0
         

  3. Make sure you have write access to your ArcGIS installation location.

  4. Double-click ArcGIS-1022-<Product>-GFFSO-Patch.msp to start the setup process.

    NOTE: If double clicking on the MSP file does not start the setup installation, you can start the setup installation manually by using the following command:

    msiexec.exe /p [location of Patch]\ArcGIS-1022-<Product>-GFFSO-Patch.msp

  5. After the installation procedure has finished, complete Upgrade a geodatabase section.


Installing this patch on Linux


Installation Steps:


Complete the following install steps as the ArcGIS Install owner. The Install owner is the owner of the arcgis folder.

ArcGIS 10.2.2 for Engine or Server must be installed before installing this patch.

  1. Download the appropriate file to a location other than your ArcGIS installation location.


        Checksum (Md5)
    ArcGIS Engine ArcGIS-1022-E-GFFSO-Patch-lx.tar 0C98D3E8961ACFFD39117CB109E727BA
         
    ArcGIS for Server ArcGIS-1022-S-GFFSO-Patch-lx.tar 15FC8F74FF9B26993DFFAFE73B55E1CA

  2. Make sure you have write access to your ArcGIS installation location, and that no one is using ArcGIS.

  3. Extract the specified tar file by typing:

    % tar -xvf ArcGIS-1022-<Product>-GFFSO-Patch-lx.tar

  4. Start the installation by typing:

    % ./applypatch

    This will start the dialog for the menu-driven installation procedure. Default selections are noted in parentheses ( ). To quit the installation procedure, type 'q' at any time.

  5. After the installation procedure has finished, complete the Upgrade a geodatabase section.

Upgrade a geodatabase

A geodatabase upgrade is required after applying this patch. To upgrade the geodatabase, follow the instructions in the help section specific to your database management system:

Patch Updates

Check the Patches and Service Packs page periodically for the availability of additional patches. New information about this patch will be posted here.

How to identify which ArcGIS products are installed

To determine which ArcGIS products are installed, choose the appropriate version of the PatchFinder utility for your environment and run it from your local machine. PatchFinder will list all products, hot fixes, and patches installed on your local machine.

Getting Help

Domestic sites, please contact Esri Technical Support at 1-888-377-4575, if you have any difficulty installing this patch. International sites, please contact your local Esri software distributor.