Error ASSIGNING Record to SQL - Forum - OpenEdge Pro2 - Progress Community

Error ASSIGNING Record to SQL

 Forum

Error ASSIGNING Record to SQL

This question is answered

Hello,

Does anyone know how to solve this problem?

At Progress side the field has INT64, int Oracle this filed NUMBER.

25-05-2017 16:31:00 - Table op.op:  Record 0x00000000321e7970 - Error ASSIGNING Record to SQL:

Value 2205767248 too large to fit in INTEGER. Line 183 in op_op_R bprepl/repl_proc/rop_op.p. (15747)

** Unable to update bfrTgtOP Field. (142)

25-05-2017 16:31:00 - ?

25-05-2017 16:31:00 - Table op.op:  Record 0x00000000321e7971 - Error ASSIGNING Record to SQL:

Value 2205767249 too large to fit in INTEGER. Line 183 in op_op_R bprepl/repl_proc/rop_op.p. (15747)

** Unable to update bfrTgtOP Field. (142)

25-05-2017 16:31:00 - ?

25-05-2017 16:31:00 - Table op.op:  Record 0x00000000321e7972 - Error ASSIGNING Record to SQL:

Value 2205767250 too large to fit in INTEGER. Line 183 in op_op_R bprepl/repl_proc/rop_op.p. (15747)

** Unable to update bfrTgtOP Field. (142)

Verified Answer
  • The problem was that the DataServer during the creation of SchemaHolder converts the data type Number (Oracle) to the data type Integer (Progress).
    After manually changing the data type in ShemaHolder, the error has disappeared.

    Can I somehow change the default behavior of DataServer in this regard?

All Replies
  • Hi Valeriy,

    This error occurs when INT max value exceeded by its cumulative sum. This exceeds the maximum value of a 32-bit integer which can hold upto the value of "2147483647".

    In your datatype definition in the database may needs to be changed. Use INT64 in the datatype instead of INT. It will resolve the issue.

    In the Oracle side also, the maximum digits for Number data type can taken upto "X(10)".

    Thanks.

    Kunal

  • Hi Kunal,

    Thank you for your reply.

    Yes, I know it, but in regards to Pro2 I don't understand why it occurred. I think, that problem in replication

    map. The oracle schema generated by Pro2.

  • The problem was that the DataServer during the creation of SchemaHolder converts the data type Number (Oracle) to the data type Integer (Progress).
    After manually changing the data type in ShemaHolder, the error has disappeared.

    Can I somehow change the default behavior of DataServer in this regard?

  • Hi Valeriy,

    I was trying to say the same thing that Needs to change the data type from the database. I thought it to be the Target database but unfortunately didn't mentioned the schema holder.

    So, Its good that the issue has been resolved.

    Thanks,

    Kunal