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:

An error message was displayed while removing the role assigned to the user

Service account does not have permission to revoke <Role>

Resolution: Revoking the role can be achieved by the same user who has granted it.

Test connection fails with an error message

Please enter valid Driver Class

Resolution: Copy the latest ngdbc.jar file in the \identityiq\WEB-INF\lib directory.

An error message is displayed for incorrect value of the VALID_FROM field

SAP DBTech JDBC: [438]: invalid user parameter value: VALID FROM not allowed to be in the past

Resolution: Enter the value of the VALID_FROM field as null to create the account with today's date.

Create Account fails with Invalid Username Error

Invalid Username

Resolution: Double check the USER_NAME field in the Create Profile section to ensure the username does not have any special characters or spaces. For more information, refer to HANA User Name Restrictions.

Uploaded JAR Uses an Unsupported Java Version

Resolution: Use a lower version file such as the SAP HANA SPS4 ngdbc.jar

SAP HANA Aggregation Failure After Database Upgrade

After upgrading the SAP HANA on-premise database from HANA 2.0 SP08 Rev 87 to HANA 2.0 SP08 Rev 89, aggregation fails with the following error:

Error in aggregation 8473e6294b9648d6a3bf7f31c2f121ec: java.lang.RuntimeException - SAP DBTech JDBC: [260]: invalid column name: USER.INVALID_CONNECT_ATTEMPTS: line 1 col 346 (at pos 345) - java.lang.RuntimeException: SAP DBTech JDBC: [260]: invalid column name: USER.INVALID_CONNECT_ATTEMPTS

Exception on iterateObjects for application : SAP HANA SE3 Test1 [source] exception is SAP DBTech JDBC: [260]: invalid column name: CREATOR

Resolution: Verify that the service account has the required permissions to access all relevant system views and tables.

If the issue persists, create a new service account with the appropriate permissions and update the connector configuration accordingly.

Account Deletion Failure

Error: Delete operation does not work.

Resolution: Set the endDateOnDelete key to false, and retry the delete operation.

Public catalog role not removed

Issue: Public catalog role is not removed in user certification.

Resolution: Set the IS_RESTRICTED key to true and remove the public role from the provisioning plan.

Set IS_RESTRICTED:

<AttributeRequest name="IS_RESTRICTED" op="Set">
  <Value>
    <Boolean>true</Boolean>
  </Value>
</AttributeRequest>

Remove the public role:

<AttributeRequest displayValue="PUBLIC" name="CATALOG_ROLES" op="Remove" value="131076"/>

Incorrect Access Sunset Timing for SAP HANADB Users Due to Time Zone Differences

When a role is sunset for SAP HANADB users, the actual expiration time may be incorrect. It might not match the requester's expectations due to how different time zones are processed.

Resolution: The sunset end date will now respect the requester's local time zone (matching their computer's system time) instead of relying on a fixed server time zone.

Examples:

Someone in EST picks end date 10 June → access ends at 12:00 AM on 10 June EST.

Someone in IST picks the same date 10 June → access ends at 12:00 AM on 10 June IST.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.