Welcome Guest ( Log In | Register )


 
 
 
 
 
 

 
 
Oracle 

Performance Tuning Reference poster
 
Oracle training in Linux 

commands
 
Oracle training Weblogic Book
 
Easy Oracle Jumpstart
 
Oracle training & performance tuning books
 
Burleson Consulting Remote DB Administration
 
 
 
Reply to this topicStart new topic
> Error IMPDP ORA-02219, Data pump from Linux to Windows
Drakken
post Feb 13 2012, 04:22 AM
Post #1


Newbie
*

Group: Members
Posts: 1
Joined: 13-February 12
Member No.: 46,754



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.
Go to the top of the page
 
+Quote Post
merrillcd_mem
post Feb 13 2012, 08:50 AM
Post #2


Member
**

Group: Members
Posts: 29
Joined: 30-June 11
From: Memphis TN
Member No.: 45,469



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..



QUOTE (Drakken @ Feb 13 2012, 04:22 AM) *
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.

Go to the top of the page
 
+Quote Post
HelloRavi
post Feb 14 2012, 07:13 AM
Post #3


Advanced Member
***

Group: Members
Posts: 111
Joined: 25-March 08
Member No.: 19,800



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.
Go to the top of the page
 
+Quote Post
burleson
post Feb 14 2012, 07:59 AM
Post #4


Advanced Member
***

Group: Members
Posts: 11,493
Joined: 26-January 04
Member No.: 13



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




--------------------
Hope this helps. . .

Donald K. Burleson
Oracle Press author
Author of Oracle Tuning: The Definitive Reference
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Lo-Fi Version Time is now: 19th September 2014 - 12:49 PM