DSXchange

The latter seems like the best solution to me... sum them first upstream and then Aggregate them.

Not sure but an exact search for "Only limited schema reconciliation will be performed" returned 8 matches, perhaps something there will help.

I'm curious how you are going to handle the "once in a lifetime" condition / trigger part of this...

Just to be anal, from what Raja posted that 'Replace' option drops and recreates the table in question, it is not being truncated. One would do one or the other, not a combination of the two.

So... is this a problem with one specific job only? If so, can you describe the job? If not and these are parallel jobs, have you confirmed that jobmonapp is running?

So... what was the resolution?

pandeesh wrote:And also we can have a trap in unix to find our whenever it's shutdown

I've said this before and I'll say it again - a comment like this where you just say "You can do X" isn't really helpful without an explanation of how to do X.

I would imagine they exist in the 8.x world but don't recall them being there in the 7.x release.

Sad to say it took a minute or three to sink in... 5/4/2012... Not just the fourth but May the Fourth... be with you. Secret call-sign of the elusive Lisping Jedi Knights.

I'm assuming they already know this since they are successfully doing what is essentially the same thing in Oracle.

A combination of the Convert() and CHAR() functions should do the trick, me thinks.

Help yourself - involve support. People here aren't going to be able to dig into your problem and help figure it out like they would be able to do. However, if this "first time" happens every day such that you need to re-run it every day and this is a scheduled run that happens at the exac...

There's really no reason to be modifying the automatically generated crontab entries DataStage creates. Never mind the fact that they only have this issue with one particular job, all other scheduled jobs are working properly from what they noted. I'd still be curious if "re-doing" the sch...

What kind of reject link is it? Meaning, did you check the Reject Link property or are you using a constraint in the link to control what goes there? I'd also be curious what "they are getting skipped" means.

Go into your job properties and add the environment variable APT_DISABLE_COMBINATION then run your job with that set to True. This will let us know the stage name generating the fatal messages...