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.

Tags: Database

Similar Questions

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

Reclaim space after ALTER TABLE DROP PARTITION
Hello

I have a partitioned table. My requirement is to reclaim the space by dropping a partition of the table.

Is it possibe to recover space for the tablespace by dropping a partition of partition table?

Thank you
Hello

ALTER TABLE DROP PARTITION will always return the space to the storage to be reused by other segments.

It's the ALTER TABLE TRONQUER SCORE, where you can specify DROP STORAGE or of REUSE STORAGE clause (in case of re-use, the space is not released and can be used by the new lines inserted in the same partition). The DROP STORAGE should be the default option.

But for the fall of the score, you don't have to worry.

Kind regards
Martin

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 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.

Exchange partition questions
I'm about 10 gr 2.

(1) is it possible to exchange the partition between two tables LIST partitioned? I know that it is possible to exchange the partition between a partitioned table and a non-partitioned table, but not sure on two partitioned table. One has done this?

(2) if I run thereafter, what happens to SELECT those already underway on the table Partitioned P1? He will continue, or will be interrupted? My result will be based on the old data or exchanged data? i.e. read consistency apply in this case?

ALTER TABLE T1 EXCHANGE PARTITION P1 with table T2

Thanks in advance for your help.
max71 wrote:
I'm about 10 gr 2.

(1) is it possible to exchange the partition between two tables LIST partitioned? I know that it is possible to exchange the partition between a partitioned table and a non-partitioned table, but not sure on two partitioned table. One has done this?

No,
You can exchange a simple table with a partition of a partitioned table.
You can exchange a partitioned table (simple) whole with a single partition of a partitioned table composite. To move a partition of a partitioned table to another list, you will have to do a 'double-Exchange' (or worse).

for example, to swap partition pX table pt1 with partition table pt2 pY:

Create a simple table empty good shape T
change the exchange table PT1 partition pX with table t.
ALTER table Exchange partition with table T pY pT2
change the exchange table partition pX with table T pT1
Drop table T

(2) if I run thereafter, what happens to SELECT those already underway on the table Partitioned P1? He will continue, or will be interrupted? My result will be based on the old data or exchanged data? i.e. read consistency apply in this case?

ALTER TABLE T1 EXCHANGE PARTITION P1 with table T2

In simple cases, the result will be correct. Oracle has introduced a form of "cross-DDL" read-consistency in Oracle 8.0 for exactly this reason. It is possible (although unlikely after so many years) you might find some bugs in there in complicated cases. I know that in the early days, I had some cases where the motions silently lose partitions after an Exchange and give erroneous results.

The thing to watch is that data segments you renamed (and still need queries to see) does not get too wrote. For example, a query on T1 that began just before the Exchange that you quote above will want to see the data of the thing which is now table T2 - and it's possible. Even if you delete the table T2, the query can still finish safely. But if you drop T3 and then create a new object that replaces the hole left by T2, the application will crash when it starts to read this space with an error such as ORA-01410 invaliid rowid, or something similar.

Concerning
Jonathan Lewis
http://jonathanlewis.WordPress.com
http://www.jlcomp.demon.co.UK

"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge." Stephen Hawking.

Invalid option to TRUNCATE PARTITION in ALTER TABLE

