This problem can occur if there is a difference in the table definition
in the source database and the target database.
Determine whether the import of this object is necessary. If the table
needs to be imported in the target database, you can either create a
copy of the existing table, drop the table, and re-run the import...




Jeffrey C. Ferrel
DMS III
State of Nevada
775.687.9327
[Email address protected]


-----Original Message-----
From: Purusottam Kaushik
[mailto:oracledba-ezmlmshield-x92406530.[Email address protected]
Sent: Tuesday, May 29, 2007 2:59 PM
To: LazyDBA Discussion
Subject: FW: RE: Import/Export error



No in our database we don't have any table with the default value of -1.

Can you please tell me the exact cause of this problem?



Or any pre requisites for performing import and export on the database.



Thanks

Purusottam Kaushik



-----Original Message-----

From: Jeff Ferrel
[mailto:oracledba-ezmlmshield-x31393913.[Email address protected]

Sent: Tuesday, May 29, 2007 4:02 PM

To: LazyDBA Discussion

Subject: RE: Import/Export error





Do you have any tables with a default value of -1?



I've seen where a table is modified after the initial database was

created, and then the import/export failed due to this constraint.



On my database, it was only one table; I was able to remove the

constraint in OEM, apply, and then export (which always worked) and then

get a successful import.



Take a look.



Jeffrey C. Ferrel

DMS III

State of Nevada

775.687.9327

[Email address protected]











---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html



Oracle LazyDBA home page