English
Continue in the app

ArcGIS Server 10.8.1 Utility Network Patch 4

Summary

This patch addresses several functional issues with the utility network in ArcGIS Enterprise 10.8.1 along with performance improvements with validation, trace, update subnetworks, as well as general performance enhancements for SQL Server enterprise geodatabases.

Description

Esri® announces the ArcGIS Server 10.8.1 Utility Network Patch 4. This patch focuses on quality and performance particularly in the areas of validate and update subnetwork, and is recommended for all utility network customers using ArcGIS Enterprise 10.8.1. Users with SQL Server enterprise geodatabases will benefit from the updates that address issues with stored procedures and internal locking. In addition, this patch deals specifically with the issues listed below under Issues Addressed with this patch.

Important Note: A geodatabase upgrade is required for the SQL Server improvements. Please refer to the Upgrade a geodatabase section below for guidance.


Issues Addressed with this patch


  • BUG-000140539 - STIntersects() queries do not use the spatial index
  • BUG-000140525 - Implement the Validate optimization, when tracing to dirty subnetworks. When a tier contains no subnetworks do not trace the tier, because nothing could be marked as dirty.
  • BUG-000140449 - Connections blocked by exclusive table lock on sde_process_information.
  • BUG-000140443 - Validate of content feature generates updates for all associations of the container feature
  • BUG-000140214 - Post holding shared table lock on gdb_itemtypes for the duration of the post operation
  • BUG-000140030 - Improve performance for branch query with UUID log file table join.
  • BUG-000140013 - Dead lock can be encountered when multiple connections hold exclusive locks on the sde_process_information and sde_table_locks tables.
  • BUG-000139968 - Upgrade can create incorrect conditional index on GDB_Locks table.
  • BUG-000139833 - Deadlocking may on SDE_branches & SDE_branch_tables_modified tables during simultaneous reconcile and post operations.
  • BUG-000139379 - Conflict propagation incorrectly occurs in a specific scenario with Attributed Relationships and Branch Versioning.
  • BUG-000139299 - Editing Performance on Enabled Network Topo
  • BUG-000133185 - The 'Validate Network Topology' tool fails, and returns the following error message, "Edit operation failed. ERROR:"
To avoid conflicts on 10.8.1 this patch also addresses:
  • BUG-000137346 - Crash occurs when reconcile is executed while the intermediate table is not registered as versioned.
  • BUG-000137139 - Optimize UpdateAssociationInfo function by splitting the query to discover from/toglobalid associations
  • BUG-000136979 - Validate Network Topology incorrectly allocating large amounts of memory impacting server soc mem usage
  • BUG-000136930 - In a branch versioned service, sourcing from a PostgreSQL database, any interruption to the connection results into underlying DBMS error until service is restarted.
  • BUG-000136892 - When a -1 is returned to ArcGIS Pro the conflict resolution dialog is unable to properly present the conflicts
  • BUG-000136889 - After upgrading Enterprise Geodatabase 10.7.1 to 10.8.1 and running the query to get Next_RowID, the following error message is returned: Msg 8144, Level 16, State 2, Procedure DBO.i13_get_ids, Line 0 [Batch Start Line 0] Procedure or function i13_get_ids has too many arguments specified.
  • BUG-000136296 - Long running reconciles may block users from editing Default or reconciling other versions with Branch Versioning.
  • BUG-000136284 - Editing data which are registered as multibranch causes lock escalation and blocking scenarios in the geodatabases in the SQL Server.
  • BUG-000136107 - The Update Subnetwork tool fails and returns the error message, "ERROR 001400: The server took too long to answer. The client has timed out. (status code 28). Failed to execute (UpdateSubnetwork)."
  • BUG-000135328 - Reconcile fails on a branch version and returns the error message, "A row with this OID already exists."
  • BUG-000135117 - Updating the subnetwork on a geographic coordinate system (GCS) spatial reference utility network fails the second time for short lines.
  • BUG-000134954 - Reconciling multiple versions in the utility network using the Reconcile Versions tool crashes the ArcSOC.exe instance.
  • BUG-000134950 - Crash occurs when reconcile is executed while a related destination table was not registered as versioned
  • BUG-000134496 - Using the 'Reconcile Versions' tool and leaving the 'Abort if conflicts detected' parameter unchecked, the session is still aborting the reconcile.
  • BUG-000134378 - Remove upper function on GUID columns in parcel fabric queries against oracle enterprise geodatabases
  • BUG-000133698 - Enabling the topology with the 'Only generate errors' option does not clean the dirty areas of the error.
  • BUG-000132887 - The electric subnet lines and electric lines do not overlap when the UN is in a GCS of 'GDA2020'.
  • BUG-000132751 - Optimize sql statements for branch versioned queries when using an enterprise geodatabase in Oracle
  • BUG-000132315 - Remove unnecessary "where 1=1" clause from feature service queries
  • BUG-000130888 - The Register with Geodatabase tool fails when registering an empty feature class
  • BUG-000130742 - Optimize branch versioned pagination queries when using an enterprise geodatabase in Oracle

