DSXchange

Thanks. All I have right now is just to clarify that adding that "print schemas" APT variable was not meant to fix anything. It was to log additional information so that you could figure out what might be going on. If you added it and its information managed to survive the job's abort, can...

That is... unfortunate.

If you still have the issue after going through all that, we'd probably need more details as to exactly what it is you have in the job.

Did you try anything from the other thread you posted in? Specifically printing out the schemas via $OSH_PRINT_SCHEMAS.

Are you perhaps thinking of Workload and/or Queue Management?

Smells like a bug to me, have you involved your official support provider?

I can't imagine it's impossible... is your parameter set using value files? Seems to me that would drive the approach.

I'll probably have to leave the actual advice up to others as I don't have DataStage access and haven't for several years now.

Sounds like a looping Sequence to me... have you ever done one before with the Start Loop and End Loop stages? I don't know why you wouldn't be able to set that parameter per iteration...

Split you out into your own topic.

I've never understood why so many people who deal with multi-byte characters stick to BYTE semantics in Oracle. Why not alter that column in the table to be VARCHAR2(30 CHAR) instead?

Okay, once again we are treating the symptom, not the disease. Can someone answer the question as to how changing auto purge at the project level affects existing jobs? We know the change will take effect on any new jobs but what about existing jobs? I seem to recall people here saying that in some ...

joycerecacho wrote:A configuration that keeps only 7 days of log only works for new jobs, right?

I'm not sure that's still the case, I seem to recall that behavior changing in later versions. Someone with actual experience with doing a change like that would need to chime in, however.

Four years down the line let's get you into a new topic for this latest question... here you go.

Did exactly that many moons ago when we had a need for a looping sequence to run something every 15 minutes on the mark. So built a routine to check to see how long the previous iteration took (what time did it end) and then do a little time math to know how long to sleep to get to the next quarter ...

Seeing as how they haven't posted since Wed Dec 07, 2011 I would tend to agree.

Start a new post, detail your issue.