Patches and updates
ArcGIS Server 10.9.1 Utility Network and Data Management Patch 3
Summary
Description
EsriĀ® announces the ArcGIS Server 10.9.1 Utility Network and Data Management Patch 3. This patch focuses on quality and performance particularly in the areas of validate, update subnetwork and reconcile, and is recommended for all utility network customers using ArcGIS Enterprise 10.9.1. This patch deals specifically with the issues listed below under Issues Addressed with this patch.
This Utility Network and Data Management patch is cumulative and includes several fixes from earlier patches. These fixes are listed below under Issues Addressed with this Patch.
Issues Addressed with this patch
- BUG-000152770 - The Export Subnetwork tool fails when Shape_Length is included in the result fields.
- BUG-000152746 - The Error Inspector does not update correctly if two instances of error layers from a validation-enabled feature service with Arcade attribute rules are present in a map.
- BUG-000152495 - Export subnetwork files must have the correct server prefix to allow the server to delete files.
- BUG-000152378 - Remove singleton queries from validate when accessing the eidmappings table.
- BUG-000152209 - Validate returns the discovered subnetworks in the response payload.
- BUG-000152047 - Optimize Oracle branch version spatial query to use DBMS 'rowid' instead of 'gdb_archive_oid' when joining to the analytic subquery.
- BUG-000152042 - The branch versioning reconcile and post require an application lock to ensure only one SOC per session can perform the operations.
- BUG-000152041 - Reconciling a version fails with the following error, "Null geometries are not allowed."
- BUG-000151865 - Poor performance when running ValidatingSubnetworkTraceResult during the Update Subnetwork operation.
- BUG-000151822 - Slow performance when viewing associations in Oracle.
- BUG-000151804 - The sde_purge_process_information procedure and delete statement can become blocked by uncommitted transactions on sys.objects.
- BUG-000151789 - Feature.AssociationStatus is out of sync after creating associations via an attribute rule.
- BUG-000151626 - Remove the singleton query from midspan connectivity processing.
- BUG-000151624 - Add MAXDOP 1 to all branch versioned queries that do not have a spatial or attribute-provided query filter.
- BUG-000151544 - The sde_branch_tables_modified primary cluster key must be branch_id, edit_moment, and registration_id.
- BUG-000151543 - Remove NOT EXISTS statements and replace them with where 'rn > 1' for branch versioning procedures.
- BUG-000151537 - Add the forceseek index hint to the delete statement in the SDE_Branch_modified_def_delete_procedure.
- BUG-000151443 - The Validate Network Topology tool with a Utility Network Version 3 deletes dirty areas when error features are present.
- BUG-000151400 - Creating multipart dirty area results in a SE_SHAPE with CAD properties.
- BUG-000151399 - Remove singleton query during the build to cache containment and attachment association records.
- BUG-000151397 - Silver dirty area features are not being removed by validate.
- BUG-000151335 - The validate process generates invalid errors for line terminals due to clipping.
- BUG-000151324 - Address duplicate vertex errors caused by conflicting XY and Z tolerances.
- BUG-000151323 - The validate network topology operation is fetching the entire subnetworks table.
- BUG-000151321 - The validate network topology operation on a UN3 release is incorrectly fetching all error features.
- BUG-000151315 - Validate is fetching the entire dirty area class.
- BUG-000151314 - Enable or validate using the wrong error code for vertices within the spatial reference tolerance, which must be error code 5.
- BUG-000151073 - Random poor performance and response times are encountered when editing, validating or reconciling versions.
- BUG-000150652 - Utility Network Version 3 produces duplicate records for the same type of dirty area for the same modified feature.
- BUG-000150504 - When editing vertices to relocate an electric junction and change the subnetwork connected to the service line, mark the new subnetwork as dirty while the original subnetwork is never flagged as dirty preventing the Update Subnetwork tool from being performed.
- BUG-000149876 - RestoreRow fails when an origin row is restored and participates in two relationship classes.
- BUG-000148896 - The Error Inspector does not update correctly if two instances of error layers from a validation-enabled feature service are present in a map.
- BUG-000147190 - Asynchronous Database cursors can cause performance impacts on SQL Server keyset cursors.
- BUG-000145428 - Optimization to reconcile by avoiding expensive sublineage queries by removing the 'not in' clause.
- BUG-000144260 - Slow performance when reconciling a branch version in PostgreSQL using the default work_mem settings.
To avoid conflicts this patch also addresses:
- BUG-000152378 - Remove singleton queries from validate when accessing the EIDMapping table
- BUG-000152124 - Slow query when expanding associated data in Attributes pane
- BUG-000152047 - Optimize Oracle branch version spatial query to use DBMS Rowid instead of GDB_ARCHIVE_OID when joining to the analytic subquery
- BUG-000151865 - Improve time spent ValidatingSubnetworkTraceResult during Update Subnetwork operation.
- BUG-000151822 - Slow performance when viewing associations in Oracle.
- BUG-000151626 - Remove singleton query from midspan connectivity processing (validate)
- BUG-000151237 - Reconcile fails on v3 [Invalid column name 'STATUS'. UN_6_Association]
- BUG-000151193 - The GetUser(portal) function fails in ArcGIS Enterprise 10.9.1.
- BUG-000151073 - branch version DML statements which use the gdb_ct1 or ct2 index via a scan will be blocked by long running transactions
- BUG-000150864 - Realign Route fails in an APR-UN environment if the beginning/end of the centerline(s) used for the realignment don't touch the route.
- BUG-000150026 - Importing Associations populates values for the From/ToTerminalID fields in the Associations table when it is not applicable.
- BUG-000149966 - Realign Route with abandonment fails when there are 200+ centerlines involved in the edit due to Pro timeout.
- BUG-000149811 - When adding a feature service containing query layers in ArcGIS Pro, a getEstimates call is returned which results in the error message, "code":500,"message":"Error performing estimates operation","details" returned.
- BUG-000149552 - A map service query layer fails to query statistics if the data is not registered with the geodatabase and sdo geometry is the storage type.
- BUG-000149497 - When importing associations, logically deleted records must be filtered during duplication check with Utility Network 4.
- BUG-000149496 - Improve the validation performance for queries to the EIDMapping table.
- BUG-000149297 - Aggregated trace results with a function barrier on the shape length are returning the entire line.
- BUG-000148965 - The validation service operation checks the entire data workspace instead of only validating the layers included in the service.
- BUG-000148965 - Evaluate is reading the entire workspace
- BUG-000148896 - The Error Inspector does not update correctly if two instances of error layers from a validation-enabled feature service are present in a map.
- BUG-000148539 - Reconciling a utility network's named version returns the error message, "The subnetwork controller name already exists in the specified tier. []."
- BUG-000148467 - A map service created with SDO_geometry data type, referencing a non-enterprise geodatabase, fails to query when a polygon search geometry and outStatistics parameters are used.
- BUG-000148331 - IsDirty property is not set to 'True' after editing an embedded tier in the utility network. Subsequently, Subnetwork Name for lower tiers is not updated, even after running Update.
- BUG-000148070 - Missing geometry for some features after running the Export Subnetwork tool with the Include Geometry parameter enabled.
- BUG-000147861 - Creating an association through an attribute rule fails with the error message, "unknown error" in an SQL Server Enterprise environment. The server incorrectly reports that the association already exists.
- BUG-000147765 - Certification of Microsoft ODBC Driver 18 for SQL Server connections.
- BUG-000147713 - Validating topology on specific dirty areas in a customer utility network fails with a generic error.
- BUG-000147630 - Using the Modify Associations pane in a versioned data results in a long delay, and fails with a deadlock error.
- BUG-000147611 - Unable to display labels for ArcGIS Server map services if the Clipping and Image Spatial Reference parameters are filled.
- BUG-000147316 - Arcpy based print service fails to add a table from a map service with aMap.addDataFromPath() function.
- BUG-000147165 - Date/time values do NOT get converted to UTC for XY Event layer when the source is a query layer.
- BUG-000146998 - Restoring a row via Conflict Manager may create a scenario where dirty areas become out of sync.
- BUG-000146789 - The Export Subnetwork tool fails and returns the error message, "Operation is only allowed by the owner of the version" unless the user is the owner of the version or the version access is public.
- BUG-000146762 - Reduce network traffic between the database and server when running the Update Subnetwork tool.
- BUG-000146752 - Relating a branch versioned point to a related table record in a child version does not display in the Version Changes window when the relationship class is attributed.
- BUG-000146650 - The contingent values are not ported over when switching from the default version to a child version using the Contents pane.
- BUG-000146481 - Post with ASYNC permits editors to post to protected DEFAULT
- BUG-000146391 - The cartographic realignment of a route with a high number of vertices and multiple time slices is taking an excessive amount of time to complete.
- BUG-000146342 - The Utility Network service fails to start with the error message, "The dataset name is invalid" returned.
- BUG-000145428 - Branch versioning reconcile trim delete statement optimization to avoid full fetching all rowids in the sublineage (removing NOT IN subquery)
- BUG-000145357 - Propagation not working correctly for lines connected to the same terminal on a device with multiple terminals
- BUG-000145334 - A dirty area returns "Status 9" after validation when the errors are created (expect '8').
- BUG-000145322 - Update Subnetwork fails with 999999 "Arithmetic overflow error converting float to data type numeric."
- BUG-000145060 - Provide a way to disable post processing in validate (marking subnetwork controllers as dirty)
- BUG-000144988 - Editing a centerline that is a curve that is not associated with a route throws a 3D error
- BUG-000144877 - System is failing to write the burn-in propagated values to phasesenergized field
- BUG-000144700 - The error, 'insufficient permissions', can occur on reconcile if the service was published by a database user which does not have permissions to a Utility Network present in the same database by another database user schema.
- BUG-000144689 - When an export map request including a definition expression on an invalid map layer is performed on a dynamic map service, the service returns incorrect query results until it is restarted.
- BUG-000144666 - Long running Save Edits operation in branch version results in ArcGIS Pro error "Save Edits Failed".
- BUG-000144593 - V3 Utility Networks regenerate Association Dirty Areas in incorrect locations
- BUG-000144420 - Reconcile fails with collation conflict error when database collation is different than instance collation.
- BUG-000144240 - Export Subnetwork taking a long time on specific utility network
- BUG-000143940 - Validate Network Topology (async) does not include Success flag to statusUrl when "Success = true"
- BUG-000143892 - Reconcile failed on v3 with (an expected field not found)
- BUG-000143529 - Error occurs when running "service area analysis" tool: Error DBMS table not found Invalid object name 'sde.sessions_137833_5'
- BUG-000140779 - When reconciling edits on a feature service with a set time zone, date type fields display incorrectly in the Conflict Manager.
- BUG-000136842 - Using the Identify tool in the ArcGIS Server Rest API returns one result if a layer is configured as a raster layer.
- BUG-000135875 - Unable to apply a layer definition to Mosaic Dataset map service layers when published from ArcGIS Pro.
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.
The ArcGIS Server 10.9.1 Setup Program Patch is a mandatory prerequisite for installing this patch on Windows. Please download and install the ArcGIS Server 10.9.1 Setup Program Patch before attempting to install this patch.
- Download the appropriate file to a location other than your ArcGIS installation location.
ArcGIS Enterprise 10.9.1 ArcGIS Server ArcGIS-1091-S-UNDM3-Patch.msp Checksum
(SHA256)4DCAE28D88B1CD4909D46D58684D64E51D5F8DE2D59A91DE4032B8F940D22901
- Make sure you have write access to your ArcGIS installation location.
- Double-click ArcGIS-1091-S-UNDM3-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-1091-S-UNDM3-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.
- Download the appropriate file to a location other than your ArcGIS installation location.
ArcGIS Enterprise 10.9.1 ArcGIS Server ArcGIS-1091-S-UNDM3-Patch-linux.tar Checksum
(SHA256)8D131070F10FD44165D3F6718C707B4A0FAC0B49C54AFBAF16A1976C62D59992
- Make sure you have write access to your ArcGIS installation location, and that no one is using ArcGIS.
- Extract the specified tar file by typing:
% tar -xvf ArcGIS-1091-S-UNDM3-Patch-linux.tar
- 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 depending on the nature of fixes included. See the Upgrade the Geodatabase section on the Geodatabase management page for your individual DBMS platform for more information. Executing the steps below will not cause any harm if your geodatabase is already at the required level, so the recommended approach is to follow the steps as outlined. If your database is already at the required level, you will get a message indicating so.
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")
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
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.
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.
Download ID:8077
Get help from ArcGIS experts
Download the Esri Support App