Installing this patch on Windows


Installation Steps:


This patch should be installed on all ArcGIS Server installations related to the ArcGIS Server site.

The ArcGIS product listed in the table must be installed on your system before you can install a patch. Each patch setup is specific to the ArcGIS product in the list. To determine which products are installed on your system, please see the How to identify which ArcGIS products are installed section. Esri recommends that you install the patch for each product that is on your system.

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

  2. ArcGIS 10.8.1  
       
         ArcGIS Server ArcGIS-1081-S-UN4-Patch.msp
         Checksum
         (SHA256)
    AFFACC045B1ECBB815A4194D2B15C33B2BAADFD5C47938AAA29639587809C060
       

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

  4. Double-click ArcGIS-1081-S-UN4-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-1081-S-UN4-Patch.msp


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. This patch should be installed on all ArcGIS Server installations related to the ArcGIS Server site.

The ArcGIS product listed in the table must be installed on your system before you can install a patch. Each patch setup is specific to the ArcGIS product in the list. To determine which products are installed on your system, please see the How to identify which ArcGIS products are installed section. Esri recommends that you install the patch for each product that is on your system.

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


    ArcGIS 10.8.1  
       
         ArcGIS Server ArcGIS-1081-S-UN4-Patch-linux.tar
         Checksum
         (SHA256)
    4A9BC41D207926EE64FE60D04077D3CDAA0F3C7174A5C8DFA36D3BC9327BCA88
       

  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-1081-S-UN4-Patch-linux.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.

Upgrade a geodatabase


When a hotfix or patch for ArcGIS has been applied, it may also be necessary to upgrade your geodatabase. See the Upgrade the Geodatabase section on the Geodatabase management page for your individual DBMS platform for more information.

Tip: Upgrade your Enterprise geodatabases stored in Microsoft SQL Server to take advantage of critical fixes to branch versioning.

Upgrading from ArcGIS Server requires the use of Python. If you are working with ArcGIS Server on Windows or Linux, you can access the appropriate Python 3 environment by using the python.exe which is included with the framework/runtime components of ArcGIS Server. Additionally, on Windows a script batch file is available to launch the Python 3 environment.

To perform the upgrade, create a script using this example Python syntax, and name the script upgrade_gdb.py.

import arcpy
Connection_File_Name_full_path="C:\\temp\\sysadmin_connection.sde"
arcpy.UpgradeGDB_management(Connection_File_Name_full_path, "PREREQUISITE_CHECK", "UPGRADE")

Additional documentation on how to Upgrade an enterprise geodatabase in SQL Server is available from this help topic: Upgrade an enterprise geodatabase in SQL Server

On Windows, run the upgrade script explicitly using the Python 3 environment. If ArcGIS Server is installed to the default location, the script can be executed with either of the following commands:

"C:\Program Files\ArcGIS\Server\framework\runtime\ArcGIS\bin\Python\scripts\propy.bat" C:\temp\upgrade_gdb.py
Or
"C:\Program Files\ArcGIS\Server\framework\runtime\ArcGIS\bin\Python\envs\arcgispro-py3\python.exe" C:\temp\upgrade_gdb.py

On Linux, launch the Python 3 environment using the following commands:

source /<arcgis_server_installation_directory>/arcgis/server/framework/etc/arcenv
unset LD_PRELOAD
unset CONDA_DEFAULT_ENV

And then execute the upgrade script with the following command:

wine "Z:\<arcgis_server_installation_directory>\arcgis\server\framework\runtime\ArcGIS\bin\Python\envs\arcgispro-py3\python.exe" <path_To>\upgrade_gdb.py


Uninstalling this patch on Windows


To uninstall this patch on Windows, open the Windows Control Panel and navigate to installed programs. Make sure that "View installed updates" (upper left side of the Programs and Features dialog) is active. Select the patch name from the programs list and click Uninstall to remove the patch.

Uninstalling this patch on Linux


To remove this patch on versions 10.7 and higher, navigate to the <Product Installation Directory>/.Setup/qfe directory and run the following script as the ArcGIS Install owner:



./removepatch.sh

The removepatch.sh script allows you to uninstall previously installed patches or hot fixes. Use the -s status flag to get the list of installed patches or hot fixes ordered by date. Use the -q flag to remove patches or hot fixes in reverse chronological order by date they were installed. Type removepatch -h for usage help.

Restart your ArcGIS services.



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.

December 2, 2021 The windows setup(s) of this patch have been updated with new digital signatures. This change addresses the possible install error:

A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

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.