Tablespace about partitioned table

Guys,
I've had some issues with the partitioned tables. Scenario is like this..
I have had a table, which was partitioned. I had to move all the partitions of this table to a new one, which worked fine and dropped the old tablespace. But now when i try to split the partition, the table still referes to the old tablespace name at a higer level. How do i change this..
I am refering to the USER_DATA on top, which is the default tablespace for the user.
It looks something like :
CREATE TABLE XCM_CU19_ASGN_DLR
XCM_CONSUMER_PK    VARCHAR2(14 BYTE)          NOT NULL,
COUNTRY_ISO3_C     VARCHAR2(3 BYTE)           NOT NULL,
CUST_CUSTOMER_R    NUMBER(11)                 NOT NULL,
CUD_DLR_CTRY_C     VARCHAR2(3 BYTE)           NOT NULL,
CUD_DLR_C          VARCHAR2(8 BYTE)           NOT NULL,
CUD_DLR_ROLE_C     INTEGER,
CUD_DLR_REF_X      VARCHAR2(15 BYTE),
CUD_DLR_ST_Y       DATE,
CUD_DLR_END_Y      DATE,
P_CUD_DLR_SRC_C    INTEGER,
P_UPDATE_ID_C      VARCHAR2(8 BYTE),
P_UPDATE_S         DATE,
XCM_UPDATE_S       DATE,
IBMSNAP_LOGMARKER TIMESTAMP(6)
TABLESPACE USER_DATA
PCTUSED    40
PCTFREE    10
INITRANS   1
MAXTRANS   255
PARTITION BY RANGE (COUNTRY_ISO3_C)
PARTITION PRT001 VALUES LESS THAN ('CZE')
    LOGGING
    NOCOMPRESS
    TABLESPACE XCM04_DATA
    PCTUSED    40
    PCTFREE    10
    INITRANS   10
    MAXTRANS   255
    STORAGE    (
                INITIAL          20M
                NEXT             20M
                MINEXTENTS       1
                MAXEXTENTS       501
                PCTINCREASE      0
                FREELISTS        1
                FREELIST GROUPS 1
                BUFFER_POOL      DEFAULT
PARTITION PRT002 VALUES LESS THAN ('DNK')
    LOGGING
    NOCOMPRESS
    TABLESPACE XCM04_DATA
    PCTUSED    40
    PCTFREE    10
    INITRANS   10
    MAXTRANS   255
    STORAGE    (
                INITIAL          20M
                NEXT             20M
                MINEXTENTS       1
                MAXEXTENTS       501
                PCTINCREASE      0
                FREELISTS        1
                FREELIST GROUPS 1
                BUFFER_POOL      DEFAULT
PARTITION PRT003 VALUES LESS THAN ('FIN')
    LOGGING
    NOCOMPRESS
    TABLESPACE XCM04_DATA
    PCTUSED    40
    PCTFREE    10
    INITRANS   10
    MAXTRANS   255
    STORAGE    (
                INITIAL          20M
                NEXT             20M
                MINEXTENTS       1
                MAXEXTENTS       501
                PCTINCREASE      0
                FREELISTS        1
                FREELIST GROUPS 1
                BUFFER_POOL      DEFAULT
PARTITION PRT004 VALUES LESS THAN ('GBR')
    LOGGING
    NOCOMPRESS
    TABLESPACE XCM04_DATA
    PCTUSED    40
    PCTFREE    10
    INITRANS   10
    MAXTRANS   255
    STORAGE    (
                INITIAL          20M
                NEXT             20M
                MINEXTENTS       1
                MAXEXTENTS       501
                PCTINCREASE      0
                FREELISTS        1
                FREELIST GROUPS 1
                BUFFER_POOL      DEFAULT
PARTITION PRT005 VALUES LESS THAN ('GIB')
    LOGGING
    NOCOMPRESS
    TABLESPACE XCM04_DATA
    PCTUSED    40
    PCTFREE    10
    INITRANS   10
    MAXTRANS   255
    STORAGE    (
                INITIAL          20M
                NEXT             20M
                MINEXTENTS       1
                MAXEXTENTS       501
                PCTINCREASE      0
                FREELISTS        1
                FREELIST GROUPS 1
                BUFFER_POOL      DEFAULT
PARTITION PRT006 VALUES LESS THAN ('ITA')
    LOGGING
    NOCOMPRESS
    TABLESPACE XCM04_DATA
    PCTUSED    40
    PCTFREE    10
    INITRANS   10
    MAXTRANS   255
    STORAGE    (
                INITIAL          20M
                NEXT             20M
                MINEXTENTS       1
                MAXEXTENTS       501
                PCTINCREASE      0
                FREELISTS        1
                FREELIST GROUPS 1
                BUFFER_POOL      DEFAULT
PARTITION PRT007 VALUES LESS THAN ('USA')
    LOGGING
    NOCOMPRESS
    TABLESPACE XCM04_DATA
    PCTUSED    40
    PCTFREE    10
    INITRANS   10
    MAXTRANS   255
    STORAGE    (
                INITIAL          20M
                NEXT             20M
                MINEXTENTS       1
                MAXEXTENTS       501
                PCTINCREASE      0
                FREELISTS        1
                FREELIST GROUPS 1
                BUFFER_POOL      DEFAULT
PARTITION PRT008 VALUES LESS THAN (MAXVALUE)
    LOGGING
    NOCOMPRESS
    TABLESPACE XCM04_DATA
    PCTUSED    40
    PCTFREE    10
    INITRANS   10
    MAXTRANS   255
    STORAGE    (
                INITIAL          20M
                NEXT             20M
                MINEXTENTS       1
                MAXEXTENTS       501
                PCTINCREASE      0
                FREELISTS        1
                FREELIST GROUPS 1
                BUFFER_POOL      DEFAULT
NOCACHE
PARALLEL ( DEGREE 8 INSTANCES 1 )
ENABLE ROW MOVEMENT;Thanks

I've done this before but I couldn't find it quickly... hence I thought it was the MOVE TABLESPACE clause. But now I think what I did was:
ALTER TABLE xxx MODIFY DEFAULT ATTRIBUTES TABLESPACE yyy;See
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_3001.htm#i2131000
Cheers,
Colin

Similar Messages

Assigning dedicated tablespaces to partitioned table 11g

Hi,
I'm facing an issue trying to assign a dedicated tablespace to a range partitioned table using the NUMTOYMINTERVAL clause.
I'm working on Oracle 11g version and I would use the auto partition creation feature in order to create
each month a new partition to use in a log table.
Using the create statement, all work fine.
If I try to use the alter table statement, i got an error.
I understand that i cannot add a new partition (Oracle automatic feature)
but I need to assign a dedicated tablespace to the new partition Oracle is going to create.
Someone could help me?
Thank you in advance.

Adding an example on MyTable:
CREATE TABLE "MyTable"
(     "ID" NUMBER,
     "CREATION_DATE" TIMESTAMP (6) DEFAULT SYSTIMESTAMP,
     "PARTITION_DATE" DATE DEFAULT TRUNC(SYSDATE),
     "TIMESTAMP" VARCHAR2(50 BYTE),
     "FAULT_GENERATING_REQUEST" CLOB
PARTITION BY RANGE(PARTITION_DATE)
INTERVAL(NUMTOYMINTERVAL(1,'MONTH')) STORE IN (LOGTBS0512,LOGTBS0612,LOGTBS0712,LOGTBS0812)
     (PARTITION NEWCO_P_LOG0512 VALUES LESS THAN (TO_DATE('01-05-2012', 'DD-MM-YYYY'))
TABLESPACE LOGTBS0512
LOB ("FAULT_GENERATING_REQUEST") STORE AS(TABLESPACE LOG_LOB_0512 cache storage(freelists 10)),
PARTITION NEWCO_P_LOG0612 VALUES LESS THAN (TO_DATE('01-06-2012', 'DD-MM-YYYY'))
TABLESPACE LOGTBS0612
LOB ("FAULT_GENERATING_REQUEST") STORE AS(TABLESPACE LOG_LOB_0612 cache storage(freelists 10)),
PARTITION NEWCO_P_LOG0712 VALUES LESS THAN (TO_DATE('01-07-2012', 'DD-MM-YYYY'))
TABLESPACE LOGTBS0712
LOB ("FAULT_GENERATING_REQUEST") STORE AS(TABLESPACE LOG_LOB_0712 cache storage(freelists 10)),
PARTITION P_LOG0812 VALUES LESS THAN (TO_DATE('01-08-2012', 'DD-MM-YYYY'))
TABLESPACE LOGTBS0812
LOB ("FAULT_GENERATING_REQUEST") STORE AS(TABLESPACE LOG_LOB_0812 cache storage(freelists 10));

Assign dedicated tablespaces to partitioned table

Hi,
I'm facing an issue trying to assign a dedicated tablespace to a range partitioned table using the NUMTOYMINTERVAL clause. I'm working on Oracle 11g version and I would use the auto partition creation feature in order to create each month a new partition to use in a log table. Using the create statement, all work fine. If I try to use the alter table statement, i got an error. I understand that i cannot add a new partition (Oracle automatic feature) but I need to assign a dedicated tablespace to the new partition Oracle is going to create. Someone could help me?
Thank you in advance.

I also searching for same solutions. If anyone has an idea please let me know.

Magic Tablespace in partitioned Table

Hi,
i have a part. Table with two Partitions. That means i can use two Tablespaces?
Hmm i thought that till last week than i found this:
CREATE TABLE "SCOTT"."EMP_REORG"
( "EMPNO" NUMBER(4,0),
"DEPTNO" NUMBER
) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
STORAGE(
BUFFER_POOL DEFAULT)
/*************/ TABLESPACE "DATA" /**************** look here ***/
PARTITION BY RANGE ("DEPTNO")
(PARTITION "P10" VALUES LESS THAN (11)
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS" NOCOMPRESS ,
There is Tablespace Nr.3. How can i change the "DATA" Tablespace ???
Thanks in advance
Marco

Sorry should have tried it first myself you got:
ORA-14511: cannot perform operation on a partitioned object
The only solution is to drop and recreate ( moving the data into a temp table first ).
see:
https://metalink.oracle.com/metalink/plsql/f?p=130:14:4925561482255200027::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,330077.1,1,1,1,helvetica

Transportable tablespace and partitioned objects

Hi,
I have to transport tablespaces which have partitioned objects from one server to another. If anyone has a proven process to perform this operation, please share with us. Following is a sample of violation report sample I got for 1 tablespace:
VIOLATIONS
Partitioned table ARIES.A_BI_BOARD_USAGE is partially contained in the transport
able set: check table partitions by querying sys.dba_tab_partitions
Partitioned table ARIES.A_TESTING_SESSION is partially contained in the transpor
table set: check table partitions by querying sys.dba_tab_partitions
Default Partition (Table) Tablespace A_DATA_SML_000000 for A_BI_BOARD_USAGE not
contained in transportable set
Default Partition (Table) Tablespace A_DATA_SML_000000 for A_TESTING_SESSION not
contained in transportable set
Thanks
Satish

Hi,
I am trying to transport the whole tablespace. What happened is that during duplication process, somehow few tablespaces in target were in offline mode and so duplication did not ceate the files properly on auxiliary server. Now, I need to get the 3 tablespaces from production to integration enviornment. These tablespaces have lot of partitioned objects. So I am trying to find a way to transport these tablespaces.
Thanks
Satish

Index on Partitioned Table with Some ReadOnly Tablespaces

We have a warehouse with fact tables range partitioned on date - daily partitions with each month worth of partitions put into a specific monthly tablespace. Each month, we set the prior month's tablespace to READONLY. So our table ends up having data in readonly and read-write tablespaces.
We now have a change we need to make to one of the fact tables - we need to add a new column AND add an index to that column. But because we have partitions in readonly state, Oracle doesn't let us create the index and it also doesn't let us update the local unique key (unique index).
Is there a way we can do this without having to put the tablespaces in read-write mode? As importantly, what happens when we offline or drop some of the older tablespaces (for archiving purposes)? We need to find a way to add the index on just the read-write partitions.
Thanks.

We have a warehouse with fact tables range
partitioned on date - daily partitions with each
month worth of partitions put into a specific monthly
tablespace. Each month, we set the prior month's
tablespace to READONLY. So our table ends up having
data in readonly and read-write tablespaces.
We now have a change we need to make to one of the
fact tables - we need to add a new column AND add an
index to that column. But because we have partitions
in readonly state, Oracle doesn't let us create the
index and it also doesn't let us update the local
unique key (unique index).
Is there a way we can do this without having to put
the tablespaces in read-write mode? As importantly,
what happens when we offline or drop some of the
older tablespaces (for archiving purposes)? We need
to find a way to add the index on just the read-write
partitions.
Thanks.Hi,
Improvements in Oracle 10g to maintain local-partitioned indexes when you use partition DDL commands:
add partition, split partition, merge partiton, move partition.
ALSO, the associated indexes NO LONGER have to be stored on the same tablespace as the table (i.e. answer to your question).
On Oracle 9i: Local indexes are recommended on data warehouse platforms. In an OLTP system, global indexes are more common. On a data data warehouse, problems can be isoloted to one partition, the partitions moved, made r/o (like yours), no local indexes need to be rebuilt
Regarding your issue:
We now have a change we need to make to one of the
fact tables - we need to add a new column AND add an
index to that columnTo maintain the simplicity + functionality of your DW configuration, I think you need to change the TS to R/W, update the objects, then alter to R/O.
fyi
http://www.oracle.com/technology/deploy/availability/htdocs/online_ops.html

How to import partitioned tables in different tablespace

Hi everyone,
I try to import the partitioned tables in different tablespace.
Consider the following situation:
I have a dump file which is created by using "Export" utility. Some data are in partitioned tables, some of them are in non-partitioned tables. Also, all tables are located in "MYTBS" tablesapce. I try to import all data from this dump file to another database. I didn't get error messages when importing the data from non-partitioned tables. However, I got error message when importing the data from partitioned tables. The error message is: tablespace 'MYTBS' does not exist.
I just want to how I can solve this problem other than create 'MYTBS' tablespace for my new database.
Thanks in advance.
Angel

Hi,
I got the following error message:
IMP-00017: following statement failed with ORACLE error 959:
"CREATE TABLE "FACILITYCONNECTION",....., "CONNECTIONTYPE" "
"NUMBER(1, 0) NOT NULL ENABLE) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 25"
"5 PARALLEL ( DEGREE DEFAULT INSTANCES 1) NOLOGGING STORAGE( PCTINCREASE 0) "
"TABLESPACE "MYTBS" PARTITION BY RANGE ("CONNECTIONTYPE" ) (PARTITION "
""EXT" VALUES LESS THAN (1) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 S"
"TORAGE(INITIAL 65536) TABLESPACE "MYTBS" NOLOGGING, PARTITION "FAC" VA"
"LUES LESS THAN (2) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 STORAGE(I"
"NITIAL 65536) TABLESPACE "MYTBS" NOLOGGING )"
IMP-00003: ORACLE error 959 encountered
ORA-00959: tablespace 'MYTBS' does not exist
Thanks.
Angel

Oracle 11gR2 Partition tables not creating in default user tablespace

Hi all:
Not sure if i'm missing something or overlooked but when i create a partition table in a user schema, it is not creating in the schema's default tablespace instead creating with no assigned to any and using SYSTEM tablesspace.
create user dgp identified by dgp default tablespace dgp temporary tablespace temp;
grant connect, resource to dgp;select USERNAME,DEFAULT_TABLESPACE from dba_users where username ='DGP';
USERNAME DEFAULT_TABLESPACE
DGP DG
select table_name, tablespace_name, partitioned from all_tables where owner='DGP';
TABLE_NAME TABLESPACE_NAME PAR
AUDITLOG_P2 DG NO
AUDITLOG_P YES
This is the partition script i used --i also gave the tablespace name:
CREATE TABLE dgp.AUDITLOG_P(
entry_time DATE,
username VARCHAR2(14),
groupname VARCHAR2(100),
ip VARCHAR2(15),
command VARCHAR2(15),
directory VARCHAR2(300)
PARTITION BY RANGE (entry_time)
partition P_PAST VALUES LESS THAN (TO_DATE('2010-01-01','YYYY-MM-DD')),
tablespace DG;
============
What is it i'm missing? Anything different with Oracle 11gR2 on the partition creations?
Thanks for your help..
Regards,
Ash

Yes, i tried using the schema login adn creating the table as well as system with schemaname prefix....
this is what i get from the below
SQL> select def_tablespace_name from dba_part_tables where table_name ='AUDITLOG_P';
DEF_TABLESPACE_NAME
DG
SQL> select partition_name, tablespace_name from dba_tab_partitions where table_name='AUDITLOG_P';
PARTITION_NAME TABLESPACE_NAME
P_PAST DG
P_20100101 DG
P_20100102 DG
P_20100103 DG
P_20100104 DG
P_20100105 DG
P_20100106 DG
P_20100107 DG
P_20100108 DG
P_20100109 DG
P_20100110 DG
P_20100111 DG
P_20100112 DG
P_20100113 DG
P_20100114 DG
P_20100115 DG
P_20100116 DG
P_20100117 DG
P_20100118 DG
P_20100119 DG
P_20100120 DG
P_20100121 DG
P_20100122 DG
P_20100123 DG
P_20100124 DG
P_20100125 DG
P_20100126 DG
P_20100127 DG
P_20100128 DG
P_20100129 DG
P_FUTURE DG
31 rows selected.

Tablespace of a partitioned Table

Hi,
what is the meaning of the outer tablespace clause in a 'create table' statement, when in the table the tablespaces are defined for each partition?
f.e.:
create table PST_ER_ZIEL (
ID NUMBER(18) not null,
PST_ZIEL_ID NUMBER(9) not null,
PST_NODE_ID NUMBER(9) not null,
MESSOBJECT VARCHAR2(100) not null,
VSTKNR VARCHAR2(11) not null,
EVENT_STATUS NUMBER(2) not null,
EVENT_TIME DATE not null
partition by range
EVENT_TIME
partition
Day1
values less than
TO_DATE('2003: 2' , 'YYYY: DDD')
tablespace PST_EV_RT,
partition
Day2
values less than
TO_DATE('2003: 3' , 'YYYY: DDD')
tablespace PST_EV_RT
tablespace DATA1;
What will be stored in DATA1 after creating the table?
Thanx,
Balazs

The outer tablespace clause is the 'default' tablespace for new partitions. When you add a new partition without adefinition for a tablespace, it is stored in DATA1.

Dropping tablespace for a partitionned table

Hi all,
I have a table partitionned and I want to drop the tablespace for a specific partition. So what happen in the table if I drop one tablespace with a commande drop tablespace tbs including contents and datafiles;
Does the index unusable in this table?
Regards

No, you can not drop a tablespace which contains tables whose partitions are not completely contained in this tablespace.
db9i :SQL> create tablespace users2 datafile '/u02/oradata/db9i/users201.dbf' size 10M;
Tablespace created.
db9i :SQL> CREATE TABLE sales_by_region (item# INTEGER, qty INTEGER,
2 store_name VARCHAR(30), state_code VARCHAR(2),
3 sale_date DATE)
4 STORAGE(INITIAL 10K NEXT 20K) TABLESPACE test
5 PARTITION BY LIST (state_code)
6 (
7 PARTITION region_east
8 VALUES ('MA','NY','CT','NH','ME','MD','VA','PA','NJ')
9 STORAGE (INITIAL 20K NEXT 40K PCTINCREASE 50)
TABLESPACE users,
10   11 PARTITION region_west
12 VALUES ('CA','AZ','NM','OR','WA','UT','NV','CO')
13 PCTFREE 25
14 TABLESPACE users2,
15 PARTITION region_unknown
16 VALUES (DEFAULT)
17 TABLESPACE test
18 );
Table created.
db9i :SQL> insert into sales_by_region values (1, 100, 'store 1','NY',sysdate);
1 row created.
db9i :SQL> insert into sales_by_region values (2, 200, 'store 2','UT',sysdate);
1 row created.
db9i :SQL> insert into sales_by_region values (3, 300, 'store 3','ZZ',sysdate);
1 row created.
db9i :SQL> commit;
Commit complete.
db9i :SQL> select count(*) from sales_by_region
2 /
COUNT(*)
         3
--insure all data went to the right partition
db9i :SQL> alter table sales_by_region truncate PARTITION region_east;
Table truncated.
db9i :SQL> select count(*) from sales_by_region
2 /
COUNT(*)
         2
db9i :SQL> alter table sales_by_region truncate PARTITION region_west;
Table truncated.
db9i :SQL> select count(*) from sales_by_region
2 /
COUNT(*)
         1
db9i :SQL> alter table sales_by_region truncate PARTITION region_unknown;
Table truncated.
db9i :SQL> select count(*) from sales_by_region
2 /
COUNT(*)
         0
db9i :SQL> insert into sales_by_region values (1, 100, 'store 1','NY',sysdate);
insert into sales_by_region values (2, 200, 'store 2','UT',sysdate);
insert into sales_by_region values (3, 300, 'store 3','ZZ',sysdate);
1 row created.
db9i :SQL>
1 row created.
db9i :SQL>
1 row created.
db9i :SQL>
db9i :SQL>
db9i :SQL> commit;
Commit complete.
db9i :SQL> select count(*) from sales_by_region
2 /
COUNT(*)
         3
--now drop one tablespace
db9i :SQL> drop tablespace users2 including contents and datafiles
2 /
drop tablespace users2 including contents and datafiles
ERROR at line 1:
ORA-14404: partitioned table contains partitions in a different tablespace
db9i :SQL> !oerr ora 14404
14404, 00000, "partitioned table contains partitions in a different tablespace"
// *Cause: An attempt was made to drop a tablespace which contains tables
//         whose partitions are not completely contained in this tablespace
// *Action: find tables with partitions which span the tablespace being
//          dropped and some other tablespace(s). Drop these tables or move
//          partitions to a different tablespace
--move table partition from users2 to users
db9i :SQL> alter table sales_by_region move partition region_west
tablespace users; 2
Table altered.
--drop tablespace again
db9i :SQL> drop tablespace users2 including contents and datafiles
2 /
Tablespace dropped.

Tablespace move in partitioned tables

I moved partitioned tables in new tablespace dedicated for 2006 data, do i need to move table relaed indexes in new tablespace also.?

No,
global Indexes will be invalid and have to be rebuild. If you have local Indexes you only have to rebuild the affected partitions. Nothing else to do.
Dim

Migrating a new partition table with transportable tablespace

I created a partitioned table with 2 partitions (2010 and 2011) and used transportable tablespace to migrate the data over to a new envionment. My question is, if I decide to add a partition (2012) in the future, can I simply move that new partition along with the associated datafile via transportable tablespace or would I have to move all the partitions (2010, 2011, 2012).

user564785 wrote:
I created a partitioned table with 2 partitions (2010 and 2011) and used transportable tablespace to migrate the data over to a new envionment. My question is, if I decide to add a partition (2012) in the future, can I simply move that new partition along with the associated datafile via transportable tablespace or would I have to move all the partitions (2010, 2011, 2012).Yes why not.
1) create a table as CTAS from 2012 in new Tablespace on source
2) transport the tablespace
3) Add partition to existing partition table Or exchange partition
Oracle has also documented this procedure:
http://docs.oracle.com/cd/B28359_01/server.111/b28310/tspaces013.htm#i1007549

About partitioning in a oracle table. Please reply ASAP.

Hi,
I have partitioned a table, but now I want to check that partition are created successfully or not. Can anyone help me to know that how to find a partition table in the database?
Reagrds,
Arpan

query these tables to find the relevant information
DBA_PART_TABLES
ALL_PART_TABLES
USER_PART_TABLES
mark if it helps
make sure you post in right forum from next time

Performance between two partitionned tables with different structure

Hi,
I would like if there is a difference between two partitionned tables with different structure in term of performance (access, query, insertions, updates ).
I explain myself in detail :
I have a table that stores one value every 10 minutes in a day (so we have 144 values (24*6) in the whole day), with the corresponding id.
Here is the structure :
| Table T1 |
+ id PK |
+ date PK |
+ sample1 |
+ sample2 |
+ ... |
+ sample144 |
The table is partionned on the column date, with a partionned every months. The primary key is based on the columns (id, date).
There is an additionnal index on the column (id) (is it useful ?).
I would like to know if it is better to have a table with just (id, date, value) , so for one row in the first table we'll have 144 rows in the future? table. The partition will already be on the columns (id, date) with the index associated.
What are the gains or loss in performance with this new structure ( access, DMLs , storage ) ?
I discuss with the Java developers and they say it is simpler to manage in their code.
Oracle version : Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
Thanks & Regards
From France
Oliver
Edited by: 998239 on 5 avr. 2013 01:59

I mean storage in tablespaces and datafiles on disk.
Can you justify please and give me concrete arguments why the two structures are equivalent ( except inserting data in T(id, date,value))
because i have to make a report.i didnt say any thing like
two structures are equivalent ( except inserting data in T(id, date,value)i said
About structure : TABLE1(id, date, value) is better than TABLE1(id, date, sample1, .... sample144)because
1) oracle has restriction for numbers of column. Ok you can have 144 columns now but for future if you must have more than 1000 columns , what will you do?
2) Restrictions on Table Compression (Table compression is not supported for tables with more than 255 columns.)
3) store same type values on diffrent columns is bad practise
http://docs.oracle.com/cd/B28359_01/server.111/b28318/schema.htm#i4383
i remember i seen Toms article about this but now i cant find it sorry ((( if i found i will post here

"Invalid segment" when shrinking a partitioned table

I'm encountering the following error when trying to shrink space compact for a partitioned table. Would you know how can I go about this?
I need to make it work.
SQL> alter table PS_SGSN_1_MONTH modify partition P_201304 shrink space compact;
alter table PS_SGSN_1_MONTH modify partition P_201304 shrink space compact
ERROR at line 1:
ORA-10635: Invalid segment or tablespace type
My Oracle DB version is 11gR2

Yes, that would be the right thing to do to check how and where MV is being used and what downtime you can get to fix this. Check if you can change the Materialized view to create based on primary key instead of Row id.
Steps would be
1 drop the materialized views related
2 drop the materialized views logs
3 shrink the tables and indexes
4 recreate the materialized views log
5 recreate the materialized views
Also, there is a bug with the primary key as well. Check this
Bug 13709220 - ORA-10663 when shrinking a master table of an MVIEW with primary key (Doc ID 13709220.8)

Tablespace about partitioned table

Similar Messages

Maybe you are looking for