Import Tables Fails - Not Connected to ORACLE

BravoZulu

Member
Using PL/SQL Developer 9.0.6 on Win7 64 bit PC against Oracle 11g DB.
Using the Export Tables menu item to create a PDE file (not compressed). When I try to then import those tables into another instance the application displays messages that it is dropping the existing tables, creating the tables, analyzing tables... disabling triggers.. and then the green progress bar stops but I quickly get a error dialog ORA-03114: not connected to ORACLE. This locks the application up such that I can't tab over to the Log to see if there is any additional information. Data has been added to the first three tables in the list of 105, but that is all.

As an alternative, I attempted to import that tables one at a time from the list. This works fine for awhile but some tables throw ORA-24909: call in progress. Current operation cancelled. This error also locks up the application.

What is going on? I am trying to determine if there are particular tables that cause the second error or if it is random.

And a possibly related question... should the uncompressed PDE file be readable? I'm seeing various odd characters before the "create table " statements in the file.

Thanks for any help.
 
I was able to go back to PL/SQL Developer version 7.# and the export/import works just fine. I was able to try it out with version 8.0.4 as well but this fails similarly to 9.0.6. I imagine this is some kind of configuration issue. Does anyone have an idea what it might be?

 
Can you go to Help > Support Info, press the 'Copy all pages' button on this info screen, and paste this text into an e-mail reply?
 
PL/SQL Developer
Version 9.0.6.1665
01.70303 - Unlimited user license
Windows 7 (64-bit) 6.1 Build 7601 (Service Pack 1)

Physical memory : 4,194,304 kB (4,194,304 available)
Paging file : 4,194,304 kB (4,194,304 available)
Virtual memory : 2,097,024 kB (1,880,420 available)

Parameters
C:\Program Files\PLSQL Developer\plsqldev.exe

Preferences
Session mode: Multi
OCI Library:
Use OCI7: False
Allow Multiple Connections: True

Preference Files
C:\Program Files\PLSQL Developer\Preferences\Default\Default.ini
C:\Users\xx001\AppData\Roaming\PLSQL Developer\Preferences\xx001\default.ini

Plug-Ins
*Active Query Builder (C:\Program Files\PLSQL Developer\PlugIns\ActiveQueryBuilder.dll)
*PL/SQL Documentation (plsqldoc) (C:\Program Files\PLSQL Developer\PlugIns\plsqldoc.dll)
(* is Active)

Aliases
BMT
CCP
CDHD
CDHDS
CDHP
...

Homes
OraClient11g_home1 (C:\oracle\product\11.2.0\client_1)

DLLs
C:\oracle\product\11.2.0\client_1\bin\oci.dll

TNS File
C:\oracle\product\11.2.0\client_1\network\admin\tnsnames.ora

Using
Home: OraClient11g_home1
DLL: C:\oracle\product\11.2.0\client_1\bin\oci.dll
OCI: version 11.1
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0

Character Sets
Character size: 4 byte(s)
CharSetID: 873
NCharSetID: 2000
Unicode Support: True
NLS_LANG: AMERICAN_AMERICA.AL32UTF8
NLS_NCHAR_CHARACTERSET: AL16UTF16
NLS_CHARACTERSET: AL32UTF8
 
As a test, can you modify the PL/SQL Developer shortcut and add the following NLS_LANG parameter?

"C:\Program Files\PLSQL Developer\plsqldev.exe" NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252

Let me know if this affects the problem.
 
Added the parameter to the shortcut (and confirmed in the Support Info shown below). Same result... "Not connected to ORACLE" when trying to Import.

Parameters
C:\Program Files\PLSQL Developer\plsqldev.exe
NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252

Character Sets
Character size: 4 byte(s)
CharSetID: 873
NCharSetID: 2000
Unicode Support: True
NLS_LANG: AMERICAN_AMERICA.WE8MSWIN1252
NLS_NCHAR_CHARACTERSET: AL16UTF16
NLS_CHARACTERSET: AL32UTF8

 
Sorry, I noticed your earlier post asked for all the support pages.

--- Registry ---

SOFTWARE\ORACLE
inst_loc = C:\Program Files (x86)\Oracle\Inventory

SOFTWARE\ORACLE\KEY_OraClient11g_home1
ORACLE_HOME = C:\oracle\product\11.2.0\client_1
ORACLE_HOME_NAME = OraClient11g_home1
ORACLE_GROUP_NAME = Oracle - OraClient11g_home1
ORACLE_BUNDLE_NAME = Enterprise
NLS_LANG = AMERICAN_AMERICA.WE8MSWIN1252
OLEDB = C:\oracle\product\11.2.0\client_1\oledb\mesg
OO4O = C:\oracle\product\11.2.0\client_1\oo4o\mesg
ORACLE_HOME_KEY = SOFTWARE\ORACLE\KEY_OraClient11g_home1
SQLPATH = C:\oracle\product\11.2.0\client_1\dbs

SOFTWARE\ORACLE\KEY_OraClient11g_home1\OLEDB
CacheType = Memory
EnableCmdTimeout = 0
ChunkSize = 100
DistribTX = 1
FetchSize = 100
OSAuthent = 0
PLSQLRset = 0
PwdChgDlg = 1
SchRstLng = 10000
UserDefFn = 0
DisableRetClause = 1
VCharNull = 1
TraceCategory = 0
TraceFileName = c:\OraOLEDB.trc
TraceLevel = 0
TraceOption = 0
SPPrmDefVal = 0
StmtCacheSize = 0
MetaDataCacheSize = 0
DBNotifications = 0
DeferUpdChk = 0

SOFTWARE\ORACLE\KEY_OraClient11g_home1\OO4O
CacheBlocks = 20
FetchLimit = 100
FetchSize = 4096
HelpFile = C:\oracle\product\11.2.0\client_1\oo4o\doc\oraclec.chm
PerBlock = 16
SliceSize = 256
TempFileDirectory = c:\temp
OO4O_HOME = C:\oracle\product\11.2.0\client_1\oo4o

SOFTWARE\ORACLE\ODP.NET

SOFTWARE\ORACLE\ODP.NET\2.112.1.0
DllPath = C:\oracle\product\11.2.0\client_1\bin
TraceFileName = C:\odpnet2.trc
TraceLevel = 0
TraceOption = 0
PromotableTransaction = promotable
SelfTuning = 1
StatementCacheWithUdts = 1
UdtCacheSize = 4096
PerformanceCounters = 0
MaxStatementCacheSize = 100
DemandOraclePermission = 0

--- Path ---

C:\oracle\product\11.2.0\client_1\bin
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0\
C:\Program Files (x86)\PRISM
C:\Program Files\BASHome\Secure
C:\Program Files\BASHome\x86\Secure
\\ronco\public\dnt\tools
\\ronco\public\dnt\tools\inetW7\bin
 
FWIW. I've attempted doing the import with a single table in the PDE file. It seemed to be the first table that didn't get any data when I was doing the batch import. The single table fails with the same "Not connected to ORACLE" message. Table has 5 rows. Fields are 6 NUMBER, 5 VARCHAR2, 2 DATE and 2 CLOB fields. 3 of the CLOBS are empty, and the other 2 have about 300 characters of HTML.

Tried the same single table process with another simple lookup table without issue.
 
To obtain some more diagnostic information, can you modify the shortcut and add the DebugSQL parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" DebugSQL

Reproduce the problem and send me the debug.txt file that is generated in the PL/SQL Developer directory or in the %APPDATA%\PLSQL Developer directory (e.g. C:\Users\\AppData\Roaming\PLSQL Developer).
 
Back
Top