DSXchange

I doubt you'll be able to 'change the metadata' so that both fixed-width files can be read correctly with a single stage. Delimited, perhaps, but not fixed-width. If they've built this file incorrectly in this 'other environment' have them correct it. If the data looks identical perhaps there is a r...

A Google search for your message "The source parcel length does not match data that was defined" returned about 5M hits, so there should be some help for you out there. Your record may be perfect but it doesn't match your metadata, it would seem.

Reset the aborted job and let us know the contents of any 'From previous run...' log message that shows up.

That's... unfortunate. You'll need to detect the format and standardize on one but - how will you know for certain which is which?

Those trigger expressions are used to check for conditions after a job completes, for example to see if it aborted. And as one might expect, the 'custom' one lets you write your own condition when none of the standard ones are appropriate. To force a job to about based on a data condition, you'll ne...

Yes there is a size limit, no there's no way to increase it and that limit (in older versions at least) has been posted here in the past. It can vary by stage and version so best to ask your official support provider for the specifics of whatever version you have.

Clearing makes it empty, not smaller. If you want to free up the allocated space, you'll need to use the 'Delete' option to drop it and then recreate it using an appropriate minimum modulus.

In the interim, it would help if you answered my question - how were these hashed files created? Pathed or in an Account?

I have overwritten a hashfile with a file of zero records Tell us exactly what this means (file of zero records?) and post what you see when you do an "ls -la" from inside the directory. For the record, an 'empty' hashed file can be (basically) any size with space allocated but not used b...

Has this error occurred again? Your sql didn't cause anything and (IMHO) redesigning the job is a waste of time... unless your error is reproducible.

Check 'jobinfo' with DSJ.JOBINTERIMSTATUS to see of the job is aborting, if so do not execute the script.

Ok... go ahead. As noted, you've got a pivot on your hands and a vertical one at that. What have you tried? Do you have an actual question?

You've got an NLS issue on your hands. Doing an exact search here for "chinese characters" found 51 other posts on the subject, more than likely one or more will help you.

Nope, you hunt for the sweet spot - go up until it blows, then back it down a notch.

Beware that deleting a pathed dynamic hashed file is trickier than Craig would have it seem. Well, to be honest we hadn't gotten to the gory details of the 'how' yet. :wink: I've had good luck using a wildcarded recursive rm as we didn't have 'overlapping' hashed file names (for lack of a better te...