I found that when updating user data, I get an error in the logs:

[10/28/20 9:58:24:000 EET] 0000021e UserCore I CWLLG0468I: Checking user MyUser for new updates...

[10/28/20 9:58:24:000 EET] 0000021e UserCore I CWLLG0469I: Fullname for user MyUser has changed. Updating...

[10/28/20 9:58:24:016 EET] 0000021e wle E CWLLG2229E: An exception occurred in an EJB call. Error: PreparedStatementCallback; SQL [update LSW_USR_XREF set USER_NAME = ?,FULL_NAME = ?,PROVIDER = ? where USER_ID = ?]; String or binary data would be truncated.; nested exception is java.sql.BatchUpdateException: String or binary data would be truncated.

com.lombardisoftware.client.delegate.BusinessDelegateException: PreparedStatementCallback; SQL [update LSW_USR_XREF set USER_NAME = ?,FULL_NAME = ?,PROVIDER = ? where USER_ID = ?]; String or binary data would be truncated.; nested exception is java.sql.BatchUpdateException: String or binary data would be truncated.

at com.lombardisoftware.client.delegate.BusinessDelegateException.asBusinessDelegateException(BusinessDelegateException.java:46)

Column Provider = nvarchar(256). But new size of this string from LDAP = 263.

How to resolve this problem? Database - MSSQL

Hello dmytro -

I suspect you have "sanitized" the log messages to replace your true user name with "MyUser" in your example, right?

In any case, how can you be sure that column which is causing the error is PROVIDER and not FULL_NAME?

I suspect you are correct, but the exception you share does not identify which column size is violated.

How do you know the size of the string from LDAP is 263? (what LDAP client/utility are you using to view that)

I do not visit this forum very frequently and I would be asking for more detailed information than you would probably be comfortable providing here in public, so my suggestion to you would be to open a support case and in the problem description ask to alert me (by name).

Hopefully, you are on a supported release (BPM 8.6 reached end-of-support on 30 Sept 2020) or have an service extension agreement

This script solved all problems:

alter table LSW_USR_XREF ALTER COLUMN PROVIDER NVARCHAR(512)

Hi dmytro - as you may be able to imagine, it is not supported to arbitrarily modify the column widths (or other characteristics) of BPM/BAW database table. The approach you took to "solve" that is not the correct/supported approach.

I offered/suggested for you to open a Support case (assuming you have an active Support agreement)

Hi Brad, Unfortunately we are using not supported version - IBM BPM 8.5.6. And this solution worked.