Reclaim space after ALTER TABLE DROP PARTITION

Similar Questions

• I'm unable to reclaim space after deleting data files.

  Dear all.
  
  I'm unable to reclaim space after deleting data files.
  
  Scenario:
  
  One of my mount point has reached full growth of undotablespace (undotbs2), so I spent again (undotbs3) and deleted the old.
  Problem 1.
  Failed to retrieve space after removing the undotbs2.
  Problem 2.
  Dial-up Mount also become fully...:)
  
  The steps that I followed for the switching of the cancellation:
  
  BANNER
  ----------------------------------------------------------------
  Oracle Database 10 g Enterprise Edition release 10.2.0.3.0 - 64bi
  PL/SQL version 10.2.0.3.0 - Production
  CORE Production 10.2.0.3.0
  AMT for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - production
  NLSRTL Version 10.2.0.3.0 - Production
  
  
  SQL > show Cancel parameter
  VALUE OF TYPE NAME
  ------------------------------------ ----------- ------------------------------
  UNDO_MANAGEMENT string AUTO
  UNDO_RETENTION integer 32400
  undo_tablespace string UNDOTBS2
  
  
  SQL > select BYTES/1024/1024, FILE_NAME in dba_data_files where nom_tablespace = 'UNDOTBS2 ';
  BYTES/1024/1024
  ---------------
  FILE_NAME
  ------------------------------------------------------------------------------------------------------------------------------------------------------
  45688.125
  /U04/oradata/RADPRDMH/undotbs02b.dbf
  6268
  /U04/oradata/RADPRDMH/undotbs02a.dbf
  
  
  
  CREATE UNDO TABLESPACE undotbs3
  DATAFILE ' / u05/oradata/RADPRDMH/undotbs03a.dbf'
  SIZE 5000M AUTOEXTEND ON;
  
  
  ALTER SYSTEM SET UNDO_TABLESPACE = undotbs3 SCOPE = BOTH;
  
  
  DROP TABLESPACE UNDOTBS2 INCLUDING CONTENT AND DATA FILES;

  Only solution is umount the point of editing or the db bounce. It is because of 'SEMAPHORE '.

  Semaphores are sharable resources who take a non-negative integer value. They are manipulted by the P (waiting) and V (signal) functions that decrement and increment the semaphore, respectively. When a process needs a resource, a "waiting" is issued and the semaphore is decremented. When the semaphore contains a value of zero, the resources are not available and the calling process turns or blocks (if applicable) until resources are available. When a process opens a resource controlled by a semaphore, it increments the semaphore and the waiting process are advised.

• ALTER table move partition in parallel

  Hello
  
  I wish that this command must be run in parallel. is this possible?
  
  ALTER TABLE xyz PARTITION MOVE xyz_p0608 TABLESPACE q208_ts
  
  Thank you

  parallel_clause
  
  Purpose
  
  The parallel_clause lets you parallelize the creation of a database object and set the default degree of parallelism for subsequent queries of and DML operations on the object.
  
  You can specify the parallel_clause in the following statements:
  
      * CREATE TABLE: to set parallelism for the table (see CREATE TABLE).
      * ALTER TABLE (see ALTER TABLE):
            o To change parallelism for the table
            o To parallelize the operations of adding, coalescing, exchanging, merging, splitting, truncating, dropping, or moving a table partition
  

  To parallelize append operations, coalescence, Exchange, merger, splitting, truncate, delete or move a partition table
  