Below edit sql works fine when I run this one.
ALTER TABLE table_name TRUNCATE partition partition_nm UPDATE GLOBAL INDEXES;
But if I run this procedure I get the error message "14054. 00000 - option ALTER TABLE TRUNCATE PARTITION invalid"
create or replace PROCEDURE TRUNCATE_WS_CLAIMS_REPORT
as
whole crsor;
rval around edge;
Start
crsor: = dbms_sql.open_cursor;
DBMS_SQL. Parse (crsor, ALTER TABLE table_name TRUNCATED partition partition_nm INDEXES', dbms_sql.v7 GLOBAL UPDATE);
rval Tip: = dbms_sql.execute (crsor);
DBMS_SQL.close_cursor (crsor);
end;
Can you guide me how to solve this error?

Have you tried to run immediately instead of dbms_sql?

Start

run immediately "ALTER TABLE table_name partition TRUNCATE partition_nm UPDATE GLOBAL INDEXES";

end;

ALTER table move lob segment of a partition

How I could move a LOB from a table segment partitioned (11.1 DB)?

I have after the table script:

CREATE TABLE COMMON.TEST_AAA2_ARH
(
  ID           INTEGER,
  TEKST        VARCHAR2(200 CHAR),
  UPDATESTAMP  DATE,
  OBJEKAT      CLOB
)
LOB (OBJEKAT) STORE AS (
  TABLESPACE COMMON_ARCHIVE
  ENABLE       STORAGE IN ROW
  CHUNK       8192
  RETENTION
  NOCACHE
  LOGGING)
TABLESPACE COMMON_ARCHIVE
LOGGING
PARTITION BY RANGE (UPDATESTAMP)
(  
  PARTITION P_201012 VALUES LESS THAN (TO_DATE(' 2011-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    LOGGING
    NOCOMPRESS 
    TABLESPACE COMMON_DATA
    LOB (OBJEKAT) STORE AS (
      TABLESPACE USERS
      ENABLE       STORAGE IN ROW
      CHUNK       8192
      PCTVERSION  10
      NOCACHE
      LOGGING),  
  PARTITION P_201101 VALUES LESS THAN (TO_DATE(' 2011-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    LOGGING
    NOCOMPRESS 
    TABLESPACE COMMON_DATA
    LOB (OBJEKAT) STORE AS (
      TABLESPACE USERS
      ENABLE       STORAGE IN ROW
      CHUNK       8192
      PCTVERSION  10
      NOCACHE
      LOGGING),  
  PARTITION P_MAXVALUE VALUES LESS THAN (MAXVALUE)
    LOGGING
    NOCOMPRESS 
    TABLESPACE COMMON_ARCHIVE
    LOB (OBJEKAT) STORE AS (
      TABLESPACE COMMON_ARCHIVE
      ENABLE       STORAGE IN ROW
      CHUNK       8192
      PCTVERSION  10
      NOCACHE
      LOGGING)
)
NOCOMPRESS 
NOCACHE
NOPARALLEL
MONITORING;

and I would switch USERS tablespace lob segment to the other...

TNX

ALTER table move partition lob () store as (tablespace )

SQL> CREATE TABLE WISSEM.TEST_AAA2_ARH
(
  ID           INTEGER,
  TEKST        VARCHAR2(200 CHAR),
  UPDATESTAMP  DATE,
  OBJEKAT      CLOB
)
LOB (OBJEKAT) STORE AS (
  TABLESPACE EXAMPLE
  ENABLE       STORAGE IN ROW
  CHUNK       8192
  RETENTION
  NOCACHE
  LOGGING)
TABLESPACE EXAMPLE
LOGGING
PARTITION BY RANGE (UPDATESTAMP)
(
  PARTITION P_201012 VALUES LESS THAN (TO_DATE(' 2011-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    LOGGING
    NOCOMPRESS
    TABLESPACE EXAMPLE
    LOB (OBJEKAT) STORE AS (
      TABLESPACE USERS
      ENABLE       STORAGE IN ROW
      CHUNK       8192
      PCTVERSION  10
      NOCACHE
      LOGGING),
  PARTITION P_201101 VALUES LESS THAN (TO_DATE(' 2011-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    LOGGING
    NOCOMPRESS
    TABLESPACE EXAMPLE
    LOB (OBJEKAT) STORE AS (
      TABLESPACE USERS
      ENABLE       STORAGE IN ROW
      CHUNK       8192
      PCTVERSION  10
      NOCACHE
      LOGGING),
  PARTITION P_MAXVALUE VALUES LESS THAN (MAXVALUE)
    LOGGING
    NOCOMPRESS
    TABLESPACE EXAMPLE
    LOB (OBJEKAT) STORE AS (
      TABLESPACE EXAMPLE
      ENABLE       STORAGE IN ROW
      CHUNK       8192
      PCTVERSION  10
      NOCACHE
      LOGGING)
)
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;
  2    3    4    5    6    7    8    9   10   11   12   13   14   15   16   17   18   19   20   21   22   23   24   25   26   27   28   29   30   31   32   33   34   35   36   37   38   39   40   41   42   43   44   45   46   47   48   49   50   51   52   53   54   55   56
Table created.

SQL> ALTER TABLE WISSEM.TEST_AAA2_ARH MOVE LOB (OBJEKAT) STORE AS (TABLESPACE USERS);
ALTER TABLE WISSEM.TEST_AAA2_ARH MOVE LOB (OBJEKAT) STORE AS (TABLESPACE USERS)
                   *
ERROR at line 1:
ORA-14511: cannot perform operation on a partitioned object

SQL> ALTER TABLE WISSEM.TEST_AAA2_ARH MOVE PARTITION P_201101 LOB (OBJEKAT) STORE AS (TABLESPACE USERS);

Table altered.

SQL>

Published by: orawiss on May 5, 2011 14:03

Partitioning of an existing Table using the EXCHANGE PARTITION

Hi all
I have one unpartitioned table I partitioned by Exchange, this table has several indexes and constraints (primary and foreign).
```
ALTER TABLE notpart_table ADD (
    CONSTRAINT PK_KCESPITI PRIMARY KEY (K_CESP, TIPORD)
        USING INDEX TABLESPACE TBLS_CONTA,
    CONSTRAINT FK_KCONTO_CE FOREIGN KEY (K_CONTO) REFERENCES xxxx (K_CONTO));

CREATE INDEX IX_NFATTURA_CE ON notpart_tab (ANNO_FATTURA, K_REGISTRO, K_REGFA, TIPORD)
    TABLESPACE TBLS_CONTA;
```
after Create a partitioned Table Destination
notpart_table2, I created the same constraints and indexes defined in notpart_table

When I run
```
ALTER TABLE notpart_table2
  EXCHANGE PARTITION PART_notpart_table2
  WITH TABLE notpart_table
  WITHOUT VALIDATION
  UPDATE GLOBAL INDEXES;
```
I get: ora-02266
Why?
Thanks in advance for any help

Post edited by: vigilant Rosario

It is not exactly what you have. Very probably not partitioned table, you are partitioning is the parent to another table table:

SQL > create table tbl1 (id number)
2.

Table created.

SQL > alter table tbl1
2 Add the constraint tbl1_pk
3 primary key
4.

Modified table.

SQL > create table tbl2 (id number)
2.

Table created.

SQL > alter table tbl2
2 Add the constraint tbl1_fk1
3 foreign key
4 references tbl1
5.

Modified table.

SQL > insert into tbl1 values (1)
2.

1 line of creation.

SQL > insert into tbl2 values (1)
2.

1 line of creation.

SQL > create table tbl1_part (id number)
2 partition by range (id)
3 (partition p1 values less than (1000000))
4.

Table created.

SQL >
SQL > alter table tbl1_part
Exchange 2 partition p1
3 with table tbl1
4 without validation
5 update global indexes
6.
with table tbl1
*
ERROR at line 3:
ORA-02266: permit to unique/primary keys in table referenced by foreign keys

SQL >

If so, of the foreign key and recreate it pointing to the partitioned table as parent after finished partitioning the table.

SY.

Exchange partition taking so long?
Hello

Oracle 11.1.0.7 version.

Why partition exchange took 10 minutes longer?

Here is my code

Table TAB is siloed single list
```
 CREATE OR REPLACE PROCEDURE load_tab;
   IS
      
      starttime   NUMBER;
      endtime     NUMBER;
      BEGIN
 BEGIN     


EXECUTE IMMEDIATE 'TRUNCATE TABLE TAB_TEMP;'

-- Dropping the index on temp table

 EXECUTE IMMEDIATE 'DROP INDEX TAB_TEMP_IDX01';
 
 BEGIN
 INSERT /*+ append */ INTO TAB_TEMP
 Select col1,col2,...coln from table1@DBLINK1,table2@DBLINK1,table3@DBLINK1 where join conditions;
 
 commit;
 END;
 
 EXECUTE IMMEDIATE 'CREATE INDEX TAB_TEMP_IDX01 ON TAB_TEMP
 (COL1)
 NOLOGGING
 TABLESPACE CSP_INDX
PARALLEL';
 
 
  Gathering stats on temp table;
 
 
 EXECUTE IMMEDIATE 'TRUNCATE TABLE TAB';
 
  starttime := SYS.DBMS_UTILITY.get_time;


 EXECUTE IMMEDIATE 'ALTER TABLE TAB  EXCHANGE PARTITION p1  WITH TABLE TAB_TEMP  WITHOUT VALIDATION UPDATE GLOBAL INDEXES';

  endtime := SYS.DBMS_UTILITY.get_time;
  
  
  logging total time taken for partition exchange on a log table ((endtime-statrtime)/100));


EXECUTE IMMEDIATE 'TRUNCATE TABLE TAB_TEMP';


EXCEPTION Block;

END;

END load_tab;
```
Please let me know why partiton Exchange taking so long? here a few times it takes 30 minutes and some time 10-15 minutes.

I was under the impression that the exchange of partion is nothing but the update of the data dictionary. Please clarify my doubt?

Thank you
Mike
If you don't have a comprehensive index on the partition table, but only local indexes, then more of the optimal approach is:

(1) create the staging table (similar to the partition table)

(2) double local indexes on the table to partition in the staging table

(3) an exchange of partition table using alter table... swap partition.. with table... including the index without validation

Such an exchange of partition must be second - as sole owner of the materials are exchanged and no treatment/audit/additional validation isn't required.

Of course, the assumption is that the intermediate table has valid data for the content of the partition it will replace.

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.

ALTER TABLE RETRACTABLE is possible online?

RDBMS Version: 11.2.0.4
Platform: Oracle Linux 6.4
We have a database of CARS of Production 2 nodes very critical. To recover the space, we want to cut some large tables. The first table we'll shrink is a 300 GB, which is not partitioned with no LOB table.
Here are the steps that we'll run.
Step1.alter mytable table allow the movement of the line;
Step2.alter mytable table shrink space compact;
Step3.alter mytable table shrink space;
Step4.alter table mytable disable the movement of the line;
STEP 5. COLLECT STATISTICS of the table (because the RETRACTABLE table will cancel all the sliders in the shared pool)
The steps above will take at least 10 hours to complete a 300 GB table. We would like to know if all of these steps can be done online. That is to say. We do not want the SHRINK command to lock the table and prevents the table to be modified (any DML) by the application
Doc below said this can be done online. But, MOS DOC 1357878.1 said that it is not and you must use the DBMS_REDEFINITION package if you want to do it online.
https://docs.Oracle.com/CD/E18283_01/server.112/e17120/schema003.htm

The MOS article you are talking about is not correct. Outside the DOF at the end of a SHRINK lock when the high tide is shifted, SHRINK the SPACE is an online operation. DBMS_REDEFNITION is actually worse because you have DDL locks at both the beginning and the end. However, in both cases, it is the DDL that is blocked by other operations DML (and not the other way around) so that your users will have no problem. If the narrowing or the redefinition is blocked, you can suspend the database for a few seconds. I described how to do here,

Database Quiesce

--

John Watson

Oracle Certified Master s/n

ALTER TABLE hf_altertest ADD COLUMN does not

I am using ORACLE 11g and my FDI is Developer SQL 4.1.1
It's all free PC version that has limits.
I tried on:
CREATE TABLE hf_altertest
(
contact_id INTEGER NOT NULL
, name VARCHAR (25)
, last_name VARCHAR (35)
PRIMARY KEY (contact_id)
);
ALTER TABLE hf_altertest State to add a CHAR (2) COLUMN;
But when I go to run the ALTER TABLE statement then I get following error:
rror starting at line: 1 323 in command.
ALTER TABLE hf_altertest State to add a CHAR (2) COLUMN
Error report-
SQL error: ORA-00904: invalid identifier
00904, 00000 - '% s: invalid identifier '.
* Cause:
* Action:
I can run the same code in MySQL without error.
This leads me to think that maybe I'm just bumping into a limit in the free version of PC.
Any thoughts?

3003916 wrote:

I am using ORACLE 11g and my FDI is Developer SQL 4.1.1

It's all free PC version that has limits.

ALTER TABLE hf_altertest State to add a CHAR (2) COLUMN;

But when I go to run the ALTER TABLE statement then I get following error:

rror starting at line: 1 323 in command.

ALTER TABLE hf_altertest State to add a CHAR (2) COLUMN

Error report-

SQL error: ORA-00904: invalid identifier

00904, 00000 - '% s: invalid identifier '.

* Cause:

* Action:

I can run the same code in MySQL without error.

This leads me to think that maybe I'm just bumping into a limit in the free version of PC.

Any thoughts?

There is no LIMIT to the 'free' version If you read the error message he said THAT was not a valid identifier. Just to show you that I tried your erroneous statement
```
ALTER TABLE hf_altertest ADD COLUMN state2 CHAR(2);
```
and here is the indicator error message in SQL +.

SQL * more: Production of liberation 12.1.0.2.0 Tue Oct 15 14:34:57 2015

Copyright (c) 1982, 2014, Oracle. All rights reserved.

Connected to:

Oracle Database 11 g Enterprise Edition Release 11.2.0.4.0 - 64 bit Production

With the partitioning, Real Application Clusters, Automatic Storage Management, OLAP

and Data Mining options

Add a COLUMN state2 TANK (2)

*

ERROR on line 2:

ORA-00904: invalid identifier

As you can see (and as the previous poster of response indicates), the 'COLUMN' KEYWORD is not necessary when adding new columns. Only when 'RENAME' is used, then you add the keyword COLUMN.

See the documentation for the syntax of ALTER TABLE here--> http://docs.oracle.com/database/121/SQLRF/statements_3001.htm#SQLRF01001

See specific clause RENAME syntax here--> http://docs.oracle.com/database/121/SQLRF/statements_3001.htm#i2183480

Conversion table of Partition Non-Partition and vice versa
Hello

I followed the method of Partition to Partition and vice versa conversion table below. Please suggest is here
any other altrnative methods available to accomplish the same thing.

Conversion table of partition table partitions. Export data, drop the table, create the table with partitions and
import data into the same table, now, the data is organized with Partitions.

Conversion table of partition table non-partition. Export data, drop the table, create the table without partitions and
import data into the same table, now, the data are organized without Partitions.

Thank you.
Google "oracle Exchange partition".

ALTER table move online in an encrypted tablespace

Hello
Our DBA want to put all our data in encrypted storage.
Once they create encrypted tablespaces, we will have to do «alter table move online...» "orders for encrypted storage space around the tables.
Has anyone here done already? Keeps the table moved really 'on-line' (available at query/insert/update) during the move? Or will we have to wait some time stop/downtime while the tables are moved?
What about the tables with long or CRAFT?
Thank you!

KSandberg and to add to the recall of John that only ITO tables can be moved online, if the table needs to be moved offline the indexes would be invalid until rebuilt. If the table is an IOT I suggest you rebuild the index online after the move because even if the indexes are always used the logical ROWID is more pointing to the correct location and access of the index will be less effective that will you rebuild the index.

- -

The dbms_redefinition package could be an alternative solution if you need to move the tables no - ITO online.

- -

HTH - Mark D Powell.

alter table Exchange partition

Similar Questions

Maybe you are looking for