DSXchange

It also depends on what you want to do with the data between the read and load. It also depends on how much memory you have. It also depends on how fast your disk I/O is. It also depends on how fast your network I/O is. PX will use whatever that is provided for it. But for us to give you some hard n...

There are overtly paranoid people in this little world of our. DataStage is a very robust tool, despite its flaws. As one of the client said, after bombarding DataStage with billions of rows, forcing the poor UNIX box onto its knees for hours at a time, with nary a blimp -- "DataStage is defini...

Make sure your environment settings have your PX environment paths declared BEFORE anything else, especially before your DB2 environment paths (I'm guessing here that you're using DB2.)

You can do it pretty much the same way -- by using an after-stage routine.

To learn more about the Wrapped Stage, check your local Parallel Extender PDF (parjdev.pdf), under chapter 55 - "Specifying Your Own Parallel Stages".

Is the data being loaded to the wrong columns? If not, then why does it bother you on how the ordering of columns are? Databases are flexible to the point where it does not matter which order the columns are, as long as the mapping between the columns and the Orchestrate's columns are properly done....

You do not need to perform the sort twice. The Sort/partitioning tab is a simplified form of the Sort stage. It is a capability that was included in all stages, to make the job flow much clearer. Take a quick look at your Orchestrate code (within the Job Parameter option after you compile the job) t...

You can also pass the date field from Oracle, and match it with the valid date fields from the Transformer. Yes, a lot of duplications. Range matching is not available just yet (coming soon...)

This could be caused by a number of things. You will need to go to your project folder, locate the specific job number (quickest way: Recompile the job, and do a ls -altr, and locate the latest ds_sc**** folder. **** is the job number). Open up DS_RT (This is coming from memory, so I may be wrong he...

The answer is: No. The real question is: Is there any particular reason why you MUST have a database table with data in any specific order? This fly against the grain of just about any practical DBMS philosophy I am aware of. Running in multiple nodes would cause partitioning. This will break up the...

Hmm, that is weird -- based on my inexperienced observation, someone may be attempting to contact you (hack?) on those open ports. Ensure that your system's security is up to par, including external firewalls. Contact Ascential Support if this still continues. I'm sure they may have some suggestions...

You could read in microseconds for timestamps in PX. You just need to enable the option within your column definition. (Sql Type needs to be Timestamp, and Extended needs to be Microsecond)

I agree. I am just trying to find a way to allow things to work for you without too much of a pain. It's a pain when Ascential wrap everything within a single structure -- logs, files, source code, et cetera. That's why we do convulted stuff such as Version Control to handle migration and control of...

Uh... why sort? Do not sort unless there is a specific case where you have to sort. I am presuming that A is a join stage. Looking at the help file for the Join stage, we see: The data sets input to the Join stage must be key partitioned and sorted. ... Choosing the auto partitioning method will ens...

The only way I could think of doing it this way is to have the Oracle stage recreate the table. But it is definitely not a good idea (as any qualified DBA would gladly explain.) MetaStage can not do this. ERWin is a possibility, although I do not know that tool well enough to do this. It is possible...

I do not know if EE have any direct loading mechanism for Teradata (I haven't used that database yet), so I can't really help you on this. (Basically, I do not know whether they install an EE client on the Teradata box itself, or use some global API call to it from the EE box.) I would definitely re...