• NOLOGGING in alter table split partition...

  Hi all
  
  Please can tell me where I would add the NOLOGGING in the below statement, or any other means by which I can stop to redo being generated
  
  ALTER table split partition EB_LOGS_082008 at (to_date('01-01-2010','DD-MM-YYYY')) NOLOGGING EB_LOGS into (partition EBLAST_TABLE, partition EB_LOGS_012010 tablespace EBLAST_TABLE tablespace EB_LOGS_082008) parallel;

  Wow... Grammar ALTER TABLE just constantly more and more complex, isn't?

  According to this:
  http://download.Oracle.com/docs/CD/E11882_01/server.112/e10592/clauses005.htm#CJAHABGF

  "For partitioned objects, the value specified for this clause is the physical attribute by default segments (and ALTER following... associated with all the partitions specified in the CREATE statement ADD PARTITION statements), unless you specify the logging attribute in the description of the PARTITION. »

  If I read that correctly, so if you want the NOLOGGING keyword to indicate more than just the physical default attribute, then it must be in the description of the PARTITION.

  So something like this, perhaps?
  Totally not tested, BTW:
  ALTER table EB_LOGS split partition EB_LOGS_082008 at (to_date('01-01-2010','DD-MM-YYYY')) into (partition EB_LOGS_082008 tablespace EBLAST_TABLE nologging, partition EB_LOGS_012010 tablespace EBLAST_TABLE nologging) parallel;

  Once again, this is an assumption and cannot yet pass the analysis.

  In regards to the perceived dangers of NOLOGGING operations, well, it is certainly something that must be clearly understood, but not to fear. The disadvantage of an operation NOLOGGING is that if you need to recover from a backup taken before the NOLOGGING operation, until a point in time after the operation NOLOGGING objects in the database that were submitted to NOLOGGING operations will logically corrupted and must be rebuilt.

  Finally, I fell on this can also be useful, regarding the optimization of SPLIT PARTITION operations:
  http://download.Oracle.com/docs/CD/E11882_01/server.112/e10837/part_admin.htm#VLDBG00304

  Hope that helps,

  -Mark

• alter table drop column

  Hi all

  I create a simple table like this:

  create table x (a number, b varchar2 (20));

  ALTER table x modify a primary key constraint a_pk;

  insert into x values (1, 'first row');

  insert into x values (2, 'second row');

  commit;

  Then:

  SQL > select * from x;

  A AND B

  ---------- --------------------

  1 first row

  2 second row

  Then I run these commands:

  SQL > alter table drop column x.

  Modified table.

  SQL > select * from x;

  B

  --------------------

  first row

  second row

  Question: Why am I able to remove this column when a PRIMARY KEY for the table? I do not use the key words of CONSTRAINT CASCADE with the DROP COLUMN clause...

  I have Mr. Steve O'Hearn here saying this in his book 'Certified Expert Guide exam 1Z0-047:

  CREATE TABLE ORDER_RETURNS

  (NUMBER OF ORDER_RETURN_ID,

  NUMBER OF CRUISE_ORDER_ID

  DATE OF CRUISE_ORDER_DATE,

  CONSTRAINT PK_OR PRIMARY KEY (ORDER_RETURN_ID));

  .. We can not remove the column the table ORDER_RETURNS that

  is subject to the constraint PRIMARY KEY (ORDER_RETURN_ID)... The reasons are:

  ORDER_RETURN_ID is the PRIMARY KEY of this table...

  Isn't this correct?

  No - it's NOT correct - the book is bad.

  You could have just tested the FULL example in the book to verify that the statement is wrong.

  http://weirdoootamee.yolasite.com/resources/Oracle%20sql%20expert.PDF

  See page 432

  CREATE TABLE CRUISE_ORDERS
  (NUMBER OF CRUISE_ORDER_ID,
  ORDER_DATE DATE,
  PK_CO (CRUISE_ORDER_ID, ORDER_DATE) PRIMARY KEY CONSTRAINT);

  CREATE TABLE ORDER_RETURNS
  (NUMBER OF ORDER_RETURN_ID,
  NUMBER OF CRUISE_ORDER_ID
  DATE OF CRUISE_ORDER_DATE,
  CONSTRAINT PK_OR PRIMARY KEY (ORDER_RETURN_ID).
  FOREIGN KEY CONSTRAINT FK_OR_CO
  (CRUISE_ORDER_ID, CRUISE_ORDER_DATE)
  REFERENCES CRUISE_ORDERS (CRUISE_ORDER_ID, ORDER_DATE));

  create two tables - add data, if you want.

  Then try to delete the primary key column and see what happends

  ALTER table drop column order_return_id order_returns;

  The best way to learn is to actuall TRY of THINGS.

  Try it with your own table, but the FIRST thing that you should try was the real example of the book.

