*From:* John Kanagaraj <mailto:[EMAIL PROTECTED]>
*To:* Multiple recipients of list ORACLE-L
<mailto:[EMAIL PROTECTED]>
*Sent:* Tuesday, October 14, 2003 5:44 AM
*Subject:* RE: RE: Separate Indexes and Data
Jared,
Any indexes supporting a "In-Today; Gon
ture for both range scan and fast full index scans. But these are
generally *exceptions*, not the norm.
Hope this mail makes it ??
Cheers
Richard
- Original Message -
From:
John
Kanagaraj
To: Multiple recipients of list ORACLE-L
Sent: Tuesday, October 14, 2003 5:44
tly from some pretty
> experienced
> > > DBAs stating that there may be 'flaws' in auto-allocate leading
> to
> > > poor extent sizes that leads to fragmentation. I believe Rachel
> > > Carmichael made a post on here a few months back with the
> similiar
leading
> to
> > > poor extent sizes that leads to fragmentation. I believe Rachel
> > > Carmichael made a post on here a few months back with the
> similiar
> > > experience(could be wrong). Due to even the 'small' chance of
> flaws
> > >
small' chance of flaws
> > in auto-allocate, Im thinking of waiting for version 10g before
> > using it. Just to be
safe. Not worth risking a defrag on a > > production system.>
> >> > > From: "MacGregor, Ian A."
<[EMAIL PROTECTED
respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
Subject: RE: RE: Separate Indexes and Data
I assume that what Rachel is referring to is the fact that indexes will
generally not release much space wh
miliar
> > experience(could be wrong). Due to even the 'small' chance of flaws
> > in auto-allocate, Im thinking of waiting for version 10g before
> > using it. Just to be safe. Not worth risking a defrag on a
> > production system.
> > >
>
ould be wrong). Due to even the 'small' chance of flaws
> > in auto-allocate, Im thinking of waiting for version 10g before using
> > it. Just to be safe. Not worth risking a defrag on a production
> > system.
> > >
> > > From: "MacGregor, Ian A.&
e IN for a list of tablespaces?
>
> Or am I missing something?
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
> [EMAIL PROTECTED]
> Sent: 30 September 2003 22:45
> To: Multiple recipients of list ORACLE-L
> Subject
Part of the problem is self-inflicted. We currently use separate tablespaces for each
major project. For instance: chemical inventory gets its own data and index
tablespaces, dosimeter data gets the same, network configuration data as well. For
many projects once the design has matured n
> sizes that leads to fragmentation. I believe Rachel
> Carmichael made a post on here a few months back
> with the similiar experience(could be wrong). Due to
> even the 'small' chance of flaws in auto-allocate,
> Im thinking of waiting for version 10g before using
> i
Couldn't you do this with a simple:
select
owner, table_name
from
all_tables
where
tablespace_name = 'index_tbs';
?
Or of
course use IN for a list of tablespaces?
Or am
I missing something?
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf
You can always schedule a script which drops all
table segments from index tablespaces ;)
Tanel.
- Original Message -
From:
[EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L
Sent: Wednesday, October 01, 2003 12:44
AM
Subject: RE: Separate Indexes and
But those holes of exactly the right size for new objects to fit into.
Since you'll presumably move it once it gets about 1,000 extents or so that
isn't a huge amount of space that's being wasted.
Jay Miller
Sr. Oracle DBA
-Original Message-
Sent: Tuesday, September 30, 2003 4:45 PM
To
30/2003 10:34 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
Subject: RE: Separate Indexes and Data
I'd be very interested to know how many people have their index tablespaces on a dif
be
safe. Not worth risking a defrag on a production system.
>
> From: "MacGregor, Ian A." <[EMAIL PROTECTED]>
> Date: 2003/09/30 Tue PM 01:34:28 EDT
> To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
> Subject: RE: Separate Indexes and Data
&
Hi!
In VLDB environments, it is mostly cheaper to restore and recover the index
tablespace datafile in case of block corruption. In my experience, I've been
lucky and have been able to get rid of corruptions that way, but I'm sure
some people have worse experiences, especially when redologs are co
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 30, 2003 1:29 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: RE: Separate Indexes and Data
>
>
>
> >
> > From: "Jesse, Rich" &
ystem.
> >
> > From: "MacGregor, Ian A." <[EMAIL PROTECTED]>
> > Date: 2003/09/30 Tue PM 01:34:28 EDT
> > To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
> > Subject: RE: Separate Indexes and Data
> >
> > I'd be very
>
> From: "Jesse, Rich" <[EMAIL PROTECTED]>
> Date: 2003/09/30 Tue PM 02:09:32 EDT
> To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
> Subject: RE: RE: Separate Indexes and Data
>
> > -Original Message-
> > From: [EMAIL PR
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 30, 2003 12:50 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: RE: Separate Indexes and Data
>
>
> the defrag paper was written back in 1998 I believe.
DT
> To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
> Subject: RE: Separate Indexes and Data
>
> I'd be very interested to know how many people have their index tablespaces on a
> different backup schedule from their data tablespaces. If so how different?
I'd be very interested to know how many people have their index tablespaces on a
different backup schedule from their data tablespaces. If so how different? What
happens when a media failure occurs and you must restore from backup? You would need
to have on hand and apply more redo logs to
23 matches
Mail list logo
