User group error when migrating database from 7.2 to 9.6

Hi Erik,

I did some tests on renaming users and user groups, but the only way I found was to do it one register at a time. I hope there's some other way, it would be really useful after a migration process.

Having said that, I'm also interested in sharing how people are dealing with the new user management system and the user consolidation.

In my case, we are in the middle of the migration process to ARIS 9.6 with a lot of databases organised by countries and a team of DB administrators with assigned databases in their area of influence. Without the user restriction by database, any administrator can see (and modify) the access permissions of all the users in the system.

The only idea we've come up with to manage this is adding the name of the database to the name of the user groups in order to use the filters. In the case of the users, this gets more difficult as the number is quite high.

Maybe we are missing something here, but the fact that the users are not "pre-filtered" by database once you enter the tool will be a problem for us.

Kind regards,

Enrique

Hi Erik,

I had exactly the same problem.  My situation is that we had installed 9.6.0.1.1 and migrated all our databases over.  This worked fine and all the users and user groups were migrated as expected.

We then had reason to upgrade to the latest service release 9.6.0.3.2.  To do this we uninstalled business designer and installed the service release.  When the server was reconfigured and attached to our SQL Server database all the databases we previously restored were still there and everything looked fine.  We subsequently restored our databases again and that is when the new user groups were created with the naming you explained in your post.  After the restore we had all our original user groups plus an equal number with the _T15_<number> format.  When we tried to export a database to business publisher, only the _T15_<number> groups went across as profiles.

So everything worked fine for us in 9.6.0.1.1 but we get the same problem you have when we restore databases with 9.6.0.3.2.

Thank you for your replies!

Our version is 9.6.0.3.9.

Noticed today also that a few groups have been merged, there are groups on the new server that simply doesnt exist in any database at any database. After some investigation it seems that a few user groups have merged. This also means that users in the merged groups have gotten new access rights.

I will probably rebuild the user groups from scratch as I don't hav that many users, but for those of you with large user groups, this is really something to be aware of and control after the migration.

By the way, its possible to rename users and grous in 7.2 but I cant do it in 9.6 Which would be really useful due to the new user group structure. Annoying!

@Graham: What user were you using when doing the database import? I remember that i didnt use "system" but a personilized admin account.

 @Enrique: How did you rename users/user groups? in UMC?



 

Hi Erik,

Global support confirmed it is a bug that they plan to fix for the next service release.  They have a solution that allows, in a round about way, to rename the groups. If you have a maintenance contract, consider creating an incident on their system and they can help you.

I was importing our 7.2 database using the "system" account.

Graham

Ok, thanks for the information.

/ erik