DSXchange

Yes. A stage variable can contain any value, and a dynamic array is just a string with delimiter characters. How you access the individual elements depends on the delimiter character used in constructing the dynamic array. A generic solution is to use the Field() function. Field(stagevariable, d...

More! This question is in the same league as "how long is a piece of string?". It really does depend on what you're doing. Ideally you shouldn't need to use /tmp at all with PX, as temp space for the Engine is configurable (via UVTEMP in uvconfig) and scratch space per node is configurable in PX con...

DataStage is driven by metadata. If the metadata change, DataStage has no mechanism to detect that fact. It must all be altered manually. That is, you need to change your DataStage job design to incorporate metadata for the new fields in the source file. You also need, if applicable, to alter the ta...

Welcome aboard! You have two choices. In the ODBC stage there is a drop-down list of how you want the rows to be treated in the target database. The default (from memory) is clear table then insert rows. If you choose any of the update options from this list, then DataStage will generate an UPDATE s...

The derivation expression for a stage variable whose value you do not want to change is simply the stage variable's own name.

An undocumented method. The STATUS statement (not the same as the STATUS function) returns a dynamic array of information about an open file. According to the BASIC manual, there are 30 fields. A little research has revealed that there are, in fact, 32 fields returned. Field 31 is the "magic number"...

We will need to see the code of ErrID routine before being able to diagnose.
Did you capture the output of the SQL statement so that you could check for errors? If so, what message was output?

There are a few possibilities. Ken mentioned setting a row limit in Director when submitting the run request. This can also be accomplished, in various ways, with the other ways of submitting a job run request, for example the dsjob command line interface. The down side to this approach is that the ...

It's only approximate, remember. The chance of a false positive could be as high as one in 2,147,483,647.

Even if you don't, someone else may benefit from that piece of knowledge, which is really why I posted it.

I think, if you read it a bit more carefully, that you will find that what Ken said was that the design called for 30M rows, but what he implemented was ten hashed files each with only 3M rows. I suspect, without knowing the individual case, that data were partitioned based on the final digit of the...

Beware that this is an Oracle answer (the OP's question was about Oracle).

This technique can also be used in other databases, but the name of the user constant may be different, for example CURRENT_USER.

Be careful. Do your research.

SDKSequences is a table. It's key value is the argument for KeyMgtGetNextValue. It has one other column; the next value to be used in the sequence. Therefore, to reset just one "sequence", use a WHERE clause in the UPDATE statement. UPDATE SDKSequences USING DICT VOC SET F1 = '1' WHERE @ID = 'dept_k...

Checksum is not a perfect way to check for duplicates, because there is a slim chance (approximately one in 2,147,483,648 for CRC32) that a false positive will occur - that is, that different data will generate the same checksum. That's close enough for many folks.

Are you running a UNIX version of DataStage in the Cygwin emulation, or are you running a Windows version of DataStage? If the latter, what is it that you are doing with Cygwin that you think might contribute to the symptom that you are describing? Is it the DataStage server machine that "freezes" (...