DSXchange

chulett wrote:Or you can use the 'old' style outer syntax - (+) - in the generated sql which will get you everything but a full outer join.

Isn't the (+) syntax only for Oracle? It's not part of the SQL CAE Access Group's standard.

Has anyone else seen the following behaviour? Added a job parameter based on the environment variable APT_BUFFERING_POLICY. Its list contains three illegal values ("Automatic buffering", "Force buffer" and "No buffer"). These should be AUTOMATIC_BUFFERING, FORCE_BUFFER and NO_BUFFER. View data fails...

Make sure data are partitioned on SBSB so that all records in any one group are on the same processing node.

Searching the forum would have revealed that the answer to your question is to use as many -param name=value options in the dsjob command as you require. How you set the value in your script is entirely up to you; it can be a shell variable for example.

I think if you put the auto purge set to two days, that should work. Because every time the logs are purged, the event id is set to 0. Not true. The event ID is only set to 0 if the log is cleared. I still think the problem is going to be with the expr command in the shell script. There is no easy ...

As far as I am aware this is not possible, but would be happy to be proven wrong. Each row in the stream of rows that is being processed may have come from any of the files. Reading from the files that match a pattern is like using cat to make a single stream in a filter, except that you can get som...

I have been using QualityStage for a while without problems, and now suddenly I can not launch it at all. The obvious question to ask, which your support provider has doubtless also asked, is "what has changed?" "Nothing" is not the correct answer. It doesn't have to be a change in QualityStage - i...

sray2001 wrote:I did not able to read your answere completely... It blocks to read since I am not premium member.

For less than $1 per week you can be a premium member.

For less than $1 per week you can be a premium member.

Doesn't need to be user-defined. You can generate a query containing join criteria. Simply put a comma-separated list of table names into the Table Name field, and the join criteria into the WHERE field on the Selection tab. In the Columns grid make sure that no ambiguities exist by using fully-qual...

The key to the DataStage log is an integer, and therefore can not be incremented beyond 2,147,483,647 (the largest representable signed integer in twos-complement numbers). DataStage is really not set up to operate this way; your performance is likely to be abysmal. The same kind of effect is likely...

A vector is a single-dimensioned array consisting of between 1 and N elements, all of which have the same data type. A vector may have a fixed number of elements, or a variable number of elements.

Just specify the join in your SELECT statement, like you would if you didn't have DataStage. This is the most efficient mechanism in general.

Look at the second case study in the Pivot Stage manual (pivot.pdf). It is exactly this scenario. A Pivot key, a non-pivoting column, and a pivoting column.

Re-organize the code in the batch so that, instead of Run Wait Run Wait, it goes with Run Run Wait Wait. It's up to you where you test the exit status (though obviously it must follow the appropriate DSWaitForJob). Try to start using job sequences. They offer everything the batch mechanism does (exc...