RE: Inadequate large extend size issue for LMT tablespace / segment space management are manual
- From: "Mark W. Farnham" <mwf@xxxxxxxx>
- To: <raja.s28@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 15 Mar 2013 08:26:30 -0400
Move all your big stuff to uniform extent tablespaces.
Try to do it in sets by isolatable application to minimize which
applications cannot be used in a rolling fashion if you cannot tolerate an
outage to simply get the work done in a batch fashion.
If you have partitioning, look into using the partition exchange method.
(Reading in on Tim Gorman's "scaling to infinity" series is probably the
best way to understand partition exchange, and while there is a lot more
than just partition exchange in his series, it is all very useful stuff to
know. Since you might be OLTP, just understand when Tim advocates NOT having
active constraints he is talking about the particular context of a data
warehouse.)
mwf
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Raja Subramaniyan
Sent: Friday, March 15, 2013 5:52 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Inadequate large extend size issue for LMT tablespace / segment
space management are manual
Hi,
We are migrating the Single Instance Database into RAC ( 10g to 11g ).
Hence as a requirement, our database converted all the tablespaces from
dictionary managed to locally managed tablespaces uing the dbms_space_admin.
However the tablespace segment space management are still in manual. Hence,
we are getting alerts for inadequate chunk of free space which is required.
Eventhougth when I extend the tablespace / adding the datafile, after some
time, I am keep on getting inadequate chuck of freespace alerts. Some one
give me idea for resolving such issues. Thanks in advance !
Regards,
Raja
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
