DSXchange

I don't have access to my 8.1 client here right now, all I'm saying is I'd be shocked as hell if it wasn't still there. Yes, perhaps somewhere else... is there no longer an 'sdk' branch?

It won't "exist" for Parallel jobs but certainly will still be there in the Server environment. Worst case, import it from your old installation. Which exact 8.x release are we talking about here, btw?

I know, it's just that sometimes it amuses me how long people will spend trying to build a 'one job' solution that could (more than likely) be troublesome to support and maintain when they could have banged out the oh-so-horrible multiple job solution on the first day. But that's just me. Best of lu...

There should be other errors logged as well that explain why it "cannot continue". And you need to find the .log file it generated which will have all of the gory details in it. From what I recall, this and the .ctl file it built will be in your 'scratch' area.

Your 'result' is the number of days between the two dates. You still need to tell us what your rules are for converting that to 'months' before we can help.

Both are 'hard disk' resources. If by 'RAM' you mean the physical memory installed on the server, that's not what the config file controls access to, which is what I assume the OP was asking in reference to.

This job worked fine in Development and Test environments but in Production some times it is giving desired output and some times not. First thought? What is different between the dev/test and production environments? Something, obviously. Could be as simple as production being the first place wher...

They why mark your server OS as 'Windows'?

I now repeat my previous advice to involve a SysAdmin.

Sounds like it is extended ascii... can you check the file with a hex editor or "od -x" and see what the hex value actually is?

Same here, with three nodes. Sounds like your tnsnames entry isn't correct... not wrong, just not correct for DataStage it seems. Ask your DBA to 'fix' it for you.

Welcome! :D You are aware that Oracle DATE fields are, in essence, a Timestamp as they carry a time portion, yes? Have you tried simply carrying it through your job as a timestamp and loading it as such? ps. The TIMESTAMP data type in Oracle adds fun stuff like milliseconds and TZ awareness, but for...

Yup, just move it from one type to the other. And as noted, the data types are not enforced in the job, but they certainly could be in your target, so be careful there.

What help do you need? That format *is* 'Oracle format' already and dates like that can be compared directly with no conversions needed.

I don't think so or they would have carted Andy off to the pokey by now. I just wonder how much someplace would charge for something like that?

vincentxy - in 'later' versions of DataStage, dsjob is installed on the client side as well so that can cut down (by one) the number of steps needed.