# Troubleshooting

If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information:

- [SailPoint Identity Services Documentation](<https://documentation.sailpoint.com/saas/help/index.html>)
- [SailPoint Support Knowledge Base](<https://support.sailpoint.com/csm?id=kb_view2&amp;kb_id=05ff44289f011200550bf7b6077fcfa3>)
- [SailPoint Developer Community](<https://developer.sailpoint.com/>)

## After upgrading or during create operation, the following error messages display:

### Ensure that the useEnhancedAggregation attribute is set to true and an EBS Proxy user is set for sptProxyHRMSEBSUser

**Resolution**: Set the value of `useEnhancedAggregation` attribute to `true`, using the REST API.

### Only creation of employee person type is supported

**Resolution**: Ensure that the PERSON\_TYPE attribute is set to Employee as the creation is supported only for PERSON\_TYPE Employee.

### You have tried to enter an employee without entering a value for their gender

OR

`Person type is mandatory to create employee`

OR

`Add mandatory fields to create employee`

**Resolution**: Provide valid values for each of the mandatory fields in [Creation/Updation of Employee Records in Oracle HRMS System](<https://documentation.sailpoint.com/connectors/oracle/hrms/va/help/provisioning.html#default-create-account-attributes>).

- FIRST\_NAME
- LAST\_NAME
- JOB
- PERSON\_TYPE (Should be set to Employee)
- GENDER

## After upgrading or during disable employee operation, the following error messages display:

### Ensure that an EBS Proxy user is set for sptProxyHRMSEBSUser

**Resolution**:

- To disable an employee, ensure that you set an EBS Proxy user for `sptProxyHRMSEBSUser`.
- The feature string **ENABLE** must be added in the application debug page for disable operations.

### Disable operation is supported only for person having type as employee.

**Resolution**: Ensure that the disable operation is triggered for an Employee as the feature is supported only for PERSON\_TYPE Employee.

### ORA-00942: table or view does not exist

**Resolution**: Ensure that the service user has the required minimum permissions.

## During email and phone updates, the following error message displays:

### It is recommended to set up a proxy user for email and phone update operations.

Set the value of `useEnhancedAggregation` attribute to `true`, using the REST API.

> [!NOTE]
>
> For more information on SailPoint's REST APIs, refer to [Best Practices: REST API Authentication](<https://developer.sailpoint.com/docs/api/authentication/>) and [REST API - Update Source (Partial)](<https://developer.sailpoint.com/docs/api/update-source-v-1/>) in the SailPoint Developer Community.

## During aggregation, the following error message displays:

### Only some users are being aggregated

**Resolution**: The Oracle HRMS connector only aggregates organizational data with active person assignments. Review whether or not the users have valid organizational data.

### The aggregation filter is not fetching accounts when useEnhancedAggregation is true

When the `useEnhancedAggregation` value is true in the application, the connector uses the HR\_ALL\_POSITIONS\_F table to get position data. If the table doesn't have any data then aggregation will not bring any data. By default, the connector aggregates only organizational data with active persons and assignments. If there's a requirement to aggregate personal data, values must be changed.

**Resolution**: Set the `aggregateOnlyOrganisationData` and `useEnhancedAggregation` values to false.