topic Multiple lengths were specified for the variable [variable] by input data set(s) even if it's not in SAS Data Management

Multiple lengths were specified for the variable [variable] by input data set(s) even if it's not

meatballs12345 — Wed, 09 Feb 2022 01:28:50 GMT

Hi everyone,

I'm currently updating the metadata objects for a certain job to align the changes made on its source. Now as I'm testing it, I got this warning:

I'm pretty sure that all of the transformations are already aligned with the new variable length but the warning persists. I came across a thread with a different concern (ERROR: different length on BASE and DATA files) and saw that it's a bug on SAS DI. This means that the physical table is not the aligned with the metadata, checked it on my end and the metadata of the physical table was outdated

(Physical Table: 40, DI Before: 60, DI After: 100)

Could it be the same cause? Also, I'm not allowed to re-create the whole job, any possible fix? If I'll alter the physical table, this means I have to commit the changes on that particular table, right?

TIA!

Re: Multiple lengths were specified for the variable [variable] by input data set(s) even if it's no

LinusH — Wed, 09 Feb 2022 21:16:35 GMT

It's a bit tricky to guide in this type of matter.

Not all transformations enforce metadata to physical tables/views.

So I think you need to back track step by step to find out where the deviation starts.

You might be forced to do changes earlier in the job to fix the problem, perhaps even add a transforrmation.

If you have changed the defult length of a numerical variable, be aware of that Proc SQL views ignore that.

Re: Multiple lengths were specified for the variable [variable] by input data set(s) even if it's no

meatballs12345 — Thu, 10 Feb 2022 00:03:03 GMT

Ohhh I see. The Proc SQL might be the answer for this. Thank you for this insight @LinusH. 🙂

Re: Multiple lengths were specified for the variable [variable] by input data set(s) even if it's no

LinusH — Mon, 21 Feb 2022 11:25:20 GMT

Did you confirm it was a SQL view that caused this (you said "might").

Also, I saw this:

https://support.sas.com/kb/68/546.html

Should be fixed from hot fix J7S002:

https://tshf.sas.com/techsup/download/hotfix/HF2/J7S.html#J7S004

Re: Multiple lengths were specified for the variable [variable] by input data set(s) even if it's no

meatballs12345 — Tue, 22 Feb 2022 01:44:41 GMT

Hi @LinusH!

Apparently there are no SQL on the transformation where it occurred. It's a join transformation btw.