Re: Errors in importing the production dump to the test database

Another approach is to determine the size of each object and then export the objects from LARGEST to SMALLEST instead of the default (often alphabetically).

One time we needed to export and re-import tables. They all fit in the tablespace but were fragmented and there was absolutely NO new diskspace to create new tablespaces to move them to.

If they all fit originally, they should fit once exported, dropped and then re-imported, right? wrong!! because the tables were imported in the order exported, the smaller tables took up the first extents. Then there was no room left for the larger initial extents. (the tablespace was slip into two datafiles).

We tried specifying the tables to be imported in a different order. Made not difference. What we had to do was to create an explicity parameter file listing all of the tables in order of size DESCENDING. That way, the larger files were imported first.

You might be able to use this information IN COMBINATION with the other responses. This is only if you have the same tablespace size AND want to compress extents but can't because the larger tables are at the end.

Babette Turner-Underwood, TMI Communications babettet_at_tmi.ca.NOSPAM (remove appropriate part to e-mail me)

Peter Chan wrote in message <3676C7E1.B548385C_at_nortelnetworks.ca>...
>Answers:
>1. It could be because your database getting the import does not have
enough disk
>space to recreate the objects, so it cannot create the initial extents.
>
> The tables that begin with EVT and SMP look like Enterprise Manager
tables.
>
>2. To change the storage parameters, first create the objects on the
database
>that is going to receive the import and then import the data into the
receiving
>database. There are a few parameters that you will have to know for the
import,
>so that this procedure will work, I don't know which ones off the top of my
head,
>but read up on the Server Utilities.
>
>I hope this helps or at least gets you started.
>
>bm2208_at_my-dejanews.com wrote:
>
>> HI All
>> Can somebody help me out by clarifying these..
>>
>> 1.When i am importing to Oracle 8.0 on NT i am getting initial extent
problem
>> for some tables,indexes and some tables with prefix EVT, SMP &S%..(not
sure
>> what's the use of these tables and is there any way to avoid these in
case of
>> no use) though the data is not much
>>
>> 2.Is there any way to change the storage parameters while exporting from
>> production database with larger extents to test database with smaller
>> extents..
>>
>> Thanks in advance
>> Madhukar Rao
>> m-rao_at_mailcity.com
>>
>> -----------== Posted via Deja News, The Discussion Network ==----------
>> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>
Received on Tue Dec 15 1998 - 15:30:53 CST