DSXchange

No. Nothing in the stage allows you to do something you wouldn't otherwise be able to do in any other client tool. Now, if Teradata has something like a 'database link' that allows one database access to the other, then you could leverage that in a single stage / query.

plunge plunge plunge

You need to put this in front of your official support provider and see what they say about the behaviour. It doesn't sound right or like anything I recall seeing or experiencing in the past.

For completeness, what exact 8.x version are you running? Are you current on fixpacks?

jreddy wrote:The inner sequence had warnings in the first run

Are you saying that one or both of the skipped jobs had warnings when they ran? Then job3 aborted, the sequence was restarted and then jobs 3 and 4 completed without warnings?

Just trying to ensure we're seeing the complete picture here.

jreddy wrote:Then I would wonder how restartability works when we have sequences within sequences..

Sorry but isn't that exactly what we're talking about here? Sequences within sequences?

jra2002: the next time you have a new question or topic to discuss, please start a new post rather than just tack it on at the end of a previous subject.

I've split this one out for you.

Don't expect or force a one-to-one conversion, either. 'Reproduce it using DataStage' means the logic / work being performed, not the number of steps involved - although they could be similar.

As noted, you really need to identify the character in question, its specific value. Only then will you be able to deal with it properly.

That may just be The Way It Works and you may want to ping your official support provider for clarification on that point. Curious what others think...

"inbetween spaces"? Pretty vague.

How about some before and after examples so we have some confidence that the right question is being answered.

What does the log for the inner sequence job show after a restart? I would think it would have whatever 'warnings' were logged that caused it to finish with warnings in spite of it successfully running to completion.

There is no point to the points, they are... pointless.

rsripathy wrote:Is there difference between,,, Change Data Delivery & Change Data Capture ? If so what ?

See the link in my previous post.

Think of uvconfig as the 'kernel tunables' for the Server engine. The dsparam file is used to store environment variables - i.e. parameters.

Didn't say it wouldn't or doesn't work, just pointing out that it makes no sense to have any code after a call to DSLogFatal.