Remote Export using OraDirect/VS2005

Graham · Post by **Graham** » Thu 07 Feb 2008 11:50

Selecting export from OraDirect/VS2005 on windows server 2003/Oracle 10 XE to a remote Oracle 10g database on Unix gives a TNS timeout error.
Any suggestions?

Alexey.mdr · Post by **Alexey.mdr** » Thu 07 Feb 2008 12:32

Check your connection string to the Linux server.
Try connecting to this server using SQL Plus.

Graham · Post by **Graham** » Thu 07 Feb 2008 12:47

I have tested the connection string within the OraDirect tool - the test indicated that connection was Ok. The tables and objects are visible in the explore pane. I have also used the same connect details reading and writing via Oracle .NET classes.

The DBA claims that the exp.exe tool can't be used remotely ??

I tried to just export a small table but received the same error message.

Alexey.mdr · Post by **Alexey.mdr** » Thu 07 Feb 2008 14:03

OraDirect .NET doesn't use exp.exe for export. What components of the product do you use?
When exactly do you get the error? Is it when you open a connection?

Code: Select all

OracleConnection.Open();

Graham · Post by **Graham** » Thu 07 Feb 2008 14:28

I connect using Database explorer but not in direct mode. I get a message asking the location of exp.exe. I change the Oracle home selected to be the XE installation home so that the utility finds exp.exe. I re-connect using the new home. I select the schema/user from the tree and from the right-mouse context menu I select the export utility. Selecting a local schema on the XE instance exports fine but selecting a remote schema/user from the Unix Oracle server begins the export but then fails with a TNS time-out error.

Alexey.mdr · Post by **Alexey.mdr** » Fri 08 Feb 2008 16:31

We are investigating this problem.
I'll let you know about our progress.

Alexey.mdr · Post by **Alexey.mdr** » Mon 11 Feb 2008 16:47

The export wizard of OraDeveloper Tools for Visual Studio simply launches the exp.exe utility with the parameters that you have chosen.
Try running this utility from the command line (without OraDeveloper Tools). If it fails, evidentially, the problem is in the incompatibility of XE client version and Oracle server (on Unix platform).