Latest Contributions by AlexanderThurstlic

You should ensure that your enterprise geodatabase version, as well as the version of any connecting ArcGIS clients, is supported with Oracle 19c. Full support for Oracle 19c starts with ArcGIS 10.8. Oracle 19c is support with ArcGIS 10.7.x with a Support patch. Oracle database requirements for ArcGIS The following Technical Article describes the steps for importing an Oracle Data Pump export dump file by schema-- to import the SDE schema first to the new 19c database and check for any invalid SDE objects prior to running the full import. How To: Perform schema restores of an Oracle enterprise geodatabase ... View more

Hi Killian.  You can still open a support ticket so that we can check your system environment details and utility network versions against what was logged in the defect.  If appropriate, your support case can be attached to the already logged defect for easier tracking. ... View more

Security folder > Logins > double-click on 'sde' login or other data creator logins > 'Server Roles' Is the sde login a member of the sysadmin server role? ... View more

Hi Charles, In SQL Server Management Studio, connect to the instance hosting the geodatabase: Security folder > Logins > double-click on 'sde' login or other data creator logins > User Mapping Does the Default Schema match the User name?   ... View more

Hi Charles,  Users who create data must have a default schema in SQL Server with the same name as their database user name. For example, if you have a user called 'GIS' mapped to the database, you will need to ensure in SQL Server that the user's default schema name is also 'GIS'.   Also, that user cannot be part of the 'sysadmin' fixed server role, since any user in that role will have the 'dbo' schema by default. ... View more

Hi Charles, This is a known limitation when working with branch versioned datasets in SQL Server.  The Version Management capability will not be available if the datasets that you have registered as versioned using the Branch versioning type are owned by dbo. When working with SQL Server databases, version management cannot be enabled if the data being shared is owned by a dbo user. It is recommended that dbo users do not own any datasets in your enterprise geodatabase. https://pro.arcgis.com/en/pro-app/help/sharing/analyzer-error-messages/00277-version-management-is-enabled-but-the-connected-geodatabase-user-is-not-the-branch-versioned-f.htm Additionally, the 'sa' user is the server administrator and will be part of the sysadmin fixed server role in the SQL Server instance.  All members of this role are considered dbo users. In the geodatabase, that means all data owned by server administrators are owned by dbo and stored in a schema named dbo, even if you set up with SDE as the geodatabase administrator and owner of the geodatabase repository.   http://desktop.arcgis.com/en/arcmap/latest/manage-data/gdbs-in-sql-server/geodatabase-administrator-sqlserver.htm ... View more