DSXchange

What 8.x release are you on? Pretty sure that functionality was added to the Sequential File stage at some point.

First question will always be "what do you consider to be a month"? For example - an interval of 30 days? Strict difference between the MM value? Were you given any business rules or guidance for this calculation? Consider 04/30/2013 and 05/01/2013 - is that zero months or one month in you...

If the job has never been run and thus the table never created and populated, then you'll get that error. Is that the case?

So it's always taking the else path? Are you sure you need that function, meaning what happens if you remove it from the derivation?

That looks like it could be Project directory corruption as all of those filenames are part of the 'legacy' repository on the ETL server filesystem. Any chance you ran out of space recently in that partition / mount point? That can cause all sorts of interesting problems when you do.

Are you using the Complex Flat File stage?

Well... ok. Details, please.

Oracle is your source or target or both? Which 'end' is throwing the error? Is your table actually partitioned? And are you really running Oracle 8? That release is 14 years old at this point, so honestly curious.

I have no idea.

You could either continue to wait for someone with Teradata experience in both versions to wander by or you could ask your official support provider.

In other words, they're already there so there's nothing to add. If you really want all jobs to always dump their score, change the setting as Arnd suggested.

It's the dreaded "truncated during fetch" error, hence my questions.

Hence the request for details of their current process.

What it is in Oracle isn't the question, it might be if you were just selecting a column but you're not. Instead you are building a logical or derived column based on "C1" and "C2" with a mixture of functions so Oracle just assumes the worst and goes big. Still trying to understa...

Just out of curiosity, which is it?

That latest message tells you exactly what the problem is and gives you the numbers you need to fix it. Well, if not "fix" then at least enough to move on to the next problem.

Post your failure message(s).