DSXchange

In server edition the Sequential File stage acknowledges that there are no data types in text files, only text. Any data types recorded are purely advisory. You must enforce the validation on a per-column basis as part of your job design. In enterprise edition (parallel jobs) the Sequential File sta...

Read the flat file using a Sequential File stage. In a Transformer stage pass along only the timestamp column, and mark it as Key. In the OBDC stage use user-defined SQL to construct a DELETE statement referring to this key in the WHERE clause. DELETE FROM tablename WHERE timestampcol = ? "Key" in t...

The name of the SQL table is the VOC (vocabulary) name of the hashed file. If you created the hashed file in an account, this is the same as the name of the hashed file. If you created the hashed file in a directory you need to create the VOC entry (search the forum for SETFILE command) then the nam...

That message is basically warning you that DataStage cannot find enough free memory to cache the hashed file, so that you are aware that it will therefore be read from disk (presumably more slowly than from memory). Solution is either to increase the cache size or to reduce the volume of data in the...

Code -99 is "other" errors; those for which there is no specific diagnostic handler within DataStage code. If you are getting T30 table full errors you have reached the maximum number of hashed files that can be open at any one time. (Remember that all the DataStage Repository tables are hashed file...

I think we need to see the script. When this occurs, is the job open in Designer, Manager or Monitor (Director)?

You can set this in the Constraints grid in a Transformer stage within the job.

I prefer never to abort jobs - see other posts on this topic.

Allocate a bigger string buffer (for example VarChar(4096)) to receive it.

Job parameters that are environment variables should have their values set not from a parameters file but by having the environment variable value set.

I tried to do the same thing with seq file. After all rows entered to Sort stage ( all 100000) the Job was ended immidiatly . It seems tahat Sort actually transfer rows but dont show it and rows count stay 0 from Aggregator With order by I get 2500 rows per sec . I want more because I have very lar...

Probably the easiest-to-understand way is to pre-store the maximum value in an earlier job (perhaps into a DataSet). Then pick up this value is a Lookup stage that precedes the Transformer stage, delivering the same value for every row processed. However, if you're going to work in the parallel envi...

Pre-sorting data prior to Aggregator is common practice, and helps the Aggregator stage to use memory efficiently (provided it's the grouping columns that are sorted). Are you claiming that no rows are output from the Sort stage? If so, please create a job that consists of your job up to the Sort st...

Use a separate Hashed File stage to update the hashed file from the stream. In the first stage, where you are reading from the hashed file, make sure that you set "lock for update", and do not use caching in either Hashed File stage.
Both Hashed File stages refer to the same hashed file.

Abort is NEVER necessary.

In the job sequence, detect that there has been a problem and use a trigger or a Nested Condition activity to determine not to proceed.

Please post on the appropriate forum, and supply a context for your question. Or do a search, either here or on Google, etc.