Geir Otto Olsen (THInc Consulting AS) asked a question.

March 4, 2026 at 11:31 AM
PRO2 sql-width problem

12.8

6.5

I have done

dbtool kif 2 20% all all

All fixed, then I did a PRO2 UX and made a new target-diff that I read into SQL.

 

Still not fixed, what more do I need to do to get rid of the errors?

 

  1. 03-04-2026 12:22:48 - Replication Procedure for kif.Utskrift encountered an error:Table kif.Utskrift: Record 0x0000000000006053 - Error Copying Record to SQL:
  2. You tried to compare or to update a character field with a value longer than the maximum length. (6182)
  3. Field num: 3, value: Rapport alle kategorier|. (2651)
  4. Could not update field 'beskrivelse' of target in a BUFFER-COPY statement. (5368)
  5. 03-04-2026 12:22:48 - Thread Error: Thread: 2 - Thread Type: REPLICATION - Error: Replication Procedure for kif.Utskrift encountered an error:Table kif.Utskrift: Record 0x0000000000006053 - Error Copying Record to SQL:
  6. You tried to compare or to update a character field with a value longer than the maximum length. (6182)
  7. Field num: 3, value: Rapport alle kategorier|. (2651)
  8. Could not update field 'beskrivelse' of target in a BUFFER-COPY statement. (5368)

 

  • 2 answers
  • 84 views

  • Dmitri Levin (Customer)

    That is a common error for SQL ( I guess you mean MS SQL Server, but in Oracle it is the same). What you can do is compare the largest width you have on OpenEdge side, either looking at the schema, since you did run dbtool or checking the data. And compare that width with the schema in MS SQL Server itself. I do not know what Pro2 UX does. But just check in SQL Server side to make sure the desired changes are there. Schema-holder DB will also need to be updated I guess.

  • Geir Otto Olsen (THInc Consulting AS)

    Sorry, my refer to Pro2 UX is the new user interface that Pro2 now have... I said " I did a PRO2 UX..." I really meant the steps needed to be done getting a target diff between source/target. I do not find it intuitive, but that is me... I have done what you comment on, and changed the fields that have the problem manually on SQL.. so I will wait and see..

     

    I just wonder, it says Could not update field.... how do I assure that they get updated, does that was rejected?