Userimport job taking more time to complete by using the modifyuserdata json

[saimeghana]

Hi Team,

We are copying the email value from email attribute to customproperty by using the sav4savrest MODIFYUSERDATAJSON.

we configured the userimport job which is taking the 1 hour 30 minutes to complete, to reduce the time we used the below json, still we see this job is taking 30 minutes to update for 1 user.

Complete Json:

{
"ADDITIONALTABLES": {
"USERS": "SELECT USERNAME,ENTITY,CUSTOMPROPERTY60,CUSTOMPROPERTY3,EMAIL,STATUSKEY FROM USERS WHERE CUSTOMPROPERTY60 IS NULL"
},
"COMPUTEDCOLUMNS": [
"CUSTOMPROPERTY60"
],
"TABLEINDEXES": {
"CURRENTUSERS": [
"USERNAME",
"CUSTOMPROPERTY3",
"STATUSKEY",
"CUSTOMPROPERTY60"
],
"NEWUSERDATA": [
"USERNAME"
]
},
"PREPROCESSQUERIES": [
"UPDATE NEWUSERDATA u1 left join currentusers u on u1.username=u.username set u1.customproperty60 = (case when (u.email IS NOT NULL and u.STATUSKEY='1' and u.customproperty3 IS NULL and u.customproperty60 IS NULL) THEN u.email ELSE u.customproperty60 END)"
]
}

Please help us to resolve this issue.

Thanks,

Sai Meghana

[dgandhi]

Where are you limiting this query for just 1 user? 

[saimeghana]

Hi Devang Gandhi,

No i didn't specified any particular user, but in the environment their is only 1 user where it need to updated, still it is taking more time.

Thanks,
Sai meghana

[Amit_Malik]

@saimeghana ,

We are copying the email value from email attribute to customproperty by using the sav4savrest

can't you do it in the actual user import job rather sav4sav? 

In logs, can you check what is taking time , the query you have written or post that.

I believe if you have 50-60 k users , it will take this much time.

In order to run the Saviynt for saviynt for lesser users, you need to restrict it upfront. in getUsers call

Something like (Sample Only)

/ECM/api/v5/getUser

{"userQuery": "user.email !=user.customproperty60",
"responsefields":["username","departmentNumber","departmentname","owner","customproperty5","custompropertY10","customproperty1","customproperty29"]}

[rushikeshvartak]

Instead of cp60, use a column that is indexed. Please raise support ticket to find which column is indexed on db level