Bug in "Import Tables..." Tool

[JDietz]

Hello,

today we found 2 bug(s) when we tried to "import" a sql-script with the "Import Tables..."->"SQL Inserts" tool.
We use PL/SQL Developer 7.1.5.1396 directly on a Windows 2003 R2 Sp2 x64 machine which also serves a 10.2.0.4 x64 Oracle Database.
In order to get PL/SQL Developer working we use a proper x86 Oracle Instant Client environment.
Our target was/is to import a 250mb "SQL Inserts" script.

Bug #1:

When we use the "Use Command Window" option then the PL/SQL Developer instance runs out of memory, i.e. it hogs a huge amount of memory until it reaches the 2GB x86 memory limitation.

Bug #2:

When we use the "Use SQL*Plus" option then the import does not work out because the sqlplus.exe from the Oracle x64 home directory is automatically suggested. But the call to that x64 sqlplus.exe does not work out due to the x86 Oracle Instant Client environment for PLSQL Developer.

If a user chooses the correct x86 sqlplus.exe the import works fine. But after restarting the PLSQL Developer the original x64 sqlplus.exe is displayed instead of the manual selection :-(

Maybe you can offer an option for the correct SQL*Plus exe via the preferences menu.

Regards,

J

 

[Marco Kalter]

I would have expected that the SQL*Plus executable is used from the Oracle Home that PL/SQL Developer is using. This will not be an x64 home. We'll check it out.