Troubleshoot Okta Integration Network Application Import Errors
Last Updated:
Overview
Okta generates various import errors depending on the application and the specific data conflict or configuration issue. Identifying the specific error message and applying the corresponding resolution steps resolves these import failures. The following error is an example of an import failure:
UserImportJob: JDBC exception on Hibernate data access: SQLException for SQL [n/a]; SQL state [HY000]; error code [1366]
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Integration Network (OIN)
- Provisioning and Imports
- User Lifecycle Management (LCM)
Cause
Import errors occur due to various reasons, including unsupported character encoding, character limits on specific fields, duplicate data objects, unsupported security group configurations, or agent timeouts. The specific cause depends on the error code generated during the failed import job.
Solution
How is the JDBC exception on Hibernate data access error resolved?
The following error typically occurs with Google Workspace and Microsoft Office 365 when Okta encounters unsupported characters:
UserImportJob: JDBC exception on Hibernate data access: SQLException for SQL [n/a]; SQL state [HY000]; error code [1366]
Okta does not support 4-byte encoded UTF-8 characters. Remove the unsupported characters from the source application to resolve this error.
Resolve the "data too long for column" SQL error.
The following error occurs with Workday when setting up immediate termination reasons:
SQL Error: 1406, SQLState: 22001 - Data too long for column
The character limit on this field is 512 characters. Use regular expressions to add multiple similar immediate termination reasons.
How is the error checking connection out of pool resolved?
The following error indicates an issue with the database connection pool:
UserImportJob: null; uncategorized SQLException; SQL state [null]; error code [0]; Error checking connection out of pool for sourceTxDataSource
Contact Okta Support to reset the import job.
Resolve the incorrect result size error.
The following error indicates duplicate underlying data objects exist:
An error occurred during import. Incorrect result size: expected 1, actual 2
Contact Okta Support for assistance with removing the duplicate data objects.
How is the UnmarshalException parse error resolved?
The following error is specific to Workday integrations:
javax.xml.bind.UnmarshalException- User Import failed with unexpected error msg=XMLStreamException: ParseError at [row,col]:[33,1360383]
Constrained Security Groups (CSG) are not supported with imports. Adjust the security group configuration in Workday to resolve this issue.
Resolve the Provisioning Agent timeout error.
The following error is specific to the Okta Provisioning Agent for Comma-Separated Values (CSV) Directory integrations:
Error while downloading all users: The Provisioning Agent call to downloadUsersPartial failed with an agent timeout. Please check and ensure Provisioning Agent is running.
Follow the instructions in the CSV Directory Import Error article to resolve the timeout.
How is the no matching constant error resolved?
The following error occurs with Zendesk integrations:
UserImportJob: Error while downloading custom objects: No matching constant for [524]
Contact Okta Support for assistance with this error.
Resolve the DataIntegrityViolationException error.
The following error occurs with Active Directory integrations:
org.springframework.dao.DataIntegrityViolationException: could not execute statement ...
Contact Okta Support for assistance with this error.
