DSXchange

Are you defining parameters as this:

$BLAH_BLAH_BLAH -- particularly those starting with the $?

If so, you need to define them on EVERY server that your job will be existing on. This is why I avoid user-defined system parameters, and just use job parameters.

Partition Table option is _NOT_ related to Oracle's Partition table. Partition Table is a behavior used in PX in pulling data from Oracle. It does NOT work with Oracle's Partitioned tables. You could file an enhancement request, but unfortunately, until this is provided as a feature, you are advised...

mngr.cfg file is optional. Pull the documents as Ray advised, and you should see the guide on how to create this file.

There are some databases where you can partition on the source (Oracle, DB2...), but the advantage of PX lies in the transformation stage. PX is capable of breaking up the data into good set of partitions (as defined by your $APT_CONFIG_FILE), and handle each set individually. This is why we strongl...

If you are referring to Dataset files, the answer is no.

Also, where are the databases? To be honest, if both tables are on the same schema, on the same server, and that server is separate from the PX server, it would definitely be advantageous to do a simple SQL query to handle the table-to-table load. Just throw together a job and run the test on your o...

SMP = Single big box with many CPUs, all running under one OS. MPP = Many boxes with few/many CPUs, all networked together. * * * Both formats are well supported by DataStage Enterprise Edition. Each have their own advantages and disadvantages. Grid computing is a MPP concept that are being advocate...

It would definitely be very helpful if you would submit this as an enhancement request to Ascential Support to ensure that Ascential will be aware of this problem with Oracle and microseconds. That's the only way they will be sure to include it in the next version (if it have not already been provid...

Actually, it's not the stored procedure stage I'm referring to. insert into [table] (field) values (field.NEXTVAL) It may not be truly parallel, but it's all within the Oracle framework. Surrogate Key Stage is a 7.x feature. It only simplify the same capability that can be found within the Column Ge...

It means that they are partitioning your data other than the default preference (Entire). If they use Entire partitioning, they would share the memory between all the nodes, instead of making copies of the same thing for each node (and eating up more memory). However, you are setting it as something...

As many as you would like.

Of course, there are practical limits, but... as many as you would like within reasons.

NOTE! Ascential DataStage is not for home use. Ascential fully expects that you pay the full price per CPU (or whatever negotiated rate you may achieve with your Ascential (or other official licensed - such as IBM, et cetera) sales representative). If you are found to be using an unlicensed copy, As...

You do realize that you can actually declare NEXTVAL on the output SQL within the Oracle Enterprise stage? You also do realize that we have a Surrogate Key Generator stage that can be used in conjunction with reading the maximum value from the database (and merged into each record via lookup, and ca...

Did you also include the Microsecond extended option? It's the column next to the type (where you declared Timestamp). It's usually blank, but can be set to include Microseconds.

If you had to ask, that means you already tried. Therefore, the answer is no. If you did not try, then why are you asking? If not, you will need to read it in as Char (or VarChar if it's a delimited file), then convert it to timestamp using StringToTimestamp() with the proper format defined in the c...