DSXchange

Worst case, if you've got some mechanism to identify records per load (timestamp, batch/load number, etc) then you can compare the counts from the source and the target as an 'after' process.

The only way it might work is if you add the 'Preserve Type' option and it seems that wasn't added until the 7.5.2 release. Let us know.

I would assume this is coming from the DB2 stage as the job is allegedly just two of those with a transformer in-between. As I've said, I've seen this before - when you have multiple Oracle stages in a job with a mixture of OCI8 and OCI9 stages, they don't play well together and can log this error. ...

Please post the complete, unedited error here and any other warnings or messages that seem pertinent. And a teensy bit of detail regarding your job design would be helpful, including details of your Merge stage usage.

Please post questions unrelated to 'Data Integration' in other forums based on the type of job - there are specific forums for Server and Parallel issues, this isn't the proper place.

Thanks.

vivekgadwal wrote:I will try the '00A' approach, but as I told you, the tool is throwing an exception and saying it is expecting nothing more than one character in that option

Don't bother, won't work. Created a small test file and not having much luck getting it to handle the 'short read' you need to do. So far.

Sorry, was working from memory. Forgot it was -logdetail from the command line and DSGetLogEntry from inside.

Interesting, was not aware of that little tidbit.

This symbol? :? CHAR(10) would be a LF but you shouldn't have to use a function to specify it. A CR is a CHAR(13) btw. I don't use this stage and the documentation is a little sparse, so I'm gonna have to guess on a couple of things. You may need to change the Record Type from Fixed to Variable sinc...

Bring up the online help from inside Designer, switch to the Index tab and then type 'dsget'. They'll all be there just below you in the list, including DSGetLogDetail.

You might be better off finding out why you have short records. Fixed is fixed and that means each record needs to always be just that - a fixed constant length. Can you verify if they start off that way on the source system? FTP can strip rather than preserve trailing spaces in records and thus hor...

They are in alpha order, so you'd need to keep going. There are 18 options in all and 'Preserve Type' is between 'Percent Coefficient of Variation Output Column' and 'Range Output Column'. If you don't see that, then I guess it was something added in 7.5.2 and you would get it if you upgraded.

As have I. And the only time I've had issues, they were easily isolated and repeatable, not something that goes away on a rerun. That seems to imply a resource issue more than anything else, but only in this job? :? I'm gonna need to ponder this, not sure where to go next. Hopefully someone else wil...

Sure! You'll need to enter it manually enclosed in pound/hash signs but it will work just fine. You can even hard-code some portion and parameterize another: /this/that/Big_old_file_#P_XML_FILENAME#_name.xml Where P_XML_FILENAME is a Job Parameter's name. As a general rule of thumb, we parameterize ...

Hmmm... this one will be difficult to track down, I'm afraid. If you Reset the aborted job, do you get any additional 'From previous run...' information in the log?