SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 44329: An "invalid byte sequence" error might occur when you use bulk load with SAS/ACCESS® Interface to Greenplum

DetailsHotfixAboutRate It

When you try to bulk load to Greenplum, you might receive an "invalid byte sequence" error similar to the one shown below:

[SAS ACCESS to Greenplum][ODBC Greenplum Wire Protocol driver][Greenplum]ERROR:
invalid byte sequence for encoding "UTF8"

This problem can occur when you try to bulk load into an existing table that contains numerics. The way that SAS stores numerics can cause Greenplum to throw an error when rounding.

This error is not specific to UTF8 encoding.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS/ACCESS Interface to GreenplumLinux for x649.39.3_M19.3 TS1M09.3 TS1M1
Solaris for x649.39.3_M19.3 TS1M09.3 TS1M1
Microsoft® Windows® for x649.39.3_M19.3 TS1M09.3 TS1M1
Microsoft Windows Server 2003 Enterprise Edition9.39.3_M19.3 TS1M09.3 TS1M1
Microsoft Windows Server 20089.39.3_M19.3 TS1M09.3 TS1M1
Microsoft Windows XP Professional9.39.3_M19.3 TS1M09.3 TS1M1
Windows 7 Enterprise 32 bit9.39.3_M19.3 TS1M09.3 TS1M1
Windows 7 Enterprise x649.39.3_M19.3 TS1M09.3 TS1M1
64-bit Enabled AIX9.39.3_M19.3 TS1M09.3 TS1M1
64-bit Enabled Solaris9.39.3_M19.3 TS1M09.3 TS1M1
HP-UX IPF9.39.3_M19.3 TS1M09.3 TS1M1
Linux9.39.3_M19.3 TS1M09.3 TS1M1
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.