• Estimating redo size of alter table DROP COLUMNS CONTINUE checkpoint of 10000

  Hello
  in my 10.2.0.3, I've got table size 90 GB suffering:
  ORA-12986: columns in partially suspended state. Propose to ALTER TABLE DROP COLUMNS CONTINUE
  I need to know how to estimate the size of redo of the:
  change the control of MORE of COLUMNS DROP table 10000 point.
  Is 2 x good estimate of table size?
  Kind regards.
  Greg

  GregG says:
  Please clarify for me how are distinguished between nitrifiants delay block trial and lower real column continue the process.
  Looks like DBC process will increment statistics such as:

  drain plug - number of calls ktugct
  gullies only - consistent read gets

  It's a good indicator, even if I think the specific statistics could be:

      commit txn count during cleanout
  

  I think it's one that tells you that you have made a change of "validation of transaction" to a block.

  I don't know why the CBD process is such redo intensive, is not on the update of ITL bit in db blocks only?

  It updates the inputs ITL and lock bytes, and it takes only entry of redo block; the overload of the roll forward database is in the tens of bytes is small compared to the 240 bytes per row of the column to fall - but if you have a large number of blocks to go before continue it really starts to have an effect, you might be fooled.

  WARNING - I haven't checked to see if delay block drain plug behaves (or even happens) on Delete column in the way that it would perform a simple update in bulk.

  Concerning
  Jonathan Lewis

• ALTER table drop column is too slow on the big table

  Hi all
  the user has run after a command in oracle 10 G: - >
  ALTER table < table name > Delete column (< cloumn list >); table in question is of a size 41GB.
  
  the results of the command to cancel space filled.
  Tips of even trace file cancel segemnts.
  
  query failed for hours.
  Why cancel is linked to this
  and what would the resolution for this.
  
  Unused help set...
  
  
  Thanks in advance,
  Rock

  Would it be useful to assign unused columns?
  What about dbms_redefinition?

• Invalid procedure after alter table add &lt; column &gt;

  Hello Experts,

  I was faced with a situation where I add a column in a table that is used in a procedure, immediately after the addition of the new procedure associated with this table column becomes invalid.

  Can someone explain please know why this happens.

  Database version:-11.2.0.4.

  I was faced with a situation where I add a column in a table that is used in a procedure, immediately after the addition of the new procedure associated with this table column becomes invalid.

  Can someone explain please know why this happens.

  Yes - the Oracle documentation explains this. I found this doc with a simple search of "column, add the oracle 11g invalid procedure.

  http://docs.Oracle.com/CD/B28359_01/server.111/b28318/dependencies.htm#CHDJIIFC

  Table 6-2 , shows how objects are affected by changes to other objects upon which they depend.

  Table 6-2 operations affects this object status

  Operation	Where the status of dependent objects
  ALTERTABLEtableADDcolumn	INVALIDWhen: Uses of the object (except a view)-dependent SELECT * on table . Dependent object uses table %rowtype . Dependent object performs INSERT on table without specifying a list of columns. Dependent object references table in the query that contains a join in SQL. Dependent object references table in the query that refers to a PL/SQL variable. Otherwise, no change.

  Read the WHOLE ARTICLE and see if it does not have to explain your problem.

• ALTER table add partition error

  Hello world
  
  In fact, I add more partitions in an existing table. My sql is
  
  ALTER table dmp_tlog1_bk add the partition by range (tmonth)
  (
  P9_200908 lower VALUES (200909) PARTITION.
  P10_200909 lower VALUES (200910) PARTITION.
  PARTITION P11_200910 lower VALUES (200911));
  commit;
  
  but I get the following error
  Error from the 1 in the command line:
  ALTER table dmp_tlog1_bk add the partition by range (tmonth)
  
  P9_200908 lower VALUES (200909) PARTITION.
  P10_200909 lower VALUES (200910) PARTITION.
  PARTITION P11_200910 lower VALUES (200911)
  Error report:
  SQL error: ORA-00902: invalid data type
  00902 00000 - "invalid data type".
  * Cause:
  * Action:
  validation succeeded.
  
  
  The data type of the tmonth is number (8.0) is the structure of the table.
  
  
  could you please help?
  
  
  Thank you very much

  alter table dmp_tlog1_bk add partition P9_200908 VALUES less than (200909)
  /
  

  SY.

