DSXchange

ray.wurlod

Welcome aboard! :D You have a little more setting up to do. You are apparently using the ODBC stage, rather than the Oracle OCI stage; the latter would use the name in tnsnames.ora and not complain; certainly it wouldn't give an error with [ODBC] (the ODBC driver manager) in it! In the DataStage eng...

ray.wurlod

Yes. You have your UNIX system administrator set higher ulimit values. Expecially the one for maximum file size. "Unlimited" is a good value!

ray.wurlod

You go back to the providers of the file, and tell them that it's not an ASCII file - it contains binary fields, whereas you require EXTERNAL representations of numeric data. Another possibility is to investigate the Iconv() function, with a second argument of "MB" or, perhaps, "MX". The former conv...

ray.wurlod

In the stage that accesses the hashed file that is updated, do you specify "lock for updating"? Perhaps (if not) you are seeing contention on a group latch (= page-level lock) or even a record lock.

ray.wurlod

Some recent posts seem to suggest a belief that a server will support an infinite number of processes. That you are trying to size the server is commendable. Arnd's guideline is for one job - you must also have the discipline to avoid starting more jobs than the machine that you specify can handle -...

ray.wurlod

There is no need to restart DataStage after cleaning up a project or reindexing. Where did you obtain this assertion? It is, however, necessary to restart DataStage if you make changes to the configuration parameters in the uvconfig file. It's also necessary to restart DataStage so that it picks up ...

ray.wurlod

Try re-compiling the job in the recalcitrant project. DS seems to have lost track of one job component.

ray.wurlod

HOW did you try? Were the parameter references correctly spelled and correctly cased and enclosed in "#" characters?

ray.wurlod

Any error message with APT relates to a parallel job. This message suggests that you have a mismatch between the input and the output. Probably in the third column definition. The Sort stage must generate the same columns that came into it!

ray.wurlod

DSParams.KEEP is like the "before image" or "rollback segment". It allows DataStage to recover if an edit is abnormally terminated.

ray.wurlod

DSR_EXECJOB has to be a run-time error. Can you run the job from the Debugger? Have you checked the indexing in the repository? Recompiled the job?

ray.wurlod

Are you using hashed file cache? Are you using shared hashed file cache?

ray.wurlod

So the query will look like:

Code: Select all

Select sum(Tram_amt) 
from t1 
where arr_id=#Hash1_Arr_id# 
and dt='#Hash2_Bill_date#'

You can use job parameter references even in generated SQL. You can also use aggregate functions such as SUM (in Derivation in the Columns grid) in generated SQL.

ray.wurlod

I've never had any, but I don't use it much. Contact your support provider, or visit the eServices web site. Or search this forum.

ray.wurlod

The easiest answer is that the parallel engine does not have any support for hashed files. The server engine does not have any support for a "lookup stage". Different tools in different tool boxes.

Search found 53125 matches