Our servers are both 10g and 11g. The one I was testing against the most is 11g. So I thought the 11g client might help. Maybe if...

Well, a full reinstall of the Oracle client software (Oracle ODAC 10.2.2.21) fixed things. Twice before I had tried installing the 11g ODAC software and pointing to it and...

Okay, I tried all the ProtectionLevel nonsense about a dozen times. Plus, we reverted all packages back to the last copies that ran. All of those settings are...

Well, it's definitely not "our company" since the only place everything broke is on the one machine where we tried to use SSIS configurations. All the other SSIS flows,...

I'm not exactly sure what you mean by all this ...

Our flows access SQL Server as well. And they access Oracle with the Attunity drivers. In all those...

No, we tried all those suggestions several times. And, regardless of what we tried, we reverted everything back to just using package level passwords but those no longer work....

I am setting persist (save password) to true. I see it true (1) in the package XML file. But it's never being saved. Either that, or it...

That's the policy here. I'm a consultant so I'm not going to question it. I shouldn't have to change policy to get around what appears to be an...

There is no problem with TNSNNAMES.ORA. Whether I use 10g or 11g, my TNSNAMES file points to one central place and I can connect to all Oracle databases...