DSXchange

It can be as simple as concatenating all of the field values into a single stage variable much like you were going to compute a checksum. In 8.5+ there are two functions that automate that: SaveInputRecord() and GetSavedInputRecord().

Are you certain as to the cause and did you mean "index becomes UNUSABLE"? More typical during a bulk load would be for a unique index to become unusable due to loading duplicates to it.

Still would like to know if we're talking about a Server or a Parallel job.

You can't upload anything here. You can, however, have your image(s) hosted at any of the free image hosting websites out there and then link to them here using the "Img" tag.

Please confirm for us you are indeed talking about a Server job and let us know your exact 8.x version.

Multiple lookup stages, one for each of the combinations listed.

Having a new issue = start a new post.

Close this one if it is Resolved and create another with the details of your import issue.

Did you try what was suggested in the other post where you asked this same question?

Or simply enable the "Include job status in email" property in the stage.

You can't, not even in a Server job as a true 'truncate' is not transactional and cannot be rolled back. You would need to do a transactional delete of all of the table data first and then (as you noted) perform the load in the same unit of work for a load failure to roll you back to your original s...

And just to be anal, this works in SQL Server. You didn't have a DataStage issue.

As far as I know, it's still a manual process and can take a day or three.

So, in other words small and easily handled by a Server job.

Sorry, not seeing a question here. Can you be more precise about the issue you are trying to solve here?

elavenil wrote:This issue occurs for everyone who logs into this project.

That's an important bit of information and rules out the whole client-side possibility. Rather than trying to "figure this out" I'd suggest getting this in front of your official support provider if you haven't already.

Help us out with one thing - does this error happen for other developers in your office or just you?