Troubleshooting - Oracle HCM

Troubleshooting

For common issues that apply to all connectors — authentication failures, syncs stuck or not progressing, no documents indexed, stale permissions — see Troubleshooting - Enterprise Search Connectors.

Incremental sync fails with "perform a full sync" message

Symptoms: Incremental sync fails immediately with a message that a full sync is required.

Possible causes:

1. No sync cursor exists from a prior successful full sync.

Resolution:

1. Run a full sync from Enterprise Search → Oracle HCM → Status.

2. After the full sync completes successfully, incremental sync resumes automatically every 2 hours.

Sync completes with fewer records than expected

Symptoms: Indexed document count is lower than the learner assignment count visible in Oracle HCM.

Possible causes:

1. Integration account lacks Oracle data security access to some records

2. Advanced filter rules are narrowing ingestion scope

3. Document-level security is enabled and the searching user's email does not match assignee emails

Resolution:

1. Verify the integration account role and data security privileges in Oracle HCM

2. Confirm the searching user's work email matches assignedToPersonPrimaryEmailAddress on the records

User cannot see their own learning assignments (DLS enabled)

Symptoms: A learner can see assignments in Oracle HCM but not in Simpplr search.

Possible causes:

1. The user's Simpplr identity email does not match assignedToPersonPrimaryEmailAddress on the record

2. The assignment record has not been synced since the email was set or changed

3. The record has no assignee email in Oracle HCM

Resolution:

1. Confirm the user's work email in Simpplr matches Oracle HCM

2. Wait for the next incremental sync (runs every 2 hours), or trigger a manual sync from the Status page

Full sync takes a very long time or fails on large tenants

Symptoms: Initial full sync runs for many hours, stalls, or fails partway through.

Possible causes:

1. Very large number of learning items and assignment records

2. Oracle HCM API throttling or transient errors during high-volume reads

Resolution:

1. Allow additional time — large tenants can take several hours on the first full sync

2. If the sync fails, trigger a manual full sync from the Status page; the connector retries failed API calls automatically

Deleted assignments still appear in search

Symptoms: An assignment removed in Oracle HCM still appears in Simpplr search.

Possible causes: Incremental sync has not run since the deletion

Resolution: Wait for the next incremental sync to complete, or trigger a manual sync from the Status page