Oracle
1Z0-339 · Question #59
Your customer reports duplicate account creation and the status unexpectedly getting changed along with various data corruption issues resulting due to duplicate processing. They are using…
The correct answer is B. Set the reconciliation batch size (batchSize parameter) to 0 in the reconciliation profile of the affected. Explanation/Reference: https://docs.oracle.com/cd/E52734_01/oim/OMDEV/reconsched.htm#OMDEV3478
Reconciliation
Question
Your customer reports duplicate account creation and the status unexpectedly getting changed along with various data corruption issues resulting due to duplicate processing. They are using push-based connectors to process reconciliation using the processReconciliationEvent API. How can you fix this issue?
Options
- ACheck if related batches are in the Ready For Processing statue by using the following statement:
- BSet the reconciliation batch size (batchSize parameter) to 0 in the reconciliation profile of the affected
- CPerform reconciliation twice if the size of the data is large.
- DModify the field length of these columns from the console and then re-create the recon profile.
How the community answered
(15 responses)- B87% (13)
- C7% (1)
- D7% (1)
Explanation
Explanation/Reference: https://docs.oracle.com/cd/E52734_01/oim/OMDEV/reconsched.htm#OMDEV3478
Topics
#reconciliation batch size#processReconciliationEvent#push-based connectors#duplicate processing
Community Discussion
No community discussion yet for this question.