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

Home -> Community -> Usenet -> c.d.o.misc -> Re: Different initial extents for indexes while import

Re: Different initial extents for indexes while import

From: flange <flange_at_pt.lu>
Date: 1997/12/25
Message-ID: <01bd114c$5e9a5040$9bd79ac2@fql10>#1/1


Hi,

	what is the difference ?
		if less than 10 Oracle blocks this can be normal.
	More than 10 Oracle Blocks.

		Check if you set the parameter compress=Y

--
Regards F. Lange Certified DBA.
29A route du vin.
L5450 Stadtbredimus.
Grand Duchy of Luxembourg.
flqnge_at_pt.lu
(int) 352 697412
(cel) 352 021193652
Phone numbers are variable length.
Luxembourg is a small country of 80 miles on 60 miles between France, Germany and Belgium.

Dorit Noga <doritn_at_bgumail.bgu.ac.il> wrote in article <Pine.OSF.3.96.971225114758.13528B-100000_at_bgumail.bgu.ac.il>...
> I use ORACLE 7.3.3 on SUN/SunOS 5.5.1 . When I am exporting/importing
> from one databse to another and using the parameter INDEXFILE (file that
> contains index creation commands) while importing , i see that the
> initial extents in the storage clause for the indexes are different from
> those in the original database (I do "select * from user_indexes where
> ..." in the original database) . it also doesn't match the default
> parameters taken from tablespace definition.
> WHY????
>
>
Received on Thu Dec 25 1997 - 00:00:00 CST

Original text of this message

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