Re: import fails to import all rows.

"Cookie Monster" <cookie.monster_at_somewhere.com> wrote

> Thinking that this might be due to a problem with the source I made a copy
> of the original table with create table ..as select... I then exported this
> copy. The export and import worked correctly with the copied table. So
> clearly there is a problem with the source, although I cannot tell what.
> ANALYZE TABLE meTable VALIDATE STRUCTURE

Why do you say that? If the export says 200,000 rows exported and a select count(*) on the source table say 200,000 then there is not a problem with the rows exported.

If the import fails to import all 200,000 and imports a subset, that points to either an import issue or a destination table issue.

I think that the reason the copy of the source table exported and imported fine is that you changed the object name. This points IMO to a problem with the original destination table (as the new import works fine with the new table name).

With the original import, does the destination table already exist? If so. Do you use the ignore parameter? Are you sure the table is empty? Have you disabled all constraints?

If the table does not exist, what is the tablespace name for the table? Does the same tablespace exist on the destination database? Does the schema you're importing into have a space quota on that tablespace? If not, what is the default tablespace of that destination schema?

Been using exports and imports for some years now and have never run into this type of problem that you describe. I strongly doubt that this is a problem with the Oracle import/export software. IMO it is either a parameter problem or an issue with the destination.

--
Billy