DSXchange

Hmmm... I would think you could do it via your SQL statement if you accessed the hash file with a UV stage. Also consider turning it around. Use the hash as a source and the ODBC information as lookups. Bring in everything from the hash and constrain it to the rows that fall between the two dates. T...

Ascential recognized that people would need to do this, so they have provided a utility to upgrade all jobs that use the OCI8 stage to use OCI9. You'll need to explore the cdrom yourself to find it, but it is there and is mentioned in the readme. Technically, the OCI8 stage will still work as long a...

Drop one in a job, open it and then click on the Help button. There should also be a pdf document for the stage in your 'Docs' directory under your client installation directory.

Time Zone? Now, as to the why...

Hardly... looked like a dead-even tie to me!

I'm guessing there is some reason why you can't use the 'AutoPurge' functionality of logs? It all boils down to the fact that you want to purge the logs of job run information, not clear them in their entirety which is what CLEAR.FILE does. Ray is letting you know it will remove everything from the ...

No, the stage itself is not modifiable and does not take parameters in the body of the email. You'd need to look into writing your own routine to wrapper 'sendmail' or whatever you are using for email. That way you could build it to take parameters or to do whatever it is you needed. Then use the Ro...

Simplest thing to do is replace your target Oracle stage with a Sequential File stage and write things out to a flat file. What does it look like there? Keep working the job until the output looks correct, then hook the OCI stage back up. ps. I personally find it "best" to work with Oracle dates as ...

Um... don't insert NULLs?

Can you make use of NVL in your source query? It's not generally a good idea to try to aggregate nulls.

You have a field in your source table that is not "properly" defined in the job. By that I mean the defined size is too small. Typically, this is because you have a LONG or NUMBER field you are extracting. Any chance of this? Note that I literally mean NUMBER as opposed to something like NUMBER(38)....

Running out of temp space? Make sure you specify in the 'Temporary Director' property somewhere that has plenty o' room. Leaving that blank defaults to the Project, which seems like what you are doing. It is generally considered to be a Bad Thing to fill that space up.

If you click on the 'Help' button in the Sort stage itself, you'll get specific online help for it. In the 'Overview' section, check out the 'Sort Criteria' topic, it explains how to set up the Collating Sequence Map you'll need.

You have to put the entire command in the Filter box, filename included just like you would from the command line. The Filename still needs to be included up top, but it (apparently) will not use it.

Wow... I'm surprised you can run much of anything in 128MB of RAM nowadays. The O/S alone wants that much.

Hey Ken, Standard ASCII sorting sequence is numbers first as they have a lower value than letters. Space and punctuation comes first, then numbers followed by upper case and then lower case letters. If you need to override this, I think you have other options rather than the external 'map' but I'm c...