I recently removed an "SCL Type 2 Loader" from a DI Studio job, and created a new surrogate PK for the output table. The job ran fine. However, now that I've transferred the job to a new environment, I get the following warning for each of the four variables that were removed along with the SCL Type 2 Loader (policy_sk, valdidfrom_dttm, validto_dttm, and current.): "WARNING: Variable <varname> was not found on BASE file. The variable will not be added to the BASE file."
I'd greatly appreciate advice on how to fix this. Thanks.
It's all there in the error message - you miss a column in the physical target, which the metadata assumes is there.
There are no built in functionality in the Type 2 loader to identify differences between metadata and physical table lay out, and create the code to harmonize the two - it's up to the developer do this separately as a one time fix job - which should be attached when pushing changes to the next environment.
It's all there in the error message - you miss a column in the physical target, which the metadata assumes is there.
There are no built in functionality in the Type 2 loader to identify differences between metadata and physical table lay out, and create the code to harmonize the two - it's up to the developer do this separately as a one time fix job - which should be attached when pushing changes to the next environment.
Good news: We've extended SAS Hackathon registration until Sept. 12, so you still have time to be part of our biggest event yet – our five-year anniversary!
Need to connect to databases in SAS Viya? SAS’ David Ghan shows you two methods – via SAS/ACCESS LIBNAME and SAS Data Connector SASLIBS – in this video.
Find more tutorials on the SAS Users YouTube channel.