• alter table Exchange partition

  Dear Experts,

  I could ask does change exchange table partition depends on the size of the table or partition?

  Thank you for your help.

  Best regards, Atanas.

  Hello Atanas,

  It's the good point: it does not depend on the size. Data is actually exchanged between the two segments, the work is only level 'dictionary': Oracle exchange the roles of both existing segments, it is now regarded as a table and the other as a partition, as opposed to their roles before the "swap partition.

  Thanks to this, Exchange a partition can be a very quick way of loading new data or old data archiving...

  Best regards

  Bruno Vroman.

• Select display after alter table

  Hello
  Why ' select * view "is not display recent columns added by alter table command." Even display columns and the data from the table only. What is the oracle of mechanism used here?
  
  Thank you
  
  Vermorel

  When you create a view, you create a static 'snapshot' of the columns of the table. Adding columns in the underlying table will not change the definition of the view. Using a "select *...» "according to the definition simply indicates the database to create the view with all the columns that appear in the table at this moment in time. He does not mean "dynamically change the display when the table is changed," which would negate the whole point of views.

  E.g.:

  SQL> create table t1 (col1 number,
    2                   col2 number);
  
  Table created.
  
  SQL> create view v1 as select * from t1;
  
  View created.
  
  SQL> desc t1
   Name
   --------------------------------------------------------
   COL1
   COL2                                                           
  
  SQL> desc v1
   Name
   --------------------------------------------------------
   COL1
   COL2                                                           
  
  SQL> alter table t1 add (col3 number);
  
  Table altered.
  
  SQL> desc t1
   Name
   --------------------------------------------------------
   COL1
   COL2
   COL3                                                           
  
  SQL> desc v1
   Name
   --------------------------------------------------------
   COL1
   COL2                                                           
  
  SQL> create or replace view v1 as select * from t1;
  
  View created.
  
  SQL> desc v1
   Name
   --------------------------------------------------------
   COL1
   COL2
   COL3                                                           
  

• How do I reclaim space after the removal of 10 million documents.

  Oracle 10g version.
  Hey it's the interview question that I met yesterday.
  
  
  After the deletion of 10 million records how you can reclaim the space used by 10 million records. ?
  
  
  Thank you

  Great discussion, just taken one of the many interesting answers:

  http://asktom.Oracle.com/pls/Apex/f?p=100:11:0:P11_QUESTION_ID:1336002638218 #1339720300346849060

  (in particular, the reference to the partitioning)

  And "read on" means:
  Quick search the docs @ http://www.oracle.com/pls/db102/homepage

• ALTER drop partition table for ORA-01031: insufficient privileges

  Hello
  
  Select * from version of v$.
  BANNER
  --------------------------------------------------------------------------------
  Oracle Database 11 g Enterprise Edition Release 11.2.0.2.0 - 64 bit Production
  PL/SQL Release 11.2.0.2.0 - Production
  CORE Production 11.2.0.2.0
  AMT for Linux: Version 11.2.0.2.0 - Production
  NLSRTL Version 11.2.0.2.0 - Production
  
  
  I have a table in the schema Y whose partition based on the value should be removed from schema X.
  
  For example, ALTER TABLE DROP PARTITION Y.TAB_NAME FOR (4853);
  
  I guess I gave almost all the privileges. Any thoughts?
  
  Select * from DBA_TAB_PRIVS where table_name = 'Table_name' and recipient = 'X '.
  
  DEALERSHIP OWNER TABLE_NAME GRANTOR PRIVILEGE HIERARCHY
  ------------------------------ ------------------------------ ------------------------------ ------------------------------ ---------------------------------------- --------- --------------------- --------- ---------------------
  X Y TABLE_NAME Y ALTER YES NO
  X Y TABLE_NAME DELETE YES NO
  X Y TABLE_NAME Y INSERT YES NO
  X Y TABLE_NAME SELECT YES NO
  UPDATE TABLE_NAME Y Y X YES NO
  INDEX OF TABLE_NAME Y Y X YES NO
  
  6 selected lines

  Additional Prerequisites for Partitioning Operations
  If you are not the owner of the table, then you need the DROP ANY TABLE privilege in order to use the drop_table_partition or truncate_table_partition clause.
  

  reference - http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/statements_3001.htm

  * That said I think seriously to give such a privilege [DROP ANY TABLE] to another schema.*

  I hope this helps!

  Published by: Sri on April 6, 2011 14:12

