ArcGIS 10.2.1 for (Desktop, Engine, Server) Utilities and Telecom Update 2 Patch

• BUG-000081231 - After disconnecting and connecting linear source features from a geometric network and updating the associated schematic diagram, a new schematic ID is generated for that feature and the vertices are removed.
• BUG-000082028 - Standard editing workflows consume increasing amounts of memory and do not release it after editing has stopped.
• BUG-000082630 - Versioned Difference Cursor single branch edits invert the "type" of change reported (e.g., Deletes become Inserts, Inserts become Deletes).
• NIM088321 - User defined spatial index grids are not honored by ArcGIS when using the Add Spatial Index tool, even though the tool runs successfully.
• NIM096460 - After dropping and rebuilding the geometric network and updating a schematic diagram containing schematic rules, network junction locations are not preserved.
• NIM097184 - Creating a checkout in a 9.3.1 geodatabase fails with 10.2.1 Desktop.
• NIM097983 - Optimize the opening of map documents by augmenting the geodatabase schema cache to include 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.
• NIM098196 - Exporting SDE schema using Oracle expdp generates ora-39127, ora-20098 and ora-06512 error about the spatial index created on GDB_items table having the st_grids parameter as commas when Oracle 11gR2 is used.
• NIM098665 - Making a connection to a non-spatial Oracle database using either a Spatial Database Connection or an OLE Database Connection takes a significantly long time when there is a large amount of objects in the database.
• NIM099484 - Provide a mechanism to enable instrumentation of memory usage when creating a feature cache in desktop.
• NIM096111 - Rotating a point after a specific selection workflow on a geometric network rotates and shifts the entire geometric network.
• NIM100182 - Bad SCHEMATICTID when diagrams get exported. Schematic features associated with GIS features which are not part of the geometric network are exported with "-2" at the end of their SCHEMATICTID.
• NIM100823 - Rebuild the spatial index on a versioned feature class fails with an SRID mismatch error.
• NIM100941 - Improve the Performance and Scalability of Creating and Syncing replicas by more efficiently caching database information.
• NIM101461 - When feature classes with different SRIDs are used in an ST_intersection query, it fails with 'ORA-06530: Reference to uninitialized composite'.
• NIM101468 - Unable to hide standalone tables using the IWorkspaceExtension.DataDictionaryTableNames method in ArcGIS 10.1 and above.
• NIM101270 - Recalculating the feature extent on specific datasets returns the following error: "Failed to recalculate extent. The specified coordinate exceeds the valid coordinate range."
• NIM101376 - ArcGIS for Desktop fails to save the connectivity rules for a specific geometric network.
• NIM101746 - The Alter Field online help documentation page indicates that the Alter Field tool is available at all license levels; however, the tool is unavailable at lower license levels.
• 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.
• NIM102846 - When exporting diagrams into another schematic dataset using the Export Schematic Dataset process configured with GUIDs reattachment, the process expects GUIDs for each feature they contain. This is blocking when GUIDs are only missing for a feature class, in particular when this is missing for _Junctions.
• 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'.
• NIM102895 - Data exported via a XML workspace does not retain any 4-byte (or greater) characters in the data's attribute table.
• 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.
• NIM103593 - File Geodatabase lock files should be opened as Read, rather than as Read/Write. This improves feature class/table creation performance.
• NIM103683 - When script/query/constant attributes are configured on a schematic feature class for which the schematic features are not initialized, the attributes are not updated.
• NIM103708 - Filter the AUDSYS, OJVMSYS, GSMADMIN_INTERNAL, DVSYS Oracle objects from connection in ArcGIS.
• NIM103781 - The network index DESC query must only fetch the necessary attributes and not SELECT * when obtaining the USERID or ELEMENT mappings.
• NIM104247 - Implement two new API functions for se_enable_schema_chache and se_disable_schema_cache.
• NIM104317 - When fetching a network dataset index page, only fetch the pageblob.
• NIM104321 - MDXT_xxx$% tables show up in ArcCatalog, connected to a 11.2.0.4 or 12.1.0.1 instance, and some are not deleted even when the feature class is deleted.

This patch includes all fixes in the ArcGIS 10.2.1 for (Desktop, Engine, Server) Utilities and Telecom Update 1 Patch.

