This content has been marked as final. Show 5 replies
I suggest disable the unique index instead of dropping it using ALTER INDEX <INDEX_NAME> DISABLE command.
Better way to handle this do below
1. disable index
2. update usr_login for deleted user using sql query eg. xx|usr_login and commit it ( update usr set usr_login='xx'|| usr_login where upper(usr_status)='DELETED')
3. enable your index
4. now login to OIM and easily you can create user with the previous user login
In this case your Index is still enbaled so it won't hamper the performancem, because this index is being used in various places for user search.
NOTE: disable any other constraints if required. But, I don't think so. Just disabling unique index will allow you to update"
Ho about using System property ...
User Id reuse property
Determines whether a deleted user account can be reused. To reuse a deleted user account, assign this property a value of TRUE and drop the unique index for the USR_LOGIN column in the USR table and create a nonunique index. To prevent a user account from being reused, assign this property a value of FALSE.