Geodatabases stored in the schema of a user other than the sde user in Oracle are not entirely self-contained; there is some functionality, such as user-defined types, that are only in the master sde geodatabase. For that reason, you cannot treat geodatabases in users' schemas as their own entity, and the following rules apply:
- You must upgrade the master sde geodatabase before you can upgrade a geodatabase in a user's schema.
- You can upgrade the master sde geodatabase without upgrading the geodatabases in other users' schemas, but you cannot upgrade a user's geodatabase without upgrading the master sde geodatabase.
- You cannot create a backup of only a user's schema and have a complete geodatabase; there are dependent objects, such as user-defined types, in the master sde geodatabase that must be part of the backup.
- When you upgrade a geodatabase in ArcGIS Pro, the geodatabase version contains both the ArcGIS Enterprise and ArcMap version number and the ArcGIS Pro version number. For example, if you upgrade a master geodatabase using ArcGIS Pro 2.4, the version in the master geodatabase will be 10.7.1.2.4. To upgrade user-schema geodatabases in this master geodatabase, you would also have to use ArcGIS Pro 2.4.