DSXchange

After it aborts, have you tried Resetting the job? If you do, is there anything in the log labelled 'From previous run'? This can give more clues as to the cause of the abort.

I still believe your error is caused by your mis-spelling the name of the function, and nothing at all to do with hashed files. As do we all. Peter's just trying to get a clarification on the "I am only trying to load 2000000 million records in to the Hash File" comment, which had me wondering as w...

Hmmm... glass houses and all that.

In the Windows environment, would this simply be a case of editing the uvdlock.config file and changing it to start=1? In any environment, actually, that is a perfectly acceptable way to enable it. Could also be 'dsdlock.config' depending on your version. What I would also like to know is how much ...

Search is your friend. Check this thread.

Or... if you looked at the thread I linked to, you could simply use the MONTH.LAST transform. No code required.

Yes it would, that's why I asked. What size did you declare it in DataStage? 38? If you did, try bumping the declared size of the field in your job to 40 and the message should stop. Don't change anything else, just the size of the target field. ps - Using ODBC? Why not use the native OCI stage?

Search is your friend. Check here for one discussion on the topic.

HOW are you loading the data? Is this an error from Oracle or a warning from DataStage?

I'd also be curious if you have any NUMBER fields in the target table. NOTE: not NUMBER(xx) but just NUMBER.

That should help.

One other option, if there is nothing in the Project worth saving, is to delete the project from the Administrator. You could then create a new, clean one and rerun your imports.

ray.wurlod wrote:Actually I probably should have continued to talk about zombie dsapi processes too, but didn't.

Too bad, could have scored our first Double Full Wurlod. Hey, it's not too late to go back and edit your post!

It's automatic and a remnant of the old way of doing Job Control. Go into Director and from the Status view, pull down the 'Tools' menu. You'll see an entry for 'Batch' and then the option to create a 'New...' one. It will look just like the Job Properties tab of a 'normal' job in Designer, but won'...

Tania wrote:We've done it before on Unix but haven't yet managed to make it work on Windows.

If you've done it for UNIX, there really shouldn't be anything different about making it work for Windows - all of the same functions apply. Except, of course, the direction the delimiters lean.

Possibly. Or do some of the things I mentioned in the post immediately above your first post. There's always more than one way to skin a DataStage cat.

Only problem is the Row Splitter / Merger stages don't show up until 7.x, but other than that...