Latest Contributions by George_Thompson

Is the PostgreSQL DB an "Enterprise Geodatabase" (with SDE schema)? If not, you cannot edit the data directly in a database (non-geo): https://pro.arcgis.com/en/pro-app/latest/help/data/databases/databases-and-arcgis.htm#ESRI_SECTION1_A188C2B1C8C54C7DA3233892FC742552 https://esriaustraliatechblog.wordpress.com/2023/02/12/can-i-edit-data-in-a-database-not-enabled-as-a-geodatabase-from-arcgis-pro/ Hope this helps! ... View more

When I see that, it usually means something may be incorrect in the EGDB repository tables. The "_evw" is a versioned view using in traditional versioning. It is automatically created when you version the data. Were permissions to the SDE schema revoked from PUBLIC? What was your restore process? the more details the better. ... View more

Yeah that may be best for this type of issue. ... View more

This would point to the SDE schema still being present but the "data" schema is gone. This can corrupt the entire EGDB. ... View more

This is not an issue per se..... but there may be functionality in the newer version that 10.9.1 cannot take advantage of. I usually suggest having the EGDB match the version of Pro / Enterprise so that you get max capabilities. See the doc below: https://enterprise.arcgis.com/en/server/latest/manage-data/windows/client-geodatabase-compatibility.htm You do not have to keep your geodatabase and ArcGIS clients at the same release, but it is recommended that you do so. Geodatabases and client software are designed to work together, and if you let one get too many releases away from the other, you risk encountering problems or unexpected behavior. This is especially true when you use a mix of client versions at your site. A newer client can create newer dataset types in the geodatabase that older clients cannot access. For enterprise geodatabases, waiting too long between geodatabase upgrades may mean you have to upgrade the underlying database more than once before you can upgrade the geodatabase. ... View more

The one that is "11.3.0.52636" seemed to be upgraded with a Pro 3.3.x client. The other with "11.0.0.3.0" were done with a Pro 3.0.x client. What version of Enterprise did you upgrade to? What was the version of Pro used for the upgrades? Did you use a different version between the EGDB upgrades? Here is a list of Enterprise to Pro versions that match best: https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/share-analysis/geoprocessing-service-compatibility.htm ... View more

There is a known issue that is actively being investigated: https://hubstatus.arcgis.com/ Does not hurt to contact Technical Support to inquire. ... View more

Ok, after the delete, did you see any of the "old" dataset items in the Oracle EGDB? ... View more

Are you copying the data into the Oracle database as the data owner (which appears to be "RETI") via the .sde connection? Or are you trying to load this via a service? ... View more

I do not believe that this is possible. Portal for ArcGIS is required for the hosted datastore. You could do this now, with PostgreSQL databases, enabled as geodatabases, registered with the unfederated server. It would basically be what you are asking for. Especially since you say there are very rigid HA, scalability requirements. ... View more

Ok, weird. I have Pro 3.4.3 and it works fine for me. Publishing to Enterprise 11.4 What is the version of your Enterprise? You may want to work with Technical Support on this issue. ... View more

I would contact Esri technical support for an update on this issue. They can provide the latest. ... View more

I have not seen this unless there is an issue with the Version Management component of the service. Was the only change that you upgraded to Pro 3.4.x and then the Versioning tab was not showing? ... View more