When Oracle fields have a defined data type of VARCHAR2 (for three characters), the FEDSVR engine defaults to the use of a VARCHAR data type that allows 3 bytes of information.

If the data in a field in Oracle contains three characters, but one character is accented and is a double-byte character, the data is truncated. Here is an example:

• “NÃO” is in an Oracle field that is defined as VARCHAR2.
• The FEDSRV engine transcodes “NÃO” as “NÔ and drops the final character.
• The final “O” is considered to be a fourth byte and exceeds the column length.

This issue is likely to occur when the Oracle database uses a single-byte character set, such as LatinX or WE8MSWIN1252.

The workaround is to increase the length of the columns as needed to accommodate any potential double-byte characters.

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

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Federation Server	Microsoft Windows Server 2012 Datacenter	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows Server 2008 for x64	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows Server 2008 R2	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows Server 2008	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows 10	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows 8.1 Pro x64	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows 8.1 Pro 32-bit	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows 8.1 Enterprise x64	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows 8.1 Enterprise 32-bit	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows 8 Pro x64	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows 8 Pro 32-bit	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows 8 Enterprise x64	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows 8 Enterprise 32-bit	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft® Windows® for x64	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows Server 2012 R2 Datacenter	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows Server 2012 R2 Std	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows Server 2012 Std	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Microsoft Windows Server 2016	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Windows 7 Enterprise 32 bit	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Windows 7 Enterprise x64	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Windows 7 Home Premium 32 bit	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Windows 7 Home Premium x64	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Windows 7 Professional 32 bit	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Windows 7 Professional x64	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Windows 7 Ultimate 32 bit	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Windows 7 Ultimate x64	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		64-bit Enabled AIX	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		64-bit Enabled Solaris	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		HP-UX IPF	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Linux for x64	4.2	4.2	9.4 TS1M5	9.4 TS1M5
		Solaris for x64	4.2	4.2	9.4 TS1M5	9.4 TS1M5

* 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.

---

A fix for this issue for Base SAS 9.4_M6 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/D9T.html#63831

---

A fix for this issue for Base SAS 9.4_M5 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/B6Q.html#63831

---

The SAS Federation Server LIBNAME engine incorrectly transcodes data from an Oracle database when the fields are defined with LatinX or the WE8MSWIN1252 database character set. The problem occurs when the length of the transcoded value exceeds the column length.

Type:	Problem Note
Priority:	high

Date Modified:	2019-03-19 15:44:05
Date Created:	2019-03-12 09:39:51