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.
Oracle accounts are missing the "CREATE SESSION (ADMIN_OPTION ='NO')" system privilege
Oracle is not adding the "CREATE SESSION (ADMIN_OPTION ='NO')" automatically while creating accounts.
Resolution: The Oracle connector does not automatically add "CREATE SESSION (ADMIN_OPTION ='NO')" while creating an account using the role, it is only applicable while creating an account using the SYSTEM privilege.
Error message is displayed when provisioning SYSDBA and SYSOPER
User entitlements not modified sailpoint.connector.ConnectorException: ORA-01031: insufficient privileges
Resolution: The user must connect with the user as "<username> as sysdba" and the <username> must have SYSDBA privileges.
Error message is displayed during access request
This error message displays when the service user does not have the required permissions available:
[ConnectorException] [Error details] NEW The server encountered an unexpected error while contacting target system. Please check the logs. User entitlements not modifiedsailpoint.connector.ConnectorException: ORA-01924: role 'AUDIT_VIEWER' not granted or does not exist
[ConnectorException] [Error details] NEW The server encountered an unexpected error while contacting target system. Please check the logs. User entitlements not modifiedsailpoint.connector.ConnectorException: ORA-00604: error occurred at recursive SQL level 1 ORA-20997: "ALTER SYSTEM" grants not allowed ORA-06512: at "RDSADMIN.RDSADMIN", line 79 ORA-06512: at line 2
Resolution: Ensure that the roles/system privileges being granted are available for the service user by using the following: WITH ADMIN OPTION=YES.
Error during provisioning
The identity attribute USERNAME does not exist in table
Resolution:The connector performs a Get Object of the provisioned accounts and checks for the USERNAME column in the DBA_USERS table. Ensure that USERNAME is present in the DBA_USERS table.
Test connection gets stuck and does not timeout
The test connection gets stuck, and the connector does not timeout and add the error message in the logs.
Resolution: To help the connection to timeout, add oracle.jdbc.ReadTimeout=10000 to the additionalConnProperties in the source.