DSXchange

So... which part of what you posted is the 'not working' part?

ps. Redirect stderr to /dev/null

And you know I meant internally. So happy I could provide sig fodder as well.

Sorry... "re-made"? Other than that, you don't think there were any differences between the two attempts?

First question, did you try simply moving one to the other without any conversion? I'd also like to point out that this: SELECT sysdate from DUAL; 06-FEB-15 Really means nothing as whatever tool you are using could have decided on the format to show you - the external format to show you. And if you'...

No dollar or pound/hash signs needed, just the name of the parameter. When you say you're "not getting the desired result", what result are you getting? Specifically with your last 'combination' listed.

I... assumed that was a typo.

Attaboy! :D

See this post for a discussion of dates and their lack of formats. Yes, it's about Parallel jobs but a DATE is a Date is a date.

Server jobs are very forgiving... what happens when you just move one to the other?

Do you understand the why of it?

You needed to execute the executable file rather than source it.

sam334 wrote:Input is delimiter file

Then your data type for input is a string. If you are able to successfully read it as a DATE then there's no conversion to do as the stage has already done that for you. Failing that, use the StringToDate() function.

Sorry but as we've discussed here quite a bit, a DATE field does not have a format. It's only when you pull it out into a string that you apply an external format to it, two of which you have shown. Meaning, there is only a conversion required when a string is involved... not two DATE fields. So, wh...

satheesh_color wrote:we could see the performance of the job is very less

Compared to what?

Nailed it!

:D

Have you tried running it manually from the command line as requested? If you still get that error, involve support. If it won't even run from the command line (should give you a basic usage error) then it's corrupt or otherwise invalid.

Through another job or a custom routine or a script or whatever mechanism you feel comfortable building and supporting. And then the rest, yes. I would leverage a Server job and USER_STATUS for the first part in your shoes.