Error IMPDP ORA-02219, Data pump from Linux to Windows Options

[Drakken]

I'm trying desperately for a few days to import an Oracle database 10.2.0.5 from a Red Hat Enterprise Linux Server release 4.1 on my Windows server 2008 R2 x64 11.2.0.1.

The expdp export is performed without errors with the following options:

DUMPFILE = expinclude.dmp
DIRECTORY = exp_dir
LOGFILE = expinclude.log
TABLES = (list of tables with partitions)
ESTIMATE = STATISTICS

When I try to import my dump I do not get a multitude of errors like this:

ORA-39083: Failed to create the object type TABLE: "VL_DATA". "LOG_VOUCHERS_MESSAGES" with option value error:
ORA-02219: invalid NEXT storage option value
SQL failing:

After having scoured the forums on the net I have found very little info on this error (besides the code itself emerges out of a thousand sites).

I tried multiple combinations for Import: excluding the index, only the structure of import, import data, etc. ... without success.

If someone have a track I would be greatly relieved.

Thank you in advance.

[merrillcd_mem]

It may not be the best method, but personally I like to pre-create the tables by extracting ddl from source, impdp contents=data_only , then build the indexes/constraints, etc..

I'm trying desperately for a few days to import an Oracle database 10.2.0.5 from a Red Hat Enterprise Linux Server release 4.1 on my Windows server 2008 R2 x64 11.2.0.1.

The expdp export is performed without errors with the following options:

DUMPFILE = expinclude.dmp
DIRECTORY = exp_dir
LOGFILE = expinclude.log
TABLES = (list of tables with partitions)
ESTIMATE = STATISTICS

When I try to import my dump I do not get a multitude of errors like this:

ORA-39083: Failed to create the object type TABLE: "VL_DATA". "LOG_VOUCHERS_MESSAGES" with option value error:
ORA-02219: invalid NEXT storage option value
SQL failing:

After having scoured the forums on the net I have found very little info on this error (besides the code itself emerges out of a thousand sites).

I tried multiple combinations for Import: excluding the index, only the structure of import, import data, etc. ... without success.

If someone have a track I would be greatly relieved.

Thank you in advance.

[HelloRavi]

IF possible try with 2 imports; First to import only structures and 2nd with data.

Also check the respective tablespace got enough space to accomodate the NEXT storage value.

[burleson]

Hi,

You have likely hit this bug:

http://www.remote-dba.cc/oracle_tips_bug_warning.htm

And there may be other bug that cause ibnvalid NEXT values, check bugs database.

http://support.oracle.com

You can easily work around this issue by importing the DDL forst, \and then the data.

Full directions are here:

http://www.rampant-books.com/book_0801_oracle_utilities.htm

*******************************************
>> ORA-02219

You need to export only the DDL, and check to see what the NEXT value is, that import is complaining about! (export rows=n)

http://www.dba-oracle.com/t_export_stored_...es_triggers.htm

You can also export the DDL with dbms_matadata:

http://dba-oracle.com/googlesearchsite_pro...q=dbms_metadata

Then, fix the NEXT and import only the DDL

Finally, import with ignore=y