AnsweredAssumed Answered

Geometric Network Error: Network property already exists

Question asked by WarrenDz on May 13, 2019
Latest reply on May 14, 2019 by bnayak-esristaff

We’re experiencing an error with a Geometric Network Database table. We previously opened a support ticket pertaining to this issue when this issue interrupted our Reconcile and Post process. After a support call the resolution at the time was to run the Repair Version Tables and Repair Version Metadata Tools corrected the issue. This solved the problem and proved to be a stable fix as the issue occurred a number of times over the following year. After that period the problem seemed to subside, perhaps due to decreased user activity editing the specific feature classes.

However, the problem has recently arisen again and I have more time to dedicate to troubleshooting the issue (ignorance was bliss). Previously when attempting to perform a reconcile, post, and compres of the database we would receive the following error:

"Error reconciling version SDE_USER.PWS.[
The feature class participates in a geometric network that could not be opened.
Network property already exists. [Property name: 'Junction Count' in the SDE_USER.N_6_Props table]]
3 of 4 versions finished.
WARNING 000084: Conflicts detected, aborting the reconcile.
Reconciling version SDE_USER.FieldEdits with SDE.DEFAULT.
Error reconciling version SDE_USER.FieldEdits.[
The feature class participates in a geometric network that could not be opened.
Network property already exists. [Property name: 'Junction Count' in the SDE_USER.N_6_Props table]]
4 of 4 versions finished.
WARNING 000084: Conflicts detected, aborting the reconcile.
Finished reconcile.
Succeeded at Tue Jul 18 18:27:34 2017 (Elapsed Time: 7.37 seconds)"

Today the error also appeared for users editing the data and attempting to save their edits.

Error dialog when attempting to save edits to a feature class that participates in a geometric network.

I’m hoping to get to the bottom of this and resolve the issue and restore my confidence in the integrity of our database.

 

A couple notes on our environment:

Oracle: v11.2.0.4.0 (11G) AIX 7.1

Geodatabase Version: 10.5.1

We also use infraMAP from iWater (uses runtime engine for 10.5.1) – this application uses geodatabase replicas that are children of a geodatabase version specific for Field Edits.

Outcomes