Re: Change DB_BLOCK size

From: James Lorenzen <james_lorenzen_at_allianzlife.com>
Date: Thu, 27 Jan 2000 15:39:24 GMT
Message-ID: <86porb$b7e$1@nnrp1.deja.com>

In my experience, Oracle will "round" the allocation upwards to the needed block size. The import will performa table create and requested allocations that are less than a blocksize are rounded up to the blocksize.

HTH
James

In article <86nubn$iem$1_at_bgtnsc02.worldnet.att.net>, "Buck Turgidson" <jcmanNOSPAM_at_worldnet.att.net> wrote:
> i reallize we have to re-create the database. I am just wondering
what will
> happen to the tables that are 8192 bytes when we import those into a
> database with a block size of 8192, since Oracle requires that they be
a
> minimum of twice the block size. I was wondering if import dealt with
that
> automatically.
>
> Sybrand Bakker <postmaster_at_sybrandb.demon.nl> wrote in message
> news:948920446.13077.0.pluto.d4ee154e_at_news.demon.nl...
> > The DATABASE will need recreation, you can't change the blocksize
without
> > recreating it.
> > This implies export/import.
> >
> > Hth,
> >
> > --
> > Sybrand Bakker, Oracle DBA
> > Buck Turgidson <jcmanNOSPAM_at_worldnet.att.net> wrote in message
> > news:86ni6e$p48$1_at_bgtnsc03.worldnet.att.net...
> > > The minimum size for a table is 2 * DB_BLOCK_SIZE. We have a lot
of
> > unused
> > > tables in our app that we have created at 8192 that will never
contain
> > rows.
> > > If we increase our DB_BLOCK size from 4096, will these tables need
> manual
> > > re-creation, or will the export/import handle it?
> > >
> > >
> >
> >
>
>

--
Life is complex; it has real and imaginary parts.

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Thu Jan 27 2000 - 09:39:24 CST