topic Re: Oracle Direct Connection failed for active Windows 7 client in Data Management Questions

Oracle Direct Connection failed for active Windows 7 client

JamesFox1 — Thu, 01 Sep 2011 01:10:43 GMT

When I try to establish a direct connection from a Windows 7 client I get the following message:

Failed to connect to database. Underlyling DBMS error ORA-28547. Connection to server failed, probable Oracle Net Admin Error. No extended error.

Yet the database is up and fine. I can SqlPlus, use other DB tools,..etc. Error implyed a tnsnames error with extproc maybe but others in my office can direct connect fine with no problem. Just not directly with ArcGIS. If turn the ArcGIS SDE service, I can connect through that.

This problem only occurs when I "load" up my Windows 7 box with other processes (lots of office, spreadsheets and word docs open,..etc). I reboot my Windows 7 client and this goes away.

Everyone else in the office is running from XP cleints.

Server:

Windows 2010 Server
Oracle 10.2.0.3.0
ArcGIS 9.2

Client:
Windows 7
ArcDesktop 10.0

-Jim

Re: Oracle Direct Connection failed for active Windows 7 client

VinceAngelo — Thu, 01 Sep 2011 10:23:27 GMT

Direct Connect uses local Oracle client libraries, but your software list doesn't show
Oracle installed on your W7 host. Which release do you have loaded?

If you have 10.2.0.3 or higher, then an Oracle forum might be more useful in tracking
this issue down.

- V

Re: Oracle Direct Connection failed for active Windows 7 client

JamesFox1 — Thu, 01 Sep 2011 14:41:19 GMT

Oracle Client: 10.2.0.1.0 installed on the W7. I looked up the error in Oracle forums but it points to general tnsnames issue which if it were the cause then probably no clients should be able to connect then. Quite perplexing.

-Jim

Re: Oracle Direct Connection failed for active Windows 7 client

VinceAngelo — Thu, 01 Sep 2011 15:18:23 GMT

No Esri certification test involving a 10.2.0.1 Client has ever succeeded. As a rule, your Oracle
Client should be at least as high as the RDBMS Server to which you connect (which in your case
happens to be the 10.2.0.3 minimum required for ArcSDE).

If you apply the 10.2.0.3 patchset to your Client, the problem will likely disappear. Alternatively,
you can install the 10.2.0.3 (10.2.0.4?) client certified for use with W7.

- V