Insert Custom System Property in OIM Database Table

Manually inserting a property into the PTY table.

Insert into PTY (PTY_KEY,LKU_KEY,PTY_KEYWORD,PTY_VALUE,PTY_NAME,PTY_SYSTEM,PTY_LOGINREQUIRED,PTY_RUN_ON,PTY_DATA_LEVEL,PTY_CREATE,PTY_CREATEBY,PTY_UPDATE,PTY_UPDATEBY,PTY_NOTE,PTY_ROWVER) values (PTY_SEQ.nextval,null,'EnvironmentName','ETS','Environment Name',null,'1',null,2,systimestamp,1,systimestamp,1, EMPTY_CLOB(),'0000000000000000');

The Unlock Job is not in Sync

By default any Password policy including Default Policy are set to Permanent Lockout, which disables the Unlock Job.
- The user can only be unlocked by Admin Users manually when Permanent Lockout is set.


To configure the Password Policy and the job to be in sync do the following for each Password Policy:

1. Log in as xelsysadm in OIM Identity UI

2. Click on Manage tab >> Policies icon >> Password Policies selection.

3. Select a Password Policy to edit

4. Ensure that "Permanent Lockout" is unchecked.

5. Set the Lock Duration to the total time for the lockout. Example: 30 minutes.

6. Save and repeat for each policy.

7. Log in as xelsysadm in the OIM sysadmin UI

8. Click on Scheduler

9. Search for Automatically Unlock User job

10. Set the job to run periodically.
- OOTB it is set to once daily
If you set it to every 5 minutes, then the job will "check" every five minutes to see if anyone is locked, if if so, has the Lock Duration has been met.
- so if Duration is 30, then on the 6th time it checks, the user would be unlocked.

The period of the job should be less than or equal to the smallest Lock Duration of the password policies that are active.

Basic Perfomance Tuning For stuck threads and response times

Documentation for performance tuning: https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.4/asper/redundant-cross-references-remo...