• NIM086295- On Oracle ST_OrderingEquals is always returning the same value as ST_Equals.
• NIM088921 - Importing an SDE schema dump fails with ORA-39083 and ORA-02309 on SDE.st_type_export.validate_spref using datapump impdp.
• NIM089510 - Inconsistent results with st_astext_f query on polygons with more than 292 vertices.
• NIM090071 - Labeling features based on join table's field throws 'ArcMap drawing errors' when the table and feature class are stored in different DBMS.
• NIM094291 - The extent of data created in MicroStation DGN files is not correctly calculated in ArcMap 10.2 which causes the data to be displayed in the wrong location.
• NIM094556 - Results from the Trace Geometric Network geoprocessing tool to trace connected are not consistent with the trace results from the Find Connected tool in the Utility Network Analyst toolbar.
• NIM095455 - In an edit session, snapping stops working on a layer if a join exists on that layer.
• NIM096135 - Provide option to create user schema geodatabases by a user other than SYS.
• NIM096817 - Loading a large amount of coordinates via ST_Geometry function results in ORA-20004 and ORA-20000 errors.
• NIM097346 - Extproc not initialized when a ST_Intersects query involving a versioned view and a base table is the first query run in the session.
• NIM099098 - ST_ASTEXT Function is failing when the result set contains more than one record, and when the NUMPOINTS is ~2000 (or more).
• NIM099383 - Do not grant all privileges on user keyset tables when created.
• NIM099484 - Provide a mechanism to enable instrumentation of memory usage when creating a feature cache in desktop.
• NIM099485 - Attempting to build a feature cache fails without an error message and does not release consumed memory.
• NIM099500 - Reconciling a particular user version returns the following error: "Invalid network element ID."
• NIM099513 - Correctly release memory when a feature cache is cancelled on the workspace.
• NIM099517- Add a model dialog to the build feature cache command which allows a user to cancel the operation.
• NIM099519 - Do not cache layers in the feature cache when the scale range of the layer is greater than the maps extent.
• NIM099883 - The strings "Building map feature cache" is not localizable in the feature cache tool.
• NIM100028 - A significant amount of CPU power is used by an ArcMap 10.2.1 edit session when there are many layers in the map document.
• NIM100141 - Missing index on the SDE versions table results in full table scan.
• NIM100503 - Loading a very large shape (>15k points) followed by small shape results in ORA-28579: error.
• 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.
• NIM101280 - Provide additional status information during a compress operation in the compress_log.
• NIM101468 - Unable to hide standalone tables using the IWorkspaceExtension.DataDictionaryTableNames method in ArcGIS 10.1 and above.
• 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.
• NIM102265 - An annotation layer loaded from the Add Historical Archive button displays polygons instead of text.

System Administrators: A technical paper is available that discusses the enterprise deployment of ArcGIS 10.2.1 setups using Microsoft Systems Management Server (SMS), System Center Configuration Manager (SCCM), and Group Policy, including additional system requirements, suggestions, known issues, and Microsoft Software Installation (MSI) command line parameters. Deployment in a lockdown environment is also covered. ArcGIS 10.2.1 Enterprise Deployment.

ArcGIS 10.2.1 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	ArcGIS-1021-DT-UTU2-Patch.msp	5A97A3A6ED6E9D9A699F5F3F4EDFAF75
   ArcGIS Desktop Background Geoprocessing (64-bit)	ArcGIS-1021-BGDT-UTU2-Patch.msp	CE72A437E3225E2555CBD36D688401A8
   ArcGIS Engine	ArcGIS-1021-E-UTU2-Patch.msp	4E4241DE1D027E210B911BED8CC2717F
   ArcGIS Engine Background Geoprocessing (64-bit)	ArcGIS-1021-BGE-UTU2-Patch.msp	A2F81937653A923C648DA6F04B247DA8
   ArcGIS for Server	ArcGIS-1021-S-UTU2-PatchB.msp	B660B0EE51D66F8F296BB51D78F0A5A1

   
   
3. Make sure you have write access to your ArcGIS installation location.
4. 
   
5. Double-click ArcGIS-1021-<product>-UTU2-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-1021-<product>-UTU2-Patch.msp
   
6. 
   
7. After the installation procedure has finished, complete the Upgrade a geodatabase section.
8. 
   

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

ArcGIS 10.2.1 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-1021-E-UTU2-Patch-lx.tar	631899446347DBDCFFC6658F486F0D6F
   ArcGIS for Server	ArcGIS-1021-S-UTU2-Patch-lx.tar	2BB2B5EF330AEEA9D632B779B002C750

   
   
2. Make sure you have write access to your ArcGIS installation location, and that no one is using ArcGIS.
3. 
   
4. Extract the specified tar file by typing:
   
   
   % tar -xvf ArcGIS-1021-<product>-UTU2-Patch-lx.tar

5. 
   
6. 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.
7. 
   
8. After the installation procedure has finished, complete the Upgrade a geodatabase section.
9. 
   

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:

SQL Server

PostgreSQL

Oracle

Informix

DB2

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

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.

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.