Re: Basic IMP/EXP question
Date: 1996/02/09
Message-ID: <4ffmlv$mtn_at_nw002.infi.net>#1/1
In article <4fdimo$oa1_at_salyko.cube.net>, kfang_at_cube.net says...
>
>dblocher_at_postoffice.ptd.net (David Blocher) wrote:
>
>>Ok I exported a table without any problem with the following command:
>>EXP username/password TABLES=(pc_rslt) log=g:\pcrslt.log
file=g:\pcrslt.dmp
>>I got no errors from this export.
>>Now I dropped the table and now I want to reimport it
>>I guess that the following command should work:
>>IMP username/password TABLES=(pc_rslt) log=g:\pcrslt.log
file=g:\pcrslt.dmp
>>But the commands just hangs. The table is recreated but no data is
>>inserted.
>>I guess I am using the wrong sytax for IMP,
>>any suggestion?
>>David Blocher
>
>If You would just start Import without all the parameters, You'd be
>asked whether You want to import the rows also. I think from the
>commandline the parameter is 'ROWS=Y' (check Your manual ...).
>
>Kersten
>
ROWS=Y is a default parameter according to the Oracle Utilities manual.
I had the same type of problem before and learned that the import process
is assigned to a single rollback segment like most other processes. If a
large table is being imported, it is possible that the rollback segment
consumes all of its extents therefore causing the import to fail. The
long wait time is the rollback process that occurs to remove the imported
data from the table. I believe that the error message appears after the
rolling back completes. I either increase my rollback space or use the
COMMIT=Y import parameter to force a commit after each import array. I
hope this helps.
-- Michael S. Cuppett cuppettm_at_richmond.infi.net Oracle Database Manager Department of Information Technology City of Richmond, VirginiaReceived on Fri Feb 09 1996 - 00:00:00 CET