Not Able To Load Xport File Via LSH SAS Loadset Due Case Sensitivity in Data Set Names ( And ebcdic1047 Encoding Instead of UTF8 )
(Doc ID 2201499.1)
Last updated on NOVEMBER 07, 2016
Applies to:Oracle Life Sciences Data Hub - Version 2.2.2 and later
Information in this document applies to any platform.
On LSH 2.2.2, not able to load XPORT file supplied from the vendor using LSH SAS loadset.
Using SAS software to read and load the file to data base its working fine. The data file looks like UTF8 format, however system is treating it of different file format.
The XPORT file supplied from the vendor is failing with below error during data load:
29 %sysexec sas -encoding 'ebcdic1047' "%sysget(CDR_BASE)/Setup/lshautoexe.sas";
30 libname source cvp "%sysget(CDR_BASE)/Source";
31 libname utfraw "%sysget(CDR_BASE)/Setup" outencoding=UTF8;
32 proc copy noclone in=source out=utfraw;
ERROR: Physical file does not exist, /proj/sastmp/saswork/LSHPRD/64019794901/Source/ZE.xpt.
PFA, the SAS file used to load and log generated as part of LSH job.
STEPS TO REPRODUCE
Testing it by first time with the vendor's file.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!