While restoring a backed-up table, especially the FSK_LOV table, in Microsoft SQL Server, you might encounter errors similar to the following:

These errors occur after you take the following actions:

• You apply Hot Fix A5T006.
• You complete the optional steps for converting all fields that could contain multibyte characters to NVARCHAR.

The errors are the result of truncated characters being loaded, and you can resolve them by ensuring that restored data is loaded into columns of the appropriate type and size.

To work around this issue, complete the following steps:

1. Back up any affected tables.
2. Alter the columns that were changed in Hot Fix A5T006 to use the NVARCHAR format. To see the expected NVARCHAR sizes, refer to the sqlserver_7.1HF5_nvarchar_3_convert_ddl.sql file, which was delivered as a part of the hot fix.
3. Reload the data.
4. Compare each new table after the hot fix is applied to the old table version that you backed up. Restore any missing values manually.

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 Anti-Money Laundering	Linux for x64	7.1
		64-bit Enabled Solaris	7.1
		64-bit Enabled AIX	7.1
		Microsoft® Windows® for x64	7.1

* 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 SAS Compliance Solutions 7.1 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/A5T.html#63097

---

The error "Unable to transcode data to/from UCS-2 encoding" occurs while restoring a backed-up table, such as the FSK_LOV table, in Microsoft SQL Server. It occurs after you apply Hot Fix A5T006 and you also convert all fields that could contain multibyte characters to NVARCHAR.

Type:	Problem Note
Priority:	high

Date Modified:	2018-11-13 12:10:08
Date Created:	2018-10-19 11:38:12