Export Tables - Oracle Export

[CTucker]

I'm trying to use the Export Tables tool with the Oracle Export option. I select a handfull of tables, set my options and start the export but nothing happens.

The following command is what appears in the log:

C:\orant\bin\EXP80.EXE parfile=c:\Temp\plsexp.par

However EXP80 reports the following:

LRM-00109: could not open parameter file 'c:\Temp\plsexp.par'
LRM-00113: error when processing file 'c:\Temp\plsexp.par'

If I look in the c:\Temp the file does not exist.

It appears that the parameter file does not get created by PL/SQL developer.

Is this a bug or am I doing something wrong?

Thanks,

 

[Marco Kalter]

I'm not aware of any problems. What is your PL/SQL Developer version? Are you using the latest 5.1.1 release? This version will keep the parameter file, whereas 5.1.0 and earlier will delete it after the export.

------------------
Marco Kalter
Allround Automations

 

[CTucker]

I was using version 5.1.0 but since have upgraded to 5.1.1. The problem is that if EXP80 fails the log does not actually show anything meaningful. It is only when EXP80 actually runs that the log has output. So when I tried to recreate the call to EXP80 to see why it failed the error was that parameter file was not found (since version 5.1.0 deleted it after the run). With version 5.1.1 I was able to rerun (since the parameter file is not deleted) and found that the TRIGGERS entry in the parameter file is not valid for EXP80. Once I turned off this option the export worked fine.

A few suggestions:

1) The log should show the output from the EXP for both failures and successful exports.

2) The export utility to use should be pre-configurable and named, i.e. I work in a environment where we have 8i and 9i databases and it would be nice to quickly pick from a list of pre-configured export utilities for the particular database I'm exporting from rather than have to reset the path.

3) There should be a directory defined for the location of the parameter files, etc. generated using the export utility.

Thanks,

 

[Marco Kalter]

I have added this to the list of enhancement requests. Note that you can already configure the export utilty that is being used on the export screen.

------------------
Marco Kalter
Allround Automations

 

[CTucker]

Few additional requests...

1) Allow a text editor popup for the where clause on the EXPORT. I typically cut from my SQL Editor and the field does not handle multi-line text.

2) On the PL\SQL Developer Export/Import allow storage clause to be ignored, i.e. if moving data from one environment to another the tablespace names are not always the same so ignoring the storage clause would allow the table to be created using the default tables space assigned the User being used for the imported.

Note that request 1) also applies the editing check constraints in the "edit table" dialog. And request 2) also applies the tables when exporting user objects.

Thanks,

 

[Marco Kalter]

I have added this to the list of enhancement requests.

------------------
Marco Kalter
Allround Automations