DSXchange

It's because of 'automatic' mode - read how it actually works. Best to switch to manual and bulk load the data yourself.

Sure you're not thinking of 'Validate'?

No functional difference from the original derivation.

kberisha wrote:I also checked the DDL of the table. only for or maybe five are decimal. But on those fields decimal I have Hardcoded values.

Examples of the hardcoded values, please. That's where I'd start.

As per my company policy I cant use crontab or any other scheduler to schedule this job. My advise - push back on the policy. I'm adding this to my list of 'silly ass policies' we see here way too often that make absolutely no sense. Do you have an Enterprise Scheduler like Control-M? It should be ...

Double-click on the phantom error in the log to get more information about it. Also try resetting the job from the Directory as Arnd suggested and looking to see if a 'From previous run...' entry shows up if the job aborts as part of all this. ps. 'Phantom' is just the DataStage term for the 'backg...

I'm having trouble running my job. where it shows an error like this: jobName..oracle table name: ORA-01722: invalid number Where to, all of the fields (all of them) are Varchar in Oracle, and more over I'm not using a conversion from numeric to something else. Not possible... there's no way you ca...

No idea... but I'd report it as a bug to IBM/Ascential and see what they have to say about it. What version of DataStage?

Yah, that was a little tongue in cheek... thanks for following it up for me, Vince.

The 'junk' values being generated is the 'funny error'? Are these junk values the contents of the 'Col' field or something else entirely? You may want to post some examples - what comes in the Col field and the result of the derivation. I would guess the IsNull check is no longer returning True for ...

Ah... good. So now this can be marked as 'Resolved', yes?

For 'large' files, the suggested change is two-fold: 1) Change the Folder stage to deliver only the fully pathed filename and not the contents of the file. One field rather than two, in other words. 2) Change the XML Input stage from an XML Source method of XML Document to URL/File path instead. Thi...

You need to be more specific. You should be perfectly able to get the same status code as you've always gotten as they haven't changed. Post your methodology - job design, trigger values, etc - whatever it will take to make us understand your problem.

Apparently nothing.

Are you sure you are executing these commands on the server where DataStage is installed?