DSXchange

You asked, I answered. Nothing more than that.

Ask to your error, search the forums as it has been discussed in the past and there is even an ongoing post today on the same subject.

OK, found the reason for DS_RESENU: this older post which had an actual problem with that particular hashed file. You drew the wrong conclusion as you don't have "the same issue". Similar but not the same.

ps. I removed your post from that other topic.

You want to create a cartesian product... does the join stage support such a thing? A join with no keys specified?

Just... concatenate them when you derive the reason.

Check to see if one or both conditions were true and write one or both messages in that column. If you are still stuck, post your constraint expression.

pdv wrote:Do we need Oracle client in the unix server to be able to load Oracle loading DS jobs in the server.

Yes... as long as "the unix server" means the server that DataStage is installed on.

I'm curious how you got from the error that you posted to "DS_RESENU"? You've got a corrupted hashed file which an exact search for "Computed blink" here would reveal. I'm also curious why the Job Type is marked as Parallel.

OK, new server so we start at the beginning... do you have an Oracle client installed on the server? Have you edited your dsenv file to add the appropriate Oracle environment variables? I'm not sure what "working fine" would mean for LIBPATH so we'll leave that one alone for the moment but...

You have to 'read' all of the columns, that's the nature of sequential media. Feel free to immediately drop the columns you don't need but they must be read.

It's basic 'group change detection'. You increment a stage variable each time you see the same 'group'. For a new group, you set the count back to 1.

Leveraging the Sort stage with a 'Key Change Column' will simplify this for you.

Access to sys.dba_data_files is required but is not available;
please see your database administrator for select privileges.

That seems pretty clear to me.

Before-job subroutines are written in BASIC.

Sure.

I have no clue or I would have replied already. I also would have suggested contacting your official support provider other than the fact that CLOBs are not supported. However, they may know of a workaround or two, can't hurt to ask.

I would also suggest changing your expectations.

So... it's important that you let us know the extent of this error. Is this the first time you are attempting to use Oracle stages with DataStage? Has this worked in the past and suddenly stopped working? Is the problem only with this job or do all Oracle jobs have an issue like this? We need that i...

saj wrote:If it is published could you please let me know where I can find the same .

Already did.

... and that exact parameter name exists in the job and the value it is being set to is valid for the parameter type. Check the ErrCode.