Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: exp saves datafile sizes incorrectly

Re: exp saves datafile sizes incorrectly

From: Chuck <chuckh_at_softhome.net>
Date: Mon, 15 Jul 2002 15:59:08 -0400
Message-ID: <agv9ie$oq75r$1@ID-85580.news.dfncis.de>


Exp may save the sizes correctly by doing that, but then you end up with unusable space in your datafiles.

"Connor McDonald" <connor_mcdonald_at_yahoo.com> wrote in message news:3D2B3547.27B4_at_yahoo.com...
> Chuck wrote:
> >
> > Oracle 8.1.7.2 on AIX
> >
> > Anyone else ever see this? Is this a bug? I have a large LMT with 18
> > datafiles of 2000.0625 mb (except one). That is 2000m + 64k. When I do a
> > full database export and grep the create tablespace lines from the
export
> > file, the datafile sizes do not match what's in the database! It's
> > generating datafiles that are exactly 2000m and do not have the extra
64k.
> > Am I doing something wrong? Am I missing something on how exp works?
Figured
> > I'd ask here before reporting it on metalink as a bug.
> >
> > SQL> r
> > 1 SELECT file_name, bytes/1048576
> > 2 FROM dba_data_files
> > 3* WHERE tablespace_name = 'ACTION_D'
> >
> > FILE_NAME BYTES/1048576
> > ---------------------------------------- -------------
> > /u201/oradata/MCPROD/action_d01.dbf 2000.0625
> > /u201/oradata/MCPROD/action_d02.dbf 2000.0625
> > /u201/oradata/MCPROD/action_d03.dbf 2000.0625
> > /u201/oradata/MCPROD/action_d04.dbf 2000.0625
> > /u201/oradata/MCPROD/action_d05.dbf 2000.0625
> > /u206/oradata/MCPROD/action_d06.dbf 2000.0625
> > /u206/oradata/MCPROD/action_d07.dbf 2000.0625
> > /u206/oradata/MCPROD/action_d08.dbf 2000.0625
> > /u206/oradata/MCPROD/action_d09.dbf 2000.0625
> > /u206/oradata/MCPROD/action_d10.dbf 1500.0625
> > /u201/oradata/MCPROD/action_d11.dbf 950.0625
> > /u208/oradata/MCPROD/action_d12.dbf 2000.0625
> > /u208/oradata/MCPROD/action_d13.dbf 2000.0625
> > /u208/oradata/MCPROD/action_d14.dbf 2000.0625
> > /u208/oradata/MCPROD/action_d15.dbf 2000.0625
> > /u208/oradata/MCPROD/action_d16.dbf 2000.0625
> > /u208/oradata/MCPROD/action_d17.dbf 2000.0625
> > /u208/oradata/MCPROD/action_d18.dbf 2000.0625
> > /u210/oradata/MCPROD/action_d19.dbf 2000.0625
> >
> > 19 rows selected.
> >
> > grep -i "CREATE TABLESPACE ACTION_D" myexp.dat
> >
> > CREATE TABLESPACE "ACTION_D" DATAFILE
'/u201/oradata/MCPROD/action_d01.dbf'
> > SIZE 2000M REUSE, '/u201/oradata/MCPROD/action_d02.dbf' SIZE 2000M
REUSE,
> > '/u201/oradata/MCPROD/action_d03.dbf' SIZE 2000M REUSE,
> > '/u201/oradata/MCPROD/action_d04.dbf' SIZE 2000M REUSE,
> > '/u201/oradata/MCPROD/action_d05.dbf' SIZE 2000M REUSE,
> > '/u206/oradata/MCPROD/action_d06.dbf' SIZE 2000M REUSE,
> > '/u206/oradata/MCPROD/action_d07.dbf' SIZE 2000M REUSE,
> > '/u206/oradata/MCPROD/action_d08.dbf' SIZE 2000M REUSE,
> > '/u206/oradata/MCPROD/action_d09.dbf' SIZE 2000M REUSE,
> > '/u206/oradata/MCPROD/action_d10.dbf' SIZE 1500M REUSE,
> > '/u201/oradata/MCPROD/action_d11.dbf' SIZE 996212736 REUSE,
> > '/u208/oradata/MCPROD/action_d12.dbf' SIZE 2000M REUSE,
> > '/u208/oradata/MCPROD/action_d13.dbf' SIZE 2000M REUSE,
> > '/u208/oradata/MCPROD/action_d14.dbf' SIZE 2000M REUSE,
> > '/u208/oradata/MCPROD/action_d15.dbf' SIZE 2000M REUSE,
> > '/u208/oradata/MCPROD/action_d16.dbf' SIZE 2000M REUSE,
> > '/u208/oradata/MCPROD/action_d17.dbf' SIZE 2000M REUSE,
> > '/u208/oradata/MCPROD/action_d18.dbf' SIZE 2000M REUSE,
> > '/u210/oradata/MCPROD/action_d19.dbf' SIZE 2000M REUSE
> > EXTENT MANAGEMENT LOCAL UNIFORM SIZE 262144000

>

> Hardly a 'workaround' but I did a test on 8173 with a 'datafile 2001m'
> clause and it popped out as expected in the dump file. Maybe resize
> your files up to 2001 ?
>

> hth
> connor
> --
> ==============================
> Connor McDonald
>

> http://www.oracledba.co.uk

>
> "Some days you're the pigeon, some days you're the statue..."
Received on Mon Jul 15 2002 - 14:59:08 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US