Recently, I was creating OIM Flat File GTC Connector and in the process of configuring it right faced some errors. There are some good sources on basic configuration steps already on web so not going to explain it again. For detailed steps check below blogs -
Here are some of the issues I faced during configuration -
1. Flat File used for feeding must have first line as some comment instead of actual header attributes. For Ex:
# GTC Flat File Feed
login|firstname|lastname|eMail|organization
PDIAZ|Petric|Diaz|p.diaz@oracle.com|Xellerate Users
2. While creating mapping between Reconciliation Staging table and OIM table, select matching only checkbox for User Login Attribute.
3. Map the Role attribute to the "Code" that exist in the lookup "Lookup.Users.Role". For Ex: I was providing the "Employee" as the value for "Role" but in "Lookup.Users.Role" there is no code exists for "Employee" and code value is actually "EMP".
So, either use the codes that are already available or create new ones based on the requirement. If the code doesn't exist then you will see the error -
"Notes:ERROR: Given User Employee Type in the Column: RECON_USR_EMP_TYPE is Invalid" in the Reconciliation Event Management screen (System Configuration -> Scheduler -> Event Management -> Search Reconciliation Events).
4. If you see below errors in OIM server diagnostics logs -
Thor.API.Exceptions.tcAPIException: oracle.iam.reconciliation.exception.ReconciliationException: Invalid Profile - OIM_FLATFILE_RECON_GTC
Caused by: org.xml.sax.SAXParseException; cvc-minLength-valid: Value '' with length = '0' is not facet-valid with respect to minLength '1'
for type 'matchingRuleType'.
It can come due to various reasons like recon profile or rules not created. Always regenerate the recon profile if you make any changes in the GTC connector config or mapping rules.
5. For below error in OIM server diagnostics logs -
MisfireHandler: Error handling misfires: Unexpected runtime exception: null OIM
See blog - http://yourhelperall.blogspot.com/2013/05/reconciliation-issue-misfirehandler.html
- http://rite-oim.blogspot.com/2013/07/flat-file-reconciliation-oim-11g.html
- http://www.iamidm.com/2012/09/oim-11g-r2-lab-3-flat-file-recon-to.html
Here are some of the issues I faced during configuration -
1. Flat File used for feeding must have first line as some comment instead of actual header attributes. For Ex:
# GTC Flat File Feed
login|firstname|lastname|eMail|organization
PDIAZ|Petric|Diaz|p.diaz@oracle.com|Xellerate Users
2. While creating mapping between Reconciliation Staging table and OIM table, select matching only checkbox for User Login Attribute.
3. Map the Role attribute to the "Code" that exist in the lookup "Lookup.Users.Role". For Ex: I was providing the "Employee" as the value for "Role" but in "Lookup.Users.Role" there is no code exists for "Employee" and code value is actually "EMP".
So, either use the codes that are already available or create new ones based on the requirement. If the code doesn't exist then you will see the error -
"Notes:ERROR: Given User Employee Type in the Column: RECON_USR_EMP_TYPE is Invalid" in the Reconciliation Event Management screen (System Configuration -> Scheduler -> Event Management -> Search Reconciliation Events).
4. If you see below errors in OIM server diagnostics logs -
Thor.API.Exceptions.tcAPIException: oracle.iam.reconciliation.exception.ReconciliationException: Invalid Profile - OIM_FLATFILE_RECON_GTC
Caused by: org.xml.sax.SAXParseException; cvc-minLength-valid: Value '' with length = '0' is not facet-valid with respect to minLength '1'
for type 'matchingRuleType'.
It can come due to various reasons like recon profile or rules not created. Always regenerate the recon profile if you make any changes in the GTC connector config or mapping rules.
5. For below error in OIM server diagnostics logs -
MisfireHandler: Error handling misfires: Unexpected runtime exception: null OIM
See blog - http://yourhelperall.blogspot.com/2013/05/reconciliation-issue-misfirehandler.html
