DSXchange

No, you've already done what needs to be done. Do you have another set of eyes that can look at what you've done? I'm not sure what else to suggest other than open a case with your official support provider. Perhaps there is a patch needed for your version...

Kernel parameters are specific to your operating system. Go have a chat with your SysAdmin.

Always a good idea to document what you are doing. Me, I had no clue what "Stuff" should be doing, never having had the pleasure of SQL Server exposure so had to go look it up: The STUFF function inserts a string into another string. It deletes a specified length of characters in the first...

You cannot use the same file as both source and target, period. Windows is a little more militant about it but even in your UNIX it is not "working fine" although for a small number of records it can appear to. Write to another file and then replace the original after job.

Ah... well that would explain the mess you are in at the moment. Hope it all works out well.

You said logs, plural. Does that mean you are seeing this same issue on multiple logs or just that you were reading multiple logs and this one errored? A search found only one mention of this message here and that back in the Oliver archives for version 4.1 so not exactly a common one. Worst case I ...

There really isn't anything more to it, all we did was switch from 64bit to 32bit libraries, in case that was the issue. You're certain the values you are using are correct? Can you source the dsenv file from the command line and then successfully connect via sqlplus?

If it can 'read the double " in the column' successfully, why not simply remove them using Convert() afterwards? Or reduce it to a single occurance if that's what you need.

If you have both an $ORACLE_HOME/lib and $ORACLE_HOME/lib32 directory, try switching to the latter.

Not counting getting the disk space back, there won't be any effect other than depriving your official support provider the opportunity of helping solve your core dump problem.

A couple of things. This is the proper forum for "general" questions (such as questions on job sequencing) which is why I moved your post here. Secondly your subject should be related to your post, "Hi" doesn't really cut it around here so I changed it. As to your actual question...

Did you "see the log file for the Oracle specific message"? That will tell you what failed. You'll find the log (which is named in your message) in your scratch area from what I recall.

So are you saying the records for one table have three fields while the records for the other have four fields? That would work. Can you post samples?

Do you have a way to determine one layout from the other?

Then skip the introduction. And I thought you still had an error 4 with the parameter so not sure how that is "working perfectly". :wink: If the angle bracket notation is not supported there, use the EReplace() or Convert() functions that I'm sure we've already mentioned to strip the @FM.