DSXchange

It wasn't just reconciliation - it was also transfer the tables' data and, indeed, create the target tables. Then reconciliation to prove that it all worked.

You're not trying to load NULL, you're trying to load a space character, which (as noted) is not legal for Decimal data type. Therefore DataStage changes it to NULL and alerts you of that fact. To eliminate the warning, don't attempt to load " " into a Decimal field.

Thanks, Gregg, but there's no Schema File property available with the ODBC Connector stage (nor with any of the other Connector stage types, as far as I am aware). Runtime Column Propagation looked after transmission of the columns for me.

In my current engagement, I am using fewer than 12 jobs, but they are generic, dynamic and multi-instance. (This was the customer's requirement, as well as an interesting technical challenge.) For example SQL statements are generated "on the fly" from information in the system tables. Many...

That you'd have to try - who knows what these database engines are capable of?

Just to make life interesting, the customer has stored non-printing characters, including 0x00, in VARCHAR2 fields. Therefore the "purely generic read" had to be ruled out because these 0x00 characters prematurely truncated data. The replacement approach, which is successful, is to generat...

If you look at the record schema, you will see that field defined as {prefix=2}string[max=3400]
The length is stored in the prefix, the characters are stored in the string.
It's how VarChars are stored in most computer systems and databases.

Oh yes, you may have compiler issues, but you can't see them until this error is fixed.

It's nothing to do with the compiler. The trick is to read the error message. ##I = informational, ##W = warning, ##F = fatal. Your fatal message is v##F IIS-DSEE-TFSU-00075 03:55:12(001) <main_program> Fatal Error: An ORCHESTRATE program must be started on a node in the configuration file. This pro...

That will depend on which stage type you choose and whether or not it's capable of parallel processing. For example, the Oracle Enterprise stage is capable of parallel processing but (unless it's a partitioned table) Oracle will only deliver a sequential stream when reading. However, a DB2 Connector...

It's always a compromise. The advise to minimize connections to databases is sound, but some of the work may involve no database connections and so could be a candidate for a modular design. Environmental factors, such as limited time windows for accessing source and target systems, may also contrib...

As noted, the important file is $DSHOME/dsenv rather than .profile. Make sure that ORACLE_HOME (and, if relevant, ORACLE_SID) are correctly set in the dsenv script. Otherwise, introduce them into your jobs as parameters so that they can be set on a job-by-job basis.

Let's start with the name - it's a "hashed" file. In DataStage BASIC you need to have opened the hashed file with an OPEN or OPENPATH statement. Then you need to read for update or lock for update, using READU or RECORDLOCKU statements. Once that has been done, effect your update with a WR...

First step must be to ask the DBA why the table is set to noparallel.

That might influence your decision about how to manage it in DataStage.

Welcome aboard.

Start by clicking on Help when in these stage types, or consulting the manual, or visiting the IBM Information Center.

A Search of DSXchange may well prove fruitful too.

Once you have acquired this knowledge, please revert with any particular questions.