• phenomenon of the drop partition parent with delete on child cacasde

  Hi have a parent and child. Both are partitioned by month.
  I have cascase ondelete for children tables...
  Now, when I tried to drop the parent partition... I got an error called key referenced in the child table.
  
  Why is - this cacading removal does not work? Perhaps because it was an operation move and do not delete.
  
  
  so first of all, I decided to drop the child partition (which was 1 row and it refers to 1 row in table parent partition)
  
  ALTER table drop partition activity_sep_2009 ACTIVITYLOGDATA
  
  then I tried to delete the parent partition
  
  ALTER table ACTIVITYLOGdrop partition activity_sep_2009
  
  I still get the same error that the columns are referenced in other tables. But there is no line at all in the child table that references the table to partition/parent (since I dropped the score just a while ago)
  
  Please suggest what the problem?

  *parent*
  
  
  CREATE TABLE ACTIVITYLOG(
    activity_log_id Number NOT NULL,
    activity_date_time Date NOT NULL,
    activity_category Varchar2(50) NOT NULL,
    activity_type Varchar2(50) NOT NULL,
    customer_id Varchar2(20),
    customer_name Varchar2(70),
    usr_login Varchar2(32),
    usr_name Varchar2(100),
    simulate_mode Varchar2(20),
    constraint ACTIVITYLOG_PK primary key (activity_log_id,activity_date_time) 
  ) ORGANIZATION INDEX COMPRESS
  
  PARTITION BY RANGE (activity_date_time)
  
   (PARTITION activity_sep_2009 VALUES LESS THAN (TO_DATE(' 10/01/2009 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_oct_2009 VALUES LESS THAN (TO_DATE(' 11/01/2009 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_nov_2009 VALUES LESS THAN (TO_DATE(' 12/01/2009 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_dec_2009 VALUES LESS THAN (TO_DATE(' 01/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_jan_2010 VALUES LESS THAN (TO_DATE(' 02/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_feb_2010 VALUES LESS THAN (TO_DATE(' 03/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_mar_2010 VALUES LESS THAN (TO_DATE(' 04/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_apr_2010 VALUES LESS THAN (TO_DATE(' 05/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_may_2010 VALUES LESS THAN (TO_DATE(' 06/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_jun_2010 VALUES LESS THAN (TO_DATE(' 07/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_jul_2010 VALUES LESS THAN (TO_DATE(' 08/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_aug_2010 VALUES LESS THAN (TO_DATE(' 09/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_sep_2010 VALUES LESS THAN (TO_DATE(' 10/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_oct_2010 VALUES LESS THAN (TO_DATE(' 11/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_nov_2010 VALUES LESS THAN (TO_DATE(' 12/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_dec_2010 VALUES LESS THAN (TO_DATE(' 01/01/2011 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS
   ) ;
  
  
  
  *child*
  
  
  CREATE TABLE ACTIVITYLOGDATA(
    logdata_id Number NOT NULL,
    activity_log_id Number NOT NULL,
    activity_date_time Date NOT NULL,
    data_key Varchar2(50) NOT NULL,
    parameters Varchar2(50),
    ordinal Number,
    text_value varchar2(100),
    integer_value number,
    date_value date,
    boolean_value char(1),
    currency_value Number(20,4),
    CONSTRAINT ACTIVITYLOGDATA_PK PRIMARY KEY (logdata_id,activity_log_id,activity_date_time),
    CONSTRAINT ACTIVITYLOG_LOGDATA_FK FOREIGN KEY (activity_log_id,activity_date_time) REFERENCES ACTIVITYLOG (activity_log_id,activity_date_time) ON DELETE CASCADE,
    CONSTRAINT ACTIVITYLOGDATA_FK  FOREIGN KEY (data_key) REFERENCES ACTIVITYLOGDATADEFINITION (DATA_KEY) ON DELETE CASCADE
  
  )ORGANIZATION INDEX  COMPRESS
  PARTITION BY RANGE (activity_date_time)
  
   (PARTITION activity_sep_2009 VALUES LESS THAN (TO_DATE(' 10/01/2009 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_oct_2009 VALUES LESS THAN (TO_DATE(' 11/01/2009 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_nov_2009 VALUES LESS THAN (TO_DATE(' 12/01/2009 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_dec_2009 VALUES LESS THAN (TO_DATE(' 01/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_jan_2010 VALUES LESS THAN (TO_DATE(' 02/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_feb_2010 VALUES LESS THAN (TO_DATE(' 03/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_mar_2010 VALUES LESS THAN (TO_DATE(' 04/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_apr_2010 VALUES LESS THAN (TO_DATE(' 05/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_may_2010 VALUES LESS THAN (TO_DATE(' 06/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_jun_2010 VALUES LESS THAN (TO_DATE(' 07/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_jul_2010 VALUES LESS THAN (TO_DATE(' 08/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_aug_2010 VALUES LESS THAN (TO_DATE(' 09/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_sep_2010 VALUES LESS THAN (TO_DATE(' 10/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_oct_2010 VALUES LESS THAN (TO_DATE(' 11/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_nov_2010 VALUES LESS THAN (TO_DATE(' 12/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS,
    PARTITION activity_dec_2010 VALUES LESS THAN (TO_DATE(' 01/01/2011 00:00:00', 'MM/DD/YYYY HH24:MI:SS')) COMPRESS
   ) ;

  raj_fresher wrote:

  This means that to remove a partition on a table... need a stand-alone table with out any FK referencing tables?

  Yes and no. There should be no FK pointing to it at the time of the fall. So before you delete the partition, you can:

  (a) child table lock
  table b) make sure child does not parent rows to be fallen partition reference. If you can remove/set null these kids lines.
  (c) drop FK
  (d) drop partition
  (e) recreate FK
  (f) to release child table

  SY.

• ALTER TABLE SHRINK the SPACE COMPACT takes a long time

  Hello
  I run:
  ALTER TABLE TOM. TAB1 SHRINK SPACE COMPACT;
  ALTER TABLE TOM. TAB1 SHRINK SPACE WATERFALL;

  
  The "ALTER TABLE TOM. Tab1 SHRINK SPACE COMPACT"was completed in 2 hours, but"ALTER TABLE TOM. Tab1 SHRINK SPACE WATERFALL"is still underway after 8 hours, less than the size of the table TAB1 and index:

  NOM_SEGMENT... GB
  TAB1................................. 166
  IDX01................................ 83
  SYS_C00......................... 42
  IDX02............................. 142
  IDX03.............................. 66
  IDX04............................. 122

  
  Why 'SHRINK the SPACE COMPACT' takes a lot of time?
  Is it possible to check how much time should I take?

  Thanks in advance!

  Running

  ALTER INDEX TOM. TAB1_IDX03 SHRINK SPACE COMPACT;

  ALTER INDEX TOM. TAB1_IDX03 SHRINK SPACE;

  set is useless, as does 'SHRINK the SPACE' that means "SHRINK SPACE COMPACT" and much more (see the quote from the Doc Oracle Hemant).  2, 'SHRINK the SPACE' is the operation that will take more time.  So if 'SHRINK the SPACE' is what you wanted (reclaim space) and you can afford to wait, run 'SHRINK the SPACE' only.

  "SHRINK the COMPACT SPACE" is a part of the work that 'SHRINK the SPACE' is only.  Generally, use you it when time is at a premium: you run SHRINK SPACE COMPACT a weekday evening (because SHRINK the SPACE does not fit in one night and accrue hourly) and you run SHRINK SPACE on the weekend to finish following the recovery of your space.

  Regarding the fact that the entire segment or a partition after another, I have no experience - I both of their time and test methods.  Perhaps running several sessions at the same time on different partitions would save time (but be more heavy on the CPU and storage).

  Also note that SHRINK the AREA generates a lot of REDO (keep an eye on the free space of your ARCHIVELOG destination).  With your data volume, I would expect dozens (or even hundreds) of gigabytes of roll forward must be generated.