Hi,

I have an export from oracle 8.1.7 and attempting to import a table into
oracle 9.2.0.4. My table has 100,000 rows but only 30,000 rows are imported.
No errors are given. The table does have one clob column.

I'm using standard export (not direct).

Does anyone have any hints on how I can resolved this problem.

Thanks.

Cookie Monster wrote:

> Hi,
>
> I have an export from oracle 8.1.7 and attempting to import a table into
> oracle 9.2.0.4. My table has 100,000 rows but only 30,000 rows are imported.
> No errors are given. The table does have one clob column.
>
> I'm using standard export (not direct).
>
> Does anyone have any hints on how I can resolved this problem.
>
> Thanks.

Are you importing into an existing table that already has constraints
and/or triggers or is the import creating a new table?

--
Daniel Morgan
http://www.outreach.washington.edu/e...ad/oad_crs.asp
http://www.outreach.washington.edu/e...oa/aoa_crs.asp
damorgan@x.washington.edu
(replace 'x' with a 'u' to reply)

"Daniel Morgan" <damorgan@x.washington.edu> wrote in message
news:1071675382.82384@yasure...
> Cookie Monster wrote:
>
> > Hi,
> >
> > I have an export from oracle 8.1.7 and attempting to import a table into
> > oracle 9.2.0.4. My table has 100,000 rows but only 30,000 rows are
imported.
> > No errors are given. The table does have one clob column.
> >
> > I'm using standard export (not direct).
> >
> > Does anyone have any hints on how I can resolved this problem.
> >
> > Thanks.
>
> Are you importing into an existing table that already has constraints
> and/or triggers or is the import creating a new table?

No, I am importing into a completely new database. It's clean, nothing in
there.

Steve.

"Cookie Monster" <cookie.monster@somewhere.com> wrote
>
> I have an export from oracle 8.1.7 and attempting to import a table into
> oracle 9.2.0.4. My table has 100,000 rows but only 30,000 rows are imported.
> No errors are given. The table does have one clob column.

To add to Daniel's reply..

How sure are you that 100,000 rows were indeed exported? Maybe the
30,000 rows mean that just 30,000 rows exist in the export dump file?

What are the export and import parameters?


--
Billy

Billy Verreynne wrote:

> "Cookie Monster" <cookie.monster@somewhere.com> wrote
>
>>I have an export from oracle 8.1.7 and attempting to import a table into
>>oracle 9.2.0.4. My table has 100,000 rows but only 30,000 rows are imported.
>>No errors are given. The table does have one clob column.
>
>
> To add to Daniel's reply..
>
> How sure are you that 100,000 rows were indeed exported? Maybe the
> 30,000 rows mean that just 30,000 rows exist in the export dump file?
>
> What are the export and import parameters?
>
>
> --
> Billy

Good point. Cookie ... perform your export and import using the LOG
parameter and read the created log to verify that what you think is
happening is, in fact, happening.

--
Daniel Morgan
http://www.outreach.washington.edu/e...ad/oad_crs.asp
http://www.outreach.washington.edu/e...oa/aoa_crs.asp
damorgan@x.washington.edu
(replace 'x' with a 'u' to reply)

"Billy Verreynne" <vslabs@onwe.co.za> wrote in message
news:1a75df45.0312171137.2b639990@posting.google.c om...
> "Cookie Monster" <cookie.monster@somewhere.com> wrote
> >
> > I have an export from oracle 8.1.7 and attempting to import a table into
> > oracle 9.2.0.4. My table has 100,000 rows but only 30,000 rows are
imported.
> > No errors are given. The table does have one clob column.
>
> To add to Daniel's reply..
>
> How sure are you that 100,000 rows were indeed exported? Maybe the
> 30,000 rows mean that just 30,000 rows exist in the export dump file?

When I run the export it tells me that 200,000 rows were exported. The file
is pretty big so I believe it.

>
> What are the export and import parameters?
>

exp name/pass fille=x.dmp compress=n statistics=none tables=meTable


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

Gives no idications of corruptions.

Cookie.
>
> --
> Billy

"Cookie Monster" <cookie.monster@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