SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 69233: You are unable to migrate attachments from SAS® Anti-Money Laundering 7.1 using the SAS® Anti-Money Laundering 8.3 migration process

DetailsHotfixAboutRate It

Attachments from your SAS Anti-Money Laundering legacy system (7.1) do not get migrated to SAS Anti-Money Laundering 8.3 using the provided migration process. This issue occurs because the migration_status field is defined as CHAR (3-byte) instead of VARCHAR2 (3).

A workaround is to change the underlying SQL query (sasaml.migration.attachments.selectUnprocessedByCode.sql) to use the TRIM() function to remove extra spaces in the migration_status field.

Here is an example:

sasaml.migration.attachments.selectUnprocessedByCode.sql=SELECT a.* FROM migration.migration_attachment a INNER JOIN \
(SELECT DISTINCT object_id FROM migration.migration_attachment WHERE object_type_cd = ? AND trim(migration_status) = ? FETCH NEXT ? ROWS ONLY) i \
ON a.object_id = i.object_id WHERE a.object_type_cd = ? AND trim(migration_status) = ? ORDER BY a.object_id, a.create_date DESC

Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Anti-Money LaunderingLinux for x648.3Viya
* 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.