DSXchange

It's been way too long but here's a crazy thought - what happens if you disable the 'Aggregate all rows' option? Have you tried that yet?

Thanks, hadn't found that mentioned when I researched for the post.

I had to build something like this to protect myself from the same thing - unannounced changes to our source system. Rather than go table-by-table, I took a more metadata driven approach utilizing the various views in the databases. Something like this, high level: 1. create a driving xref table of ...

That is an option very specific to DB2. Read the Oracle section.

Okay, I'll bite. No, there isn't anything random about it as that would make absolutely no sense. How about more details - I for one would be curious what your source is that is sending these rows and how it is configured. Would also like to know input versus output results. Saying "It sets the...

Yup - there's a specific chapter on Oracle in the pdf including cursor requirements.

Why? Any idea what is driving this "need"? You've got something that is working, after all. :? As noted by Ray, there is only encryption with this being what I assume he meant. However, it does not note the type of encryption - a critical piece of information if you ever want to be able to...

Seem to recall that being included as part of the Stored Procedure stage documentation... did you check there?

Well worth checking out... let us know if that turns out to be your issue!

Out of curiosity, what kind of encryption are you thinking about / needing to do? And just to be clear, this is about handling an encrypted column in a file, this rather than taking a single column from a file and encrypting it in some other target, yes?

Welcome. If you gone through all of the posts here and already done what you can then we can dispense with all of that and go straight to the heart of the matter. So, you're down to the fact that dsadm has no such issue while dsops causes the timeout? Can you go into detail about how you setup this ...

Another option, since the results are returned in a dynamic array, is to use array notation. That can help simplify things if you ever need to return something other than the first item in a list of returned values.

Execute_Command_1.$CommandOutput<1>

Try removing the Field Mark before you send it to the Start Loop stage, perhaps in a User Variables Activity stage. This rather than the Execute Command.

Ray noted the resolution in his very first reply.

Hiccups? You betcha. I don't care what tool you migrate to, ETL or otherwise, there will be issues early on - either with the tool itself or your understanding on how to use it. Especially when you constrain the migration to recreating exactly what you have (and exactly how you do it) in the old too...