DSXchange

Yes; upgrade to version 8, where there is no more Manager. You then import using the Designer. Apart from that I'm not aware of anything. Why do you want to do this? Actually that's a lie, you can create packages and load those using the package installer on the server. But that's archaic technology.

Put a WHERE clause in your SELECT statement. Pass the date as a job parameter. Use a reference to that parameter in the WHERE clause, for example

The NLS map for hashed files should always be NONE.

Hashed files are "inside" DataStage - the requisite mappings have already be done in the "boundary" stages.

You can not use the Schema File property unless you have a schema file to which to refer. And you can not have a schema file unless it contains a record schema - the same kind of record schema that you see in the generated OSH or in a job score.

For less than 30c (approximately Rs12) per day you can purchase premium membership which, among other things, will allow you to read the entire post. Premium membership is one of the ways that the hosting and bandwidth costs needed to keep DSXchange alive are covered. On that basis I can not accede...

What do you believe the data type should be? Were any other errors logged?

What is the transaction size and array size in the target OCI stage? Is the Oracle database exhausting some resource, such as the size of the rollback segment? (Ask your Oracle DBA to check while this job is running.)

It does not.

Category is only a logical construct (apart from categories for Templates), implemented as an indexed column in the pertinent Repository database tables.

The record schema will tell you that. The prefix is the number of bytes in the number that describes the length. Convert to date using StringToDate() function. For this to work your string must contain a valid date according to the date format string you specify, or according to the project's defaul...

What does the record schema in the schema file look like?

Your counted loop is based on a DCount() function. Can we please see that? Within the generated code that's where the handle$list variable name first occurs.

Using the key management routines will automatically increment the sequence value for the given sequence name. If the hashed file is in the project you can use a straightforward UPDATE statement to reset the "next value" of the sequence. You will find this statement by searching the forum.

DSJE_BADSTATE indicates that the job is not in a runnable state. I doubt that it's even being reset. Capture the jobinfo before and after your attempt to run, and show the commands you are using.

It's "hashed file", not "hash file". Be more precise about what you wish to do, and whether the hashed file is cataloged in your project's vocabulary (that is, whether the hashed file was created in the project or in a directory). The answer will be different depending on your response to the above.

Why are you using standalone.sh ? Can you rsh to the other machines mentioned in your configuration file?