DSXchange

Post it. The complete "it", copied from the log, please.

Then you'd need to check if the original value is equal to that same value in upper case.

Do you know the maximum number of 'delimited subcolumns' you can see? If so, then it's still just a regular pivot with something downstream of it to block the 'empty' subcolumns.

Too many variables unique to your environment to say with any certainty how much 'struggling' there will be. Suggest you move from the theoretical to the practical and actually build a test job. See how well it performs for you on your setup.

Not sure what you mean by the 'disadvantage' remark, the Project Default values will be both used in the job and logged in the log for you. And I honestly don't believe that 8.x changes any of this.

As long as you understand your queries are unaware of any records flowing through the job and need to 'stand alone' you *should* be able to do this. "Should" as it depends on exactly what you are attempting to do, but they can certainly be used for tasks of this nature.

The 'real' thread on this topic is here:

http://www.dsxchange.com/viewtopic.php?t=119486

No need to explain, I understood perfectly what you are doing - and what you are doing is (almost) the same as many other installations are doing. That's what Project level Environment Variables are for. However, you've missed the key point in my post, which explains why there's no need to change an...

What stage? If you are using the 'OCI Load' stage in Automatic mode, no logs are produced. In manual mode, you tell it where to put them so you should have the answer already in that case.

That shouldn't be necessary, so I'm guessing you're not using them correctly. Parameter values are never changed during any import or export operation. If you have them setup in each Project with certain default values, what you want to use in each job as the default value there is $PROJDEF. That wa...

Doesn't make much sense. Please explain what you get when this 'wrong set of records' is generated, and can you post examples?

It's possible. Search for 'update sdksequences' to find out how to do it, it has been posted here a number of times.

The Execute Command stage in a Sequence job? Any output from the command should automatically be logged from what I recall. You'd have to double-click on the log entry to see those details under the elipses (...) but they should be there. Rather than write the output to a file, why not let it echo t...

Yup. Only two ways to keep those warnings in check - either don't create them or abort the job after X warnings to keep them from overflowing your logs.

If neither one of those work, perhaps try setting this parameter:

APT_BAT_UPSIDE_HEAD=True

Oh, wait... Server job. Never mind.

Sorry, but answers 2 and 3 don't apply to Server jobs.

Your best answer is to fix the job so that it doesn't generate any warnings. There's no reason on the planet why a Server job should generate anything but loverly little green Info messages.