DSXchange

Not preserve partitioning. Preserve Type.

The problem's on the output side. One of your target columns is of type Char or VarChar (string) even though it's the result of an Aggregator set function. Either use the Preserve Type property in the Aggregator stage (assuming you're doing something string-legal, such as Max), or specify the output...

The "native" connectivity to Netezza uses ODBC 3.x protocol. (The "native" connectivity to DB2 uses protocols closely based on ODBC. The "native" connectivity to UniVerse uses ODBC protocols. So the Netezza story is nothing particularly new. After all, all that's happen...

Any sequence activity can retrieve the job status of a Job activity that is upstream of the requesting activity through use of the activity variable $UserStatus. If the Job activity is not upstream in the sequence this is not directly accessible, but the user status could be retrieved via a routine ...

The whole of your understanding is incorrect. Each job (each instance of a multi-instance job) has various entries in its own RT_STATUSxxx hashed file, and only its own user status is recorded in one particular record in that hashed file. Sequences are jobs, so they have their own, independent RT_ST...

The User Variable activity did not exist in 2008.

You are correct. The job's user status area is a field within the job's RT_STATUSxxx hashed file. Therefore it is destructively overwritten, so that only the most recently-written value is available at any time.

Then get privileges to effect that particular ALTER TABLE statement.

You might like to read that section of the manual that deals with handling the special characters "%" and "#" for DB2 and Oracle.

This problem can also be seen in the final field of a text file record, where the line terminator is not properly handled so is being treated as part of the data (particularly DOS-style line terminators where the metadata are specifying UNIX-style).

Your proposed scenario of different number of nodes for range map will fail.

Structure of the range map is not documented in the public domain. You can be fairly certain that it contains the limit values for each node. Range partitioning does not perform a sort, though it will preserve any sorted order of the partitioning key that happens to exist on the input link. This is ...

Easy scenario - second run with same source data.

1. Not in the DataStage job, because the file is still open while the job is running. However, you can rename the file in an after-job subroutine (for example ExecSH) providing the timestamp portion as a job parameter or in the command itself (using backquotes on the date command). 2. In the sequenc...

Upsert might generate updates only if every record already exists in the target, but not otherwise.