RE: Next Extent Failure Notification for Locally Managed Tablespaces

From: Kline.Michael <Michael.Kline_at_SunTrust.com>
Date: Wed, 23 Jun 2004 09:04:58 -0400
Message-ID: <52C70FF150F49E479DAF59C68A27149D06708C@va016a0e2.corp.suntrust.com>

I've done those sorts of things on the fly. This is a sort of "batch system" though, so when they are in the "pre load" many tablespaces go empty.

I also took some archives from TS_CST_M1(-M3) to TS3_CST_M1(-M12) and during the "move partitions" I picked up uniform extents and autoextend. (The TS3 means they will be saving 3 years.)

Between production and test we're about 17TB.

I just fixed a disaster with a tablespace(4 of them) that was LOGGING and 64K extents which may have been okay, but the combined load was roughly 80GB. So they are now NOLOGGING and 100M extents.

Curious thing was it took a long time to truncate the old tables, and they were LOCAL, but there was a whole lot of the fet$ stuff, at least I think that was it going on during the clean up. But given the old 64K and the 30-50GB table sizes, there would have been a boat load of extents.

I inherited these systems and am working to get them tuned up, but not have to take the databases down to do it. It will be many months.

Michael Kline
Database Administration
Outside 804.261.9446

> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org

[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of DENNIS
> WILLIAMS
> Sent: Tuesday, June 22, 2004 4:29 PM
> To: 'oracle-l_at_freelists.org'
> Subject: RE: Next Extent Failure Notification for Locally Managed
Tablespaces
>
> Steve
> Don't sell it to them based on making your life easier. Sell it to
them
> based on reducing failures. Because you can predict what will happen
better.
> Then you look more proactive. Woops . . . did I say that?
>
> Dennis Williams
> DBA
> Lifetouch, Inc.
> dwilliams_at_lifetouch.com
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Wales, Stephen
(RTSI)
> Sent: Tuesday, June 22, 2004 3:27 PM
> To: oracle-l_at_freelists.org
> Subject: RE: Next Extent Failure Notification for Locally Managed
> Tablespaces
>
>
> We were thinking about that. Might have to try to test it out on the
=
> development database and get some timing. Because if downtime is
going =
> to be excessive then I'll have a hard time selling it to management
just =
> to that I can make my life a little easier from a monitoring =
> perspective.=20
>
> Thanks to all who threw input at this topic.
>
> Steve
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Niall Litchfield
> Sent: Tuesday, June 22, 2004 2:03 PM
> To: oracle-l_at_freelists.org
> Subject: Re: Next Extent Failure Notification for Locally Managed
> Tablespaces
>
>
> Guang's idea would work perfectly well without recreating the
> database. I don't think that you can avoid downtime though.

The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer.

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Wed Jun 23 2004 - 08:03:23 CDT