![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, We are exporting from 10g and importing to 11g. We encountered this error: IMP-00003: ORACLE error 439 encountered ORA-00439: feature not enabled: Basic Compression So ok, maybe compression is no longer free? But, how can I uncompress the tables and export them? I mean, if say for example, my database has 5000 compressed tables and each contain 1 million or more rows........does Oracle provide a way to export & uncompress? |
#3
| |||
| |||
|
|
On Tue, 20 Sep 2011 08:23:54 -0700, ExecMan wrote: Hi, We are exporting from 10g and importing to 11g. *We encountered this error: IMP-00003: ORACLE error 439 encountered ORA-00439: feature not enabled: Basic Compression So ok, maybe compression is no longer free? *But, how can I uncompress the tables and export them? *I mean, if say for example, my database has 5000 compressed tables and each contain 1 million or more rows........does Oracle provide a way to export & uncompress? Is the Oracle 11g database in question enterprise edition or some other type of install? Compression is only available in the enterprise edition. You can do export/import over the DB link and in that case you don't need compression. --http://mgogala.byethost5.com |
#4
| |||
| |||
|
|
Sorry, it is SE (or maybe SE1). But if we cannot use compression, is there a way to uncompress during the export? Or, will we need to create new tables, uncompressed, then export. A real pain! |
#5
| |||
| |||
|
|
On Tue, 20 Sep 2011 09:03:20 -0700, ExecMan wrote: Sorry, it is SE (or maybe SE1). *But if we cannot use compression, is there a way to uncompress during the export? *Or, will we need to create new tables, uncompressed, then export. * A real pain! The problem is in creating tables with the compressed attribute. Try this in your destination database: SQL> create table t1(c1 varchar2(20),c2 number(10,0)) compress; Table created. If that succeeds, and I don't think it will, the problem is soluble by using the DB link for export/import. If not, you will have to create all compressed tables without the "COMPRESS" option before the import and import with TABLE_EXISTS_ACTION=APPEND --http://mgogala.byethost5.com |
#6
| |||
| |||
|
|
On Sep 20, 12:11Â*pm, Mladen Gogala <gogala.mla... (AT) gmail (DOT) com> wrote: On Tue, 20 Sep 2011 09:03:20 -0700, ExecMan wrote: Sorry, it is SE (or maybe SE1). Â*But if we cannot use compression, is there a way to uncompress during the export? Â*Or, will we need to create new tables, uncompressed, then export. Â* A real pain! The problem is in creating tables with the compressed attribute. Try this in your destination database: SQL> create table t1(c1 varchar2(20),c2 number(10,0)) compress; Table created. If that succeeds, and I don't think it will, the problem is soluble by using the DB link for export/import. If not, you will have to create all compressed tables without the "COMPRESS" option before the import and import with TABLE_EXISTS_ACTION=APPEND --http://mgogala.byethost5.com You could potentially use dbms_metadata to generate all the create table statements and just edit the result to remove the compress statement then create the tables manually in the target database followed by trying an impor into the existing table. HTH -- Mark D Powell -- |
![]() |
| Thread Tools | |
| Display Modes | |
| |