DSXchange

Automatically handle activities that fail will, if you do not have an Exception Handler in the design, abort the job sequence. Click on Help next time you're in that page; it's well explained there.

Doubtless you are also seeking a document containing all the undocumented features.


I am not aware of any documentation outside of the various manuals and forums/blogs. There is certainly no "book".

Try setting the Field Width property for each of the fields.

If you're confident that all table definitions in a category can be deleted, simply delete the category in Manager or Designer.

The scores you've posted are for license checking, not for job execution. With more operators, there is more license checking to do.

What's the matter with the help already given? Did you de-duplicate the inputs?

Welcome to the wonderful world of parallel processing! I suggest that you need to delete (or truncate) upstream of the Oracle Enterprise stage (or even in a preceding job), using an operator that executes sequentially (or even a server job) - send zero rows to Oracle with the rule set to "truncate t...

Row counts in Designer are, at best, cosmetic. There are several conditions that can prevent them from being displayed. Don't worry about it. Use the "proper" row counts you can get in the log. What do you get in the Monitor?

That's only because you have operator combination enabled. What you have described as the "event" is actually the Orchestrate operator that is posting the message. With operator combination disabled the message would be posted by a transform operator (that, curiously, would have the same name as you...

AccentureTA wrote:Please pour in ur suggestions at the earliest.

Ur, I suggest, was a city in ancient Babylon.

Alas, the default is "Fail" - you would need to change the "import failed" rule to Drop or Output.

You need to re-assemble the various components of the source string into a timestamp format, and then apply a StringToTimestamp() function. One issue that you'll need to address is a consistent, two-digit, format for month and day; another is the business rule for the century in which a two-digit ye...

Can you post how the ranges were specified in the Lookup stage?

If you don't know you can not expect to tell DataStage how the record is "columnized" (a horrible word, but one used in IBM training).

You can read the record as a single VarChar and figure out in the job how to parse it, but you first need to know (or ascertain) what the rules are.

How are you attempting to run the job (e.g. from Director or from Designer, from schedule or from command line)? Have you tried simply closing the Director client and opening a new one? Have you tried running the job using the dsjob command line interface? If you don't answer the questions it makes ...