Error code 1461 during Crowd synchronization of Confluence or Jira Data Center

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

If Crowd is being used as LDAP for Confluence and/or Jira, the synchronization may fail with the error:

SQL state [72000]; error code [1461]

This issue is specific to Oracle Database.

Environment

  • Confluence 9.2.1

  • Oracle 19c

  • JDK 17

  • Ojdbc driver version 11

Solution

  1. Run Confluence 9.2.1 and Crowd 613

  2. Ensure that Crowd uses Oracle 19c with Ojdbc11.jar

  3. Create some user directories in Confluence, linking with Crowd users

  4. Try to synchronize from directories section of Confluence

The synchronization may fail with error:

ORA-01461: A LONG value can only be bound for insertion into a LONG column update cwd_synchronisation_status set directory_id=?, node_id=?, node_name=?, sync_start=?, sync_end=?, sync_status=?, status_parameters=?, incremental_sync_error=?, full_sync_error=? where id=?]; SQL state [72000]; error code [1461]; Caesium-2-3 INFO [atlassian.crowd.directory.DbCachingRemoteDirectory] failed synchronisation complete for directory [ 655361 ] in [ 190037ms ] Caesium-2-3 DEBUG [crowd.dao.directory.DirectorySynchronisationStatusDAOHibernate] Updating object: DirectorySynchronisationStatusImpl[id=983269426, directory=655361, startTimestamp=1742379437106, endTimestamp=1742379627167, status=FAILURE, statusParameters=, incrementalSyncError=null, fullSyncError=HibernateJdbcException: JDBC exception on Hibernate data access: SQLException for SQL [update cwd_synchronisation_status set directory_id=?, node_id=?, node_name=?, sync_start=?, sync_end=?, sync_status=?, status_parameters=?, incremental_sync_error=?, full_sync_error=? where id=?]; SQL state [72000]; error code [1461]; could not execute batch; nested exception is org.hibernate.exception.GenericJDBCException: could not execute batch, nodeId=c2191b4b-a5d1-421f-98d9-ff40211979bb, nodeName=]

Switch Ojdbc version to resolve

Instead of Ojdbc11.jar, use Ojdbc10.jar or Ojdbc17.jar.

If you encounter further issues on Ojdbc17, try Ojdbc19.jar, which should not cause any issues.

Updated on May 19, 2025

Still need help?

The Atlassian Community is here for you.