DSXchange

For insert only, the trick (I believe) is to use the "User-defined Update Only" option and then make your actual user-defined SQL an insert statement.

Yes, I've seen it personally and it has been reported here as well by several others, I do believe. All it takes is the loss of the hidden .Type30 file inside the directory to cause this issue as the hashed file is no longer a dynamic one. It can then fall back on this funky (type 1? 19?) "hash...

What exactly happens when you try to "compile"? Does the job have a Transformer in it by chance? If so, you'll need to have a supported C++ compiler installed and properly configured before that will work. For the view data problem, what stage are you using? What errors are you getting? Ha...

No setting here - the first action must fail for the second to happen, so you'll need a unique index over your key(s) to keep the duplicate inserts from happening.

Actually, the amount per month is 13.61333333333333... so you either need to alternate rounding up and then down across the months to even out the difference across the year or you need to lump the difference into the first or last month - 13.66 - otherwise you'll be short. Isn't this just two outpu...

DIVIHN wrote:I did it I have set APT_DUMP_SCORE at Job level but still the job using project level value.

You add it to the job and then override the value in the job itself to be True via the Director.

What about them? Look inside the directories, there's nothing mysterious in there.

You can't corrupt the job by messing with its log. As for your questions - try it, let us know... though I have no idea why you'd want to do that.

Did you install 7.5.2 or 7.5x2? The latter is the only pre-8.x release that will actually run PX jobs on Windows. Since it looks to be attempting to run them, I would guess the latter is actually correct.

Post your config file. Have you "tested" it using the built-in tester utility?

Same answer for any of the APT environment variables. There are several that you should be doing this with in every job so you have the option to change them at runtime if needed. Don't have a list off the top of my head any more but APT_DUMP_SCORE and APT_CONFIG_FILE come to mind...

What kind of "impact" are you thinking would happen? Logs need to be cleared periodically, hence the Auto Purge as the primary mechanism for that. It supports two purge types, the same two types you can do manually from the Director - by days or by runs - three types if you count clearing ...

meet_deb85 wrote:BUt IF i am adding any other SQL IT is failing with warning no fatal..same as pasted earlier..

It's too long, you'll need to find another way to do this... a view comes to mind.

Look inside them.

Yes, the "LOG" one is a dynamic hashed file holding the job's log and you don't want to be deleting any of them.

That's because of the trailing delimiter, it means there is another field coming. Remove it. You should have n-1 delimiters for n values in the list of values.

Split from this topic.