DSXchange

This is ugly and potentially dangerous.

If MsSQL or Sybase, which I do not believe support MINUS or INTERSECT through such elegant words, you can use an EXISTS (INTERSECT) or NOT EXISTS (MINUS) subquery. Example: TABLEA (C1, C2, C3, C4) TABLEB (C1, C2, C3, C4) MINUS subquery: SELECT * FROM TABLEA A WHERE NOT EXISTS ( SELECT 1 FROM TABLEB ...

I would suspect that the windows server version supports bcp for MsSQL. Thus, I would suspect that the windows version would toast Unix when putting data away directly to MsSQL.

If you are heavy MsSQL or only MsSQL I would consider staying on the windows version.

You can always compare a set of something to a set of nothing. What is tough is comparing a set of something to a set of something that is unknown. That will throw ya. A set of something other than nothing is never equal to the set of nothing. They are mathematically different. Anyways, in relationa...

What happens if you install a new client on an entirely new (never had DataStage installed) PC? Cool. I guess. It is missing the stages as well. Ascential told us that the project default is stored in the project directory (server side) and that they don't how to rebuild (apart from dropping/recrea...

Ascential does not know why their product caused itself corruption. In addition, they do not want to try and figure out the specifics of why it happened. They want me to export the jobs, drop the project (note: cannot restore easily because of complexity of the patch that was installed), recreate th...

chulett wrote:Have you tried just reinstalling the client? ...

Good suggestion. I actually tried and it results in the same situation. All stages are missing?

Ascential had us right click on the pallete and select "reset to factory default". This got rid of the entire pallete!!! They are now trying to figure out how best to restore it as it seems the configuration for all stages was blown away by this operation. That is, even when you go into cu...

After applying a critical patch for the PXEngine, the server jobs (not parallel), have an infinite number of sort stages in the stage pane. After clicking through about 200 of them the designer becomes unstable and crashes. This happens for all projects. Anyone ever seen a stage get duplicated to wh...

That is a limitation of Datastage. I use a few of the bulk loader utilites directly and these can use sequential files without corrupting my data. I can use Datastage as well, but I have to change chars to varchars because it thinks my data needs to be how it needs to represent it. WRONG. I don't wa...

ray.wurlod wrote:DataStage can handle a NULL in a Char(N) column, but the value that is used to represent NULL must have exactly N characters. Such is the definition of Char(N), surely? ...

No. The definition of null is lack of any value.

I am making an assumption that the datatype you are using is a char? Most DBMS's don't care if the character datatype is varchar or char. In fact, for many, a char null is actually defined internally as a varchar null. Which I think would be technically correct. A char null is not fixed width. It ei...

I assume you do not need a fixed length file. I thought the original requirement was to load a null value into the file? If so, changing the value to something which is not null is not loading a null value into the file. A null is the absence of a value. Thus, for a sequential file it would be the f...

From one of the previous posts. There is an environment variable APT_ORACLE_NO_OPS that can be set to 1 which will tell Ascential not to check for the existence of the table SYS.GV_$INSTANCE. Once this was added to our Job, it ran fine. So it would seem that it is used to disable any parallel server...

Just got patched that fixed. Ecase 91460. Tx. The patch did not fix the issue. It caused another bug where decimals would get truncated both before and after the decimal point. Example, 123456.9999 would get loaded as 123450.9900 Ascential released another patch. Ecase 91572. This caused another pr...