nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcSDE 10 upgrade - "Database user name and current user schema do not match"

ForteConsulting

I am trying to upgrade a sql server geodatabase from sde 9.3 to 10. SDE is installed on one machine, and SQL Server with the geodatabase is installed on a different server. The SQL Server native client is installed on the machine with ArcGIS Desktop v10sp2 and ArcSDE v10. When I create a direct connection to the geodatabase using ArcCatalog v10sp2 and the sde login, the prerequisites check runs successfully, the sde tables and procedures were updated, but the log window finishes with "Database user name and current user schema do not match." and then Upgrade failed.

The SQL server 2005 database is owned by a network account . It has an sde user (with associated login and schema) which is part of db_owners. There is also another user called geodata which is part of db_owners, has a login of the same name as well as schema. Most of the data in this geodatabase is in the geodata schema e.g. GEODATA.PARCEL_FABRIC. There is, however some data that is simply stored in the dbo schema e.g. dbo.NewWater.

After the upgrade failed as the sde user, I attempted the upgrade again as both the database owner and the GEODATA user, each time resulting in the same message.

Can you suggest changes that I could implement that would allow the database upgrade to complete successfully?

Thanks,

Patricia

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

NanaDei

Hi Melinda,
Can you please shed light on the "underlying problem"?
1. Was "Database user name and current user schema do not match" noticed in the upgrade log, though the process seems to have been completed successfully with the 'sa' user?
2. Is the "Database user name and current user schema do not match" prompt returned when creating new feature classes or tables from ArcCatalog?

Thanks

MelindaCampbell

I'm having the same issue. I was able to upgrade my database by connecting as the sa user. But, I would like to know how to fix the underlying problem.

How did you end up completing your upgrade? Were you able to fix the problem or did you connect as sa and upgrade?

Thanks,
Melinda

EugeneYang

Is your database SDE schema or DBO schema?

User must have sysadmin role to upgrade geodatabase on SQL Server. We specifically do not allow 'sde' user to upgrade geodatabase even if the 'sde' login has sysadmin privilege.

You can try again with a user, other than 'sde', who has sysadmin role, or try as 'sa' user.

LindseyKnapp

Thanks Vince. I did not notice that the first time I read it. "ArcSDE 10 or ArcSDE Service Pack 1 must be installed before you can install ArcSDE 10 Service Pack 2."

VinceAngelo

All Esri service packs are cumulative (SP2 includes SP1). This is also true of SQL-Server.
The Esri-supported releases of SQL-Server 2005 are SP2 and SP3.

- V

LindseyKnapp

Did you install sp1? For ArcSDE 10 both must be installed. Sp2 does not contain the sp1 fixes.

ForteConsulting

Are ArcSDE 10 sp1 and 2 installed? This is where I would look first. I had a similar problem last week and installing both packs worked.

I have installed SP2 and that did not fix the issue.

LindseyKnapp

Are ArcSDE 10 sp1 and 2 installed? This is where I would look first. I had a similar problem last week and installing both packs worked.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.