DSXchange

Ramu, please start your own thread.

You first need to do what Arnd asked and confirm if the quotes are indeed being stripped or not. Does your 'other environment' source from a different database? If so, any chance there's legitimately no records that match the where clause?

Interesting... a search here for "OutOfMemoryException" gets 7 matches, 6 of which were various incarnations of the same problem posted by you and they go all the way back to November of 2008. The only other one was a problem someone else was having importing XML metadata from a gigantic x...

The Peek stage can be anywhere in the job, and no that behaviour is not environment specific unless (perhaps) your environments are different hardware platforms and/or operating systems.

Your job blew up. Seriously, that's all that means. As noted, there should be other supporting messages logged as to the cause, that or you need to Reset the job and look for a 'From previous run...' log message.

All CPUs will always be utilized. The license doesn't restrict that, it only serves as a check against what it finds.

If you set it correctly, it won't be the same error from "APT_CombinedOperatorController".

First suggestion is always going to be to disable operator combination so you can see where the error is actually being generated. Add $APT_DISABLE_COMBINATION to your job, set it to True and rerun the job.

You can specifically transfer control to a Terminator stage, but IMHO it's cleaner to only use 'OK' triggers and enable the compiler option to 'Automatically handle activities that fail'... it handles them by aborting the Sequence.

You'll need to stick with Approach 1, it's best all around. 2 doesn't do any kind of secure transfer and it is metadata driven, making it ok for a specific file transfer but not for generic file transfers. You could try treating everything as one large varchar field, but I'd go with a scripted appro...

This topic would be a great conversation starter for your DBA.

ray.wurlod wrote:You only get the common fields, the first five fields, from a dictionary listing. After that, the record structure is different for each different OLETYPE.

Ah, yes... forgot about that.

Not sure it would be simpler and what you'd get (if there was a way) is the number of columns the file is supposed to have while your first method will get you what it actually does have. Which are you after?

No clue. Why not ask your official support provider?

Not sure. Can you answer the question I asked, please?