DSXchange

I've seen behaviour like this before, it was a bug in the client from what I recall.

What happens if you try to set it to auto-purge after x number of job runs, instead of days? Does that stick?

Well, someone who actually uses ODBC with Oracle will need to chime in as I don't, preferring to use the native stages. Pushing it through as a char 6 doesn't sound quite right... I would *think* you are going to need time information in your string, not just the date. And I would guess that And jus...

Have you checked the docs for the ODBC plugin and verified the format it is expecting? People have been giving you advice assuming you were using OCI, but I'm not sure if it is exactly the same for ODBC. Also, just for grins, what are you defining the field as in DataStage?

What stage are you using? ODBC?

How tight are your PL/SQL skillz, Tony?

Yah, they are valid... just not usually written that way. The sizing of the COMP-3 stuff can be strange at first, but the rules are simple. If you haven't found them yet, they are: * Count the number of digits. * Add 1 for the sign if present. * If the total is odd, add 1 more. * Divide by 2. So as ...

How can I see what patches were installed in the DataStage Server? The patches mentioned above are Operating System patches, nothing to do with DataStage other than their effect on it. Check with your System Administrators, they can give you details about patch levels. All of the executions of the ...

It means you've created a "circle" or "loop" in your data flow, something that is not allowed and is caught by the compiler. Searching for "linear dependencies" shows several other discussions, one of which is here. Check that thread out or search for the others for some examples of the problems and...

Not enough information. What happens when, after the job aborts, you reset it? Note, this is not recompile, it is the 'Reset' option available in the Director, the two backwards facing arrows like 'rewind' on a VCR. Let us know if, when you do so, any entries labelled 'From previous run...' appear i...

No, sorry... no magic bullet. At least not on the Server side. If by chance your data is sorted such that you can take advantage of supressing repeating groups, you can do the fairly standard Stage Variable thing to check for duplicates. Let the first value pair through, suppress the rest. I'm guess...

I'm pretty sure you do, Tony. I seem to recall it being documented in the .pdf or online help...

The other option is "Fully Generated SQL", I believe. From what I recall, after you build the query you can click the 'Synchronize' button and it will create whatever columns are required to support the query. I think. I tend to avoid that particular way of doing things.

The input is coming from character field like this: 20041030 I'm a little confused as well. This seems to match your desired output format and would (usually) mean no conversion was required. So, what are we missing? For what it's worth, DIGITS is a Built-In Transform that simplifies the call to OC...

DIGITS will work fine and will remove all non-numerics. Phillip just needs to get his conversion tweaked a little.

You could change the derivation of the stage variable to make it a little easier - or at least what I think is a little easier on the eyes and brain. You don't need to explicitly set svAddItPrep to @TRUE or @FALSE: svTrimbOrgtgIbtN = 2610 or svTrimbOrgtgIbtN = 2710 or svTrimbOrgtgIbtN = 5810 or svTr...