UDT connection "Account Locked". Connection using tnsnames.ora file

[wallbertelicot]

Hi. So a little background here. We have several connections utilizing the tnsnames.ora. This is to have little maintenance on them in case the oracle host changes, we only have to change the entry on the tnsnames.ora file. This was working fine until recently.

Its kind of weird since the error "Account Locked" is only appearing when testing the connection via UDT. If we refresh a report (with a universe utilizing said connection), it refreshes fine. If we change the service from the tnsname entry to the full connection string, it tests fine. tnsping to the said oracle service also tests properly so we now that the tns entry is correct.

I've already tried restarting the connection server to see if it would resolve the issue, but no go.

Any ideas?

[Joe_Peters]

Yes.

Check tnsnames.ora on the computer that you are running UDT on. I'll bet it's different than the one on the BO server.

Also note that Oracle client has separate installations for 32-bit and 64-bit. BO server uses the 64-bit client while UDT uses the 32-bit client. Even if you have UDT installed on the BO server, they will be using different instances of tnsnames.

IDT allows you to optionally use server-based imddleware, in which case the server's Oracle client would be used. But UDT does not have that option - it uses the middleware software on the machine that it's running on.