Issue Description:
Sometimes when we provision some target resource in OIM 11g R2 PS1, we can see from the log that tasks got triggered which are responsible for creating the account but when we go to "Accounts" tab for that user, we don't see that Target Resource instance there.
Root Cause - Missing Application Instance Key:
Look for the entry in OIU table for that user, you would be able to see that data exists in the table but still it is not visible on the screen. Look for APPLICATION_INSTANCE_KEY column, you would see NULL.
Solution:
Populate that column with correct "Application Instance Key" and Refresh the screen. You can use SQL Query to do that.
OR
We have an OOTB schedule job "Update Accounts With App Instance Job" for updating the Application Instance Key in OIU table.
Question:
Why Application Instance Key is null for few accounts.
Answer:
As per Oracle, here is the explanation:
The application instance might not be available when the account is provisioned. This is possible when:
Sometimes when we provision some target resource in OIM 11g R2 PS1, we can see from the log that tasks got triggered which are responsible for creating the account but when we go to "Accounts" tab for that user, we don't see that Target Resource instance there.
Root Cause - Missing Application Instance Key:
Look for the entry in OIU table for that user, you would be able to see that data exists in the table but still it is not visible on the screen. Look for APPLICATION_INSTANCE_KEY column, you would see NULL.
Solution:
Populate that column with correct "Application Instance Key" and Refresh the screen. You can use SQL Query to do that.
OR
We have an OOTB schedule job "Update Accounts With App Instance Job" for updating the Application Instance Key in OIU table.
Question:
Why Application Instance Key is null for few accounts.
Answer:
As per Oracle, here is the explanation:
The application instance might not be available when the account is provisioned. This is possible when:
- Oracle Identity Manager is upgraded, when app_instance_key is to be populated for all the existing entries in the OIU table.
- Accounts are brought in via reconciliation, but the application instances are not available when the accounts are reconciled. The application instances are created after the reconciliation.
-
Accounts are provisioned via access policies, but the application
instances are not available when the accounts are provisioned. The
application instances are created after the provisioning.
But I believe there may be some other reasons as well for "NULL APPLICATION_INSTANCE_KEY"