# 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/>)

## User with same employee id is not fetched in aggregation

**Resolution**: Add following entries in application, update the source, and retest use case:

```xml
<entry key="useEffectiveDate">
<value>
<Boolean>false</Boolean>
</value>
</entry>

<entry key="aggregateActiveAccounts">
<value>
<Boolean>true</Boolean>
</value>
</entry>
```

## Missing or blank responsibilities under user account attributes after account aggregation

**Issue**: Responsibilities aggregate successfully during entitlement aggregation but appear blank or missing under user account attributes after account aggregation, even though the responsibilities are assigned in Oracle EBS.

**Resolution**: Update the source configuration to enable indirect assignments:

1. Contact SailPoint Support or have your authorized administrator execute a PATCH request using the [Update Source API](<https://developer.sailpoint.com/docs/api/v2025/update-source/>) for the target source ID.
2. In the PATCH request, set `disableIndirectAssignment` to false.
3. After updating the configuration, run the following aggregations in order:

   - Entitlement aggregation
   - Account aggregation
4. Verify that the missing responsibilities now appear under account attributes.

   > **Note**
   >
   > The `disableIndirectAssignment` setting is not available in the SailPoint UI. You must update this setting through the API. Contact SailPoint Support or an authorized administrator to make this change.

## ORA-00918: column ambiguously defined

**Issue**: Error occurred during ORA-00918: column ambiguously defined operation.

`sailpoint.connector.ConnectorException: ORA-00918: column ambiguously defined`

**Resolution**: Remove the `PASSWORD_LIFESPAN_ACCESSES` and `PASSWORD_LIFESPAN_DAYS` attributes from the `Account` schema if they were manually or additionally added. Keep all out-of-the-box (OOTB) attributes unchanged.

## FND\_USER\_PKG error during provisioning

**Issue**: Provisioning fails with the error java.sql.SQLException: ORA-06550: line 1, column 7:\\nPLS-00201: identifier 'FND\_USER\_PKG' must be declared\\nORA-06550: line 1, column 7:\\nPL/SQL: Statement ignored

**Resolution**: The following attribute can be added to the source to disable FND\_GLOBAL.APPS\_INITIALIZE: key=disableInitializeSession value=true

## Provisioning fails with a Custom user name validation error

`"<Message key="[ ConnectorException ] &#xA; [ Error details ] Error occurred during Create operation. Please check the logs. Error: ORA-20001: Custom user name validation in subscription to event oracle.fnd.user.name.vali&#xA;date failed.&#xA;ORA-06512: at &quot;APPS.APP_EXCEPTION&quot;, line 72&#xA;ORA-06512: at &quot;APPS.FND_USER_PKG&quot;, line 4207&#xA;ORA-06512: at &quot;APPS.FND_USER_PKG&quot;, line 1328&#xA;ORA-06512: at &quot;APPS.FND_USER_PKG&quot;, line 1599&#xA;ORA-06512: at &quot;APPS.FND_USER_PKG&quot;, line 1718&#xA;ORA-06512: at line 1&#xA;" type="Error"/>."`

**Resolution**: For Oracle E-Business version 12.2.4 and later, ensure the service account has been provided with the permissions using AD\_ZD.GRANT\_PRIVS API only. For more information, refer to [Support for AD\_ZD.GRANT\_PRIVS Package](<https://documentation.sailpoint.com/connectors/oracle/ebusiness_suite/va/help/additional_information.html#support-for-ad_zdgrant_privs-package>). All other permissions are as outlined in [Required Permissions](<https://documentation.sailpoint.com/connectors/oracle/ebusiness_suite/va/help/index.html#required-permissions>).

## Need to set END\_DATE to NULL value for Modify provisioning operation

Refer to the below sample plan:

```xml
<ProvisioningPlan>
    <AccountRequest op="Modify">
        <AttributeRequest name="END_DATE" op="Set" value="NULL" />
            <Attributes>
                <Map>
                    <entry key="assignment" value="true" />
                </Map>
            </Attributes>
        </AttributeRequest>
    </AccountRequest>
</ProvisioningPlan>
```

The date can also be set to NULL by using the julian date format by passing the END\_DATE value as to\_date('2', 'j').

## Provisioning and Aggregation fails with an error message

```text
sailpoint.connector.InsufficientPermissionException: [ InsufficientPermissionException ] 391 [
Possible suggestions ] Service account does not have sufficient privileges. 392 [ Error details ]
Error occurred while establishing the connection with Oracle EBS Server during Provisioning
operation. ORA-00942: table or view does not exist
```

**Resolution**: Verify the permission mismatch by referring to the [Validating Service Account Permissions on Oracle E-Business](<https://community.sailpoint.com/knowledge/Validating-Service-Account-Permissions-on-Oracle-E-Business>) document.

## RA\_Customers table not found when managing Oracle version 12c

If you are using the SailPoint connector for Oracle ERP - Oracle E-Business Suite to manage Oracle version 12c or later, the Integration Module installation expects a table named `RA_Customers`. This table was renamed to `AR_Customers` in Oracle versions 12c and later.

**Resolution**: Make a synonym for the `AR_Customers` table in Oracle and call it `RA_Customers`.

For example:

```sql
create synonym ra_customers for apps.ar_customers;
```

## A user must be rehired who is disabled in the native system

When a user must be rehired who is disabled in the native system, the following error message appears on the native system:

```text
User already exists
```

**Resolution**: To rehire a user who is disabled in the native system, run an account aggregation. This corrects the account status in SailPoint. Enable the account from SailPoint or the native system.

## A new user with an existing user name on the native system in a disabled state must be newly hired

When a new user must be hired with an old user name that is in a disabled state on the native system, the following error message appears on the native system:

```text
User already exists
```

**Resolution**: The connector does not have the old user details for the account that is disabled on the native system, so the create account request fails. Enter a new name for the new user.

## The create account operation fails with an error

```text
Missing IN or OUT parameter at index
```

**Resolution**: Ensure that all the mandatory fields for create account operations are entered.

## Account aggregation fails with an error

```text
ORA-00980 synonym translation is no longer valid error
```

**Resolution**: Assign new permissions using the following:

```text
alter use ${newuser} enable editions;
```

## Table with columns defined in 'Required Columns' filter is not showing in security extract.

**Resolution**:

- Make sure that the table name with required columns list is also added as table name under the 'Additional Table Filters' section (with or without table filter).
- Also make sure that the Service Account used for connection has right permission to access Additional Tables from database.

> [!NOTE]
>
> **Screenshot**
>
> [![Troubleshooting Additional Table](<https://documentation.sailpoint.com/connectors/oracle/ebusiness_suite/va/help/img/troubleshooting_additional_table_image.png>)](<https://documentation.sailpoint.com/connectors/oracle/ebusiness_suite/va/help/img/troubleshooting_additional_table_image.png>)

## New create and disable users are not fetched in aggregation when Account Aggregation Filters filter set to Aggregate only employees.

**Resolution**: When a user is initially created or disabled there is no responsibility added to it. It is created in fnd\_users table. To aggregate such users set "Account Aggregation Filters" to "Aggregate all users from FND\_USER table in Oracle E-Business".

## Enable Operation Fails with ORA-20001

**Issue**: Enabling the account fails with the following error:

```text
ORA-20001: Description format is incorrect. Correct format is [Position Name]|[GUID].
```

**Resolution**: The enable operation failed because `ebsDescription` was missing the Position Name. Oracle received `|GUID` instead of `Position Name|GUID`.

Update the transform so it populates `ebsDescription` in the format `Position Name|GUID`.