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; } } }

Help: I am getting "version missmatch" with dm_UserRename

ecm_newer

Hello all,

Happy new year.

I have to rename almost 3000 users in the docbase due to synchronisation Error. In fact I write some java code with dfc. I am using the method Rename on IdfUser. During the execution of my code, after the 135th user, my code return "version missmatch error".

How can I handle this situation. Like check if the job is complete for first user before call it for the second and so one and so four.

Please advise!!!

Find more posts tagged with

Comments

bacham2

The root of the problem is that another process/user has modified the dm_user object since you fetched it. You can't avoid it completely but you can reduce the chance of this happening. First, make sure that no other job affecting users (e.g. LDAP snyc or user rename) is running. Second, call IDfUser.fetch against your IDfUser object prior to changing any attributes.

ecm_newer

bacham2>>Thanks for your answer.

Do I need to save the user after fetch with the name and call the Job UserRename? like this?

[CODE]

MyCurrentUser.fetch(sUserName);

MyCurrentUser.renameUser(sUserFromIntraSubstitution,true,true,false);

MyCurrentUser.save;

[/CODE]

bacham2

There is no point in calling fetch prior to IDfUser.renameUser since this method doesn't change the user but only queues a request for the dm_UserRename job to handle. No need to save either.

Where exactly do you get the version mismatch error? Is it in the dm_UserRename job or is it in your code? What does your code do exactly?

ecm_newer

I got the error like exception result from the call of the job:

The user XXXXXXXXXXX can not be renamed. Error: [DM_OBJ_MGR_E_VERSION_MISMATCH]error: "save of object 0801068e80000231 of type dm_job failed because of version mismatch: old version was 147"

In my code:

Execute dql query to have the users concerned by this modification and the new name
I made getUser Object
Change The description of this user
Change the objectName of the default folder
set the new name of the folder as the defaultfolder of the old user
save user
Call UserRename;

bacham2

Sounds good. Do you call userRename with isImmediate = T? I would recommend calling it with False, since you have multiple users to update. No need to call it multiple times.

If you don't change the user after calling userRename, there shouldn't be any version mismatch error. Post your code if it's not too long.

ecm_newer

Ok I just post the main part. I also add a control on the status of the jod UserRename before calling it again

for(col = query.execute(my_sessionTmp, 3); col.next();){
                    i_nbrToBeReplaced++;
                    String sUserName = col.getString("userdctm");
                    sUserFromIntraSubstitution=col.getString("dctmintraname");
                    writeOutput(i_nbrToBeReplaced+"- SUBSTITUTION de: " + sUserName +" par: "+sUserFromIntraSubstitution);
                    IDfUser MyCurrentUser = my_sessionTmp.getUser(sUserName);
                    if (MyCurrentUser == null)
                        writeOutput("---------------------->ERROR USER NOT FOUND");
                    else {
                        //get MyCurrentUser the default_folder
                        String strDfaultFolder=MyCurrentUser.getDefaultFolder();
                        IDfFolder userFolder = my_sessionTmp.getFolderByPath(strDfaultFolder);
                        userFolder.setObjectName(sUserFromIntraSubstitution);
                        try{
                            userFolder.save();
                        }catch (DfException dfe) {
                            i_nbrFldExist++;
                            writeOutput("The folder "+userFolder.getObjectName()+" already exists. So it was deleted and replaced. Error: " + dfe.getMessage());
                            //userFolder.

//my_sessionTmp.apiExec("destroy", docId);

How can I destroy the existing folder here and create a new one??

                        }
                        MyCurrentUser.setDefaultFolder("/"+sUserFromIntraSubstitution, true);
                        MyCurrentUser.setDescription(sUserFromIntraSubstitution);
                        MyCurrentUser.save();
                        try{
                            String strInitVstamp=getI_vstamp(my_sessionTmp, "dm_UserRename", "dm_job");
                            MyCurrentUser.renameUser(sUserFromIntraSubstitution,true,true,false);
                            i_nbReplaced++;
                            String strFinalVstamp;
                            /**
                             * Waiting bloc
                             * */
                            do{
                                Thread.sleep(WaitTime);
                                 strFinalVstamp=getI_vstamp(my_sessionTmp, "dm_UserRename", "dm_job");
                            }
                            while(strInitVstamp.equals(strFinalVstamp));

                        }catch (DfException dfe) {
                            i_nbrNonRenamed++;
                            writeOutput("The user "+MyCurrentUser.getUserName()+" can not be renamed. Error: " + dfe.getMessage());
                        }
                    }
                }
                col.close();
                writeOutput("There are "+i_nbrToBeReplaced+" users and "+i_nbReplaced+" replaced and "+i_nbrNonRenamed+" users that not renamed");
            }

I just added the control on the job this modification is due to the error version missmatch. On this way I can handle the version missmatch but the execution will take too long

bacham2

Looks like you are making your life more difficult than it should be. Call renameUser with isImmediate set to false. Remove all the code that is waiting for the job to run. This is very inefficient. Plus if there is a problem with the Java Method Server, it will wait for nothing.

Just process all the users first, and let the job wake up naturally and rename the users all in the same run. Or if you absolutely need to, trigger the job at then end of your processing (after you close the collection).

As a side note, in your query.execute statement, don't use an integer constant (don't even know what '3' means) but use the constants IDfQuery.DF_EXEC_QUERY, etc. This will make your code more readable.

ecm_newer

thank you for your help and your explanations. I apply all your advices

I have one more question:

If I set a new object_name for the default folder et get exception (in save action) because this folder already exist. How can I destroy this folder in with dfc code instead of using mysession.apiExec("destroy", fldId);

bacham2

IDfFolder.destroy()

However, it won't work if the folder contains objects. You will have to move all objects first (including all versions). Some might be checked out, some might be immutable, so it's not straightforward.

ecm_newer

Thank for All.

So I modifie my code link you advise. "Call renameUser with isImmediate set to false. Remove all the code that is waiting for the job to run" so

I make this

[CODE]

MyCurrentUser.renameUser(sUserFromIntraSubstitution,false,true,false);

[/CODE]

But I Saw the job started just after lunching my program. I am still getting the following errors :

[ERROR]
The user John DOE_1 can not be renamed. Error: [DM_SYSOBJECT_E_LOCKED]error: "The operation on dm_UserRename sysobject was unsuccessful because it is locked by user dmadmin."

The user John DOE_2 can not be renamed. Error: [DM_OBJ_MGR_E_VERSION_MISMATCH]error: "save of object 0801068b80000231 of type dm_job failed because of version mismatch: old version was 39"

[/ERROR]

Can you explain me the raison?

bacham2

This happens when the user you want to rename has checked out documents. You can either specify to ignore such objects (parameter in renameUser method) or you need to cancel the checkout of such objects.

ecm_newer

bacham2>> I tried both before (ignore or cancel) but still same missmatch error