DSXchange

Jeez, popular subject all of a sudden. You've already posted in the thread most relevant to this, anything we could say on the subject is there. And pretty much any post that mentions BCI is "relevant" to your issue.

Sainath.Srinivasan wrote:Remember seeing a similar post with issue in control file size thus resulting in truncation of control file.

That was when there were 400+ fields in the table.

I remember seeing something similar as well. In other words, possibly a bug that your official support provider could have a patch for.

One row in = one row out, 11 hashed lookups notwithstanding.

Two can play that game.

Not sure how anyone here can really help, seeing as we're not there and not able to examine both servers ourselves. However, you are, which is why that duty falls to you and yours. Something is different between the two, something other than simply the CPU. Sure, there are teeny differences between ...

Exactly... what were you planning on using for the time portion here? If not another field or source then you'll need to do what Ray has shown.

Only point of contention is that Ray mentions there being no output link on the first transformer when combined into a single process and thus the problem that IPC 'fixes'. Problem is you said it worked fine as an after-stage routine when associated with the first transformer, it was the second one ...

Scott, as Mike noted that sql is only "similar" because the same tables are involved. The actual mechanisms are totally different. All that setting the Transaction Size to 0 means is to allow all records to be written to the database before the 'commit' is executed. Yes, that means you get...

I don't know FoxPro but I sincerely doubt that is correct. Database is just typically the name itself and shouldn't contain any user/password info if that's what you are doing - that would come as part of the stage setup, the credentials needed to make that connection at runtime.

Different poster but a remarkably similar question.

viewtopic.php?p=323634

Asked and answered.

Not sure how anyone here can really help, seeing as we're not there and not able to examine both servers ourselves. However, you are, which is why that duty falls to you and yours. Something is different between the two, something other than simply the CPU. Sure, there are teeny differences between ...

Not sure how anyone here could help, you need to thoroughly check your Citrix server and what is actually installed on it. Perhaps at one time it did have 6.0 installed. Maybe these 'few specific users' are going to the wrong machine? Who knows.

Ah... the Masked Decimal conversions. They're not really all that well explained in the docs, you mostly have to infer how they work from the examples they include. What exactly does "MD2-" mean? A scale of two with a trailing minus sign?

Sure, all kinds of ways to skin this cat. And I edited my post to remove the "End" statements from the code as they are not used in a derivation.