FOR statement generates errors 6182 and 2651 using Unicode-enabled DataServer for MS SQL Server

Errors 6182 and 2651 occur when querying NVARCHAR field with a FOR statement where the value used in the ABL WHERE clauses exceeds the max-width of the field in MS SQL Server.

Mar 26, 2012
Knowledge

Title

URL Name

000030544

Article Number

000192438

Environment

OpenEdge 10.2B Windows DataServer for MS SQL Server

Question/Problem Description

FOR statement generates errors 6182 and 2651 using Unicode-enabled DataServer for MS SQL Server.

Errors 6182 and 2651 occur when querying NVARCHAR field and value used in the ABL WHERE clauses exceeds the max-width of the field in MS SQL Server:

You tried to compare or to update a character field with a value longer than the maximum length. (6182)
Field num: <field-num>, value: <value>. (2651)

Steps to Reproduce

Clarifying Information

Schema holder is UTF-8.

MS SQL Server field is defined as:
name nvarchar (30) null

Example ABL query:
FOR EACH customer WHERE NAME = "1234567890123456789012345678901234567890" NO-LOCK:
END.

The value in the WHERE clause is 40 characters long.

Problem does not occur when the same query is executed against a VARCHAR(30) field.

Error Message

You tried to compare or to update a character field with a value longer than the maximum length. (6182) Field num: <field-num>, value: <value>. (2651)

Defect Number

Defect OE00217893

Enhancement Number

Cause

Only non-Unicode data is truncated during data comparison, while an equivalent Unicode character datatype issued an error due to the size mismatch of the comparison.

Resolution

Upgrade to 10.2B06.

Workaround

Prior to 10.2B06. the issue can be alleviated by increasing the Length value of the field in the MS SQL Server table to a number that will accommodate the length of most WHERE clauses. Once done, re-pull the table back into the schema holder.
Note: the error will occur should the length of the WHERE clause exceed the Length of the field specified for the Unicode data-type.

Notes

References to Written Documentation:

Per the READMESP.TXT file included with Service Pack 6 for OpenEdge 10.2B:

Note: OE00217893 Type: Behavior Change

Unicode datatypes mapped to OE CHARACTER truncated during data comparison

---------------------------------

In the previous releases, only Non-Unicode data was truncated during data comparison, while an equivalent Unicode character datatype issued an error due to the size mismatch of the comparison. To resolve this issue, Unicode datatypes in MS SQL Server mapped to the OpenEdge CHARACTER datatype in database tables (defined in the schema holder), get truncated during data comparison with other Unicode character columns or expressions defined in a WHERE clause. (This is similar to the non-Unicode data types behavior.) This is done to achieve compatibility with the OpenEdge database which currently performs this same WHERE clause value truncation. Therefore, the new behavior provides consistency across all (Unicode and non-Unicode) character types.

Keyword Phrase

Last Modified Date

9/13/2015 11:56 PM

FOR statement generates errors 6182 and 2651 using Unicode-enabled DataServer for MS SQL Server

Files(0)

Was this article helpful?

Was this article helpful?

FOR statement generates errors 6182 and 2651 using Unicode-enabled DataServer for MS SQL Server

Information

Related Articles