DSXchange

shershahkhan wrote:its a migration project, i have changed the code to Teradata for more then 2000 jobs.

You might want to expand a little bit on that... 'changed the code' from what? Didn't this come up in your testing before you did a wholesale change to 'more than 2000 jobs'?

samsuf2002 wrote:If I restart the sequence again it will run the above job which was not running but will abort at some other position.

With that same odd 'not running' error?

Never used it but I'm pretty sure there's a Netezza stage for the Server product. It would be one of the optional plug-ins, though, one you would have to have chosen to install when the server was setup but you can go back and add it at any point. Any 'Enterprise' stage is only valid in a Parallel j...

Even the OCI8 stage can interface with 10g using an 8i client. I don't think 10g was 'officially' supported until the OCI stage was included in 7.5.1a but that's not to say earlier versions were not compatible.

Cool. Not sure how much I actually helped, but glad you found the problem regardless.

No clue. Suggest you delete the ODBC stage, add it back to the job and see if that straightens things out for you.

And a SELECT as well.

Figured you could shell out, but still... [shrug]

Hello, it's me, just to tell you that I won't try with 64-bit hashed file, as the set up is for all the projects and I all the projects are not mine, so, I'll stay with my 2G file... What does that mean? No-one suggested you turn on the 64BIT option for the entire install but rather just create thi...

Wow... tested it myself and it actually does work. For both TO_DATE and TO_TIMESTAMP. Boggles me mind. :shock: OK, with that out of the way I guess we're back to your format difference. If I had to guess, I'd say the problem is the fact that you're using a 10g client to talk to a 9i instance. It wil...

:? I find it hard to believe this actually works: TO_TIMESTAMP('20090227', 'YYYY-MM-DD HH24:MI:SS') when the mask doesn't match the data format, unless TO_TIMESTAMP is *very* forgiving of user errors. I need to test it. What Oracle stage are you using, OCI? And your actual Oracle target datatype is ...

If your target field is a DATE, you should have TO_DATE in your sql, not a TO_TIMESTAMP. And you must match the format mask being used so the routine must return a full YYYY-MM-DD HH24:MI:SS timestamp for what you posted to work.

What do you consider to be the "DataStage system prompt"?

If you are talking from inside a dssh/TCL session, I can't think of a single reason to do that... do it from the O/S.

Logs are stored in tables in each Project repository named after the internal number associated with their parent job. There's no reason to go directly after those tables, however, as there is a perfectly good API for accessing that data. From the DataStage side, open up the online help Index tab an...

Short answer is 'no'.