ArcGIS Enterprise Upgrade status

[MyEthiopia]

Hi, 

I recently upgraded our enterprise geodatabase in ArcGIS Pro after the sql database was upgraded. 

All of the database had a status 11.0.0.3.0 except one and I am not sure if it's an issue 

It says " This ArcGIS Pro 3.3.0 - 11.3.0.52636 geodatabase is up to date." Does anyone know why its different from the others ?

[George_Thompson]

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-se...

[MyEthiopia]

Oh that makes sense. Our ArcGIS Server is 10.9.1. We have ArcGIS Server that is federated with portal. I did the last upgrade and my ArcGIS Pro was on 3.3. I guess the other ArcGIS pro version was 3.0.

This will be an issue going forward, correct ? Since we didn't use 2.9?

[George_Thompson]

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....

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.

[MyEthiopia]

Thanks George, 

Is there a way to downgrade to 2.9.

[George_Thompson · Accepted solution]

Nope, once you upgrade the EGDB you CANNOT downgrade.

The only way would be to restore the backup before the upgrade (which should have been taken) then upgrade with the correct client.

There may be the need to bring over any updates since the backup was taken.

[MyEthiopia]

Hi George, 

I have a question for you. We fixed one of the database. But have the other one remaining on the 3.0 instead of 2.9. Everything was working fine until I looked into assigning a new user to the database and connected to the user. Everything seems to work fine in the database except in the new user the feature classes are no longer in a feature dataset and they are missing the icons. This is only true for the none dataowner and admin database. Is this a result of the arcgis pro version ? or 

Thanks 🙂

[MyEthiopia]

Just noticed the user has the same copy of the same data except one is all caps and the other has "evw".

[George_Thompson]

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.

[MyEthiopia]

Hi George, 

We did a back up and restore from the old serve to the new server. The users where created before the back up and restore. We run into a issue where a data owner didn't have access to the database so the database admin edit the user to have access to the sde. One thing I do remember is that the sde user also didn't have access to the data it owned so it was modified to have access after the back up and restore. The issue is relevant both in operator authenticator users and created users except for our IT database manager for some reason he doesn't have issue although his logged in through operator authenticator. Of course the data owners doesn't have an issue. Also the naming structure is similar to the newer enterprise where its sde.featuredatabase due to the 3.3 upgrade