Arcgis Pro 2.9 Freezes when editing postgresql 13 geodatabase

Question

We are having a problem with Arcgis Pro 2.9 freezing (just hangs) when editing feature classes in a traditional versioned enterprise geodatabase in Postgresql 13.3.

We run a reconcile/compress process and rebuild indexes nightly using a python script so the states are kept down to a minimum.

When reviewing the sde_intercept logs, when pro hangs, I see the following notation in the log:

[W 14:37.951] Command:      GetstreamError

[W 14:37.951] Long:         1

[R 14:37.951] Long:         -51

[R 14:37.951] NString:      "ERROR:  cursor "sdecur_78212_1464" does not exist"

[R 14:37.951] NString:      "SQLSTATE=34000"

We have an ESRI support ticket open, but we haven't found the solution yet.

Thanks in advance for any insight you might have.

sondickerson · Answer

Another observation in the database logs -

could not receive data from client: An existing connection was forcibly closed by the remote host.

This is due to the use closing the client (ArcGIS Pro) due to it freezing.  We've been using arcgis server services for editing just to get by.  We'd prefer to use direct connects in ArcGIS Pro but with it inconsistently freezing during the editing process, it has become an unreliable client.

sondickerson · Answer

We migrated the databases from sqlserver to postgresql 13.3 and all geodatabases are set to 10.9.1.2.9 – which matches the current ArcGIS release.  These are the steps we followed for the migration.

run reconcile/compress script for database - get the states down to 1
export xml for data and schema using pro
create enterprise geodatabase
run sql statement in pgadmin that establishes owner role and schema for the enterprise geodatabase and enable the postgis extension
import the xml into the new database using pro
replace relationship classes - due to fieldname changes from mixed case to lowercase
apply permissions using pgadmin
Run script to disable edit tracking
editing column fix - run python script
Run script to enable edit tracking
set up versioning in pro
verify the connections and data

George_Thompson · Answer

That is a good start. This one may be a little tough to troubleshoot on the forums.

Did you upgrade the geodatabase to the equivalent Pro 2.9.x version?