create the list-range partition table

Database version: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi

I am trying to create a partition with beach-LIST table, and I get this error message, is the oracle 10.2.0.4 database supports to create the list range (composite) score

{
SQL > CREATE TABLE tbp_list_range
(
DATE OF REPORT_DATE,
member_id_01 varchar2 (2),
Date of DATE_SERVICE,
member_id varchar2 (15)
)
PARTITION OF LIST (member_id_01)
SUBPARTITION BY RANGE (DATE_SERVICE)
(
PARTITION SPTYR04M01_C VALUES ('AA', 'aa')
NOLOGGING
COMPRESS)
SUBPARTITION PTYR12M011 VALUES LESS THAN (TO_DATE (' 2012-01-01 00:00:00 ',' SYYYY-MM-DD HH24:MI:SS ',' NLS_CALENDAR = GREGORIAN ')),
SUBPARTITION PTYR12M021 VALUES LESS THAN (TO_DATE (' 2012-02-01 00:00:00 ',' SYYYY-MM-DD HH24:MI:SS ',' NLS_CALENDAR = GREGORIAN ')),
SUBPARTITION recent1 VALUES LESS THAN (MAXVALUE)
),
PARTITION SPTYR04M01_Yo VALUES ('BJ', 'bj')
NOLOGGING
COMPRESS)
SUBPARTITION PTYR12M01 VALUES LESS THAN (TO_DATE (' 2012-01-01 00:00:00 ',' SYYYY-MM-DD HH24:MI:SS ',' NLS_CALENDAR = GREGORIAN ')),
SUBPARTITION PTYR12M02 VALUES LESS THAN (TO_DATE (' 2012-02-01 00:00:00 ',' SYYYY-MM-DD HH24:MI:SS ',' NLS_CALENDAR = GREGORIAN ')),
SUBPARTITION recent2 VALUES LESS THAN (MAXVALUE)
)
)
/
SUBPARTITION BY RANGE (DATE_SERVICE)
*
ERROR on line 9:
ORA-00922: missing or not valid option

SQL > select * from v version $;

BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
AMT for Linux: release 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production

}

Any help would be greatly appreciated.

Thank you

There are no ladders of partitioning in 10g either.

Have a look here for partitioning methods: http://www.orafaq.com/wiki/Composite_partitioning

Tags: Database

Similar Questions

TIMESTAMP (6) partitioned key-> range partitioned table ddl needed
What is the DDL TIMESTAMP syntax (6) partitioned key, range partitioned table

Published by: oracletune on January 11, 2013 10:26
>
What is the DDL TIMESTAMP syntax (6) partitioned key, range partitioned table
>
Don't know what you're asking. Are you asking how to create a table partitioned using a TIMESTAMP column (6) for the key?
```
CREATE TABLE TEST1
(
    USERID                 NUMBER,
    ENTRYCREATEDDATE     TIMESTAMP(6)
)
PARTITION BY RANGE (ENTRYCREATEDDATE) INTERVAL(NUMTOYMINTERVAL(1, 'MONTH'))
(
    PARTITION P0 VALUES LESS THAN (TO_DATE('1-1-2013', 'DD-MM-YYYY'))
)
```
See my answer posted: January 10, 2013 21:56 if you need to do on a TIMESTAMP with TIME ZONE column. You must add a virtual column.
Creating scores of auto range

Range partitioned table is not created in the compressed format interavl

Hello

Using oracle 11.2.03. and trying to create a table with compress

Fine regular table but challenging syntax below but tabel properties don't show no compression

Tried to compress at the top of the sql as described and down

Aldso tried to compress and compress for oltp - bahviour even do not get compressed.

Now HSOING at the TABLE LEVEL or ON TABLE PORPETIES BUT WHEN check user_tab_partitions shows compressed for oltp

Thank you

create table RETAILER_TRANSACTION_comP_POR parallel
COMPRESS FOR OLTP

partition by range (PARTITIONING_DATE)
INTERVAL (NUMTOYMINTERVAL(1,'MONTH'))
subpartition by hash (PLANT_ISSUE_ID) 
subPARTITIONS 4
(
  partition PART_200912 values less than (TO_DATE(' 2010-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_200912
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201001 values less than (TO_DATE(' 2010-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201001
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201002 values less than (TO_DATE(' 2010-03-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201002
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201003 values less than (TO_DATE(' 2010-04-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201003
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201004 values less than (TO_DATE(' 2010-05-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201004
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201005 values less than (TO_DATE(' 2010-06-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201005
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201006 values less than (TO_DATE(' 2010-07-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201006
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201007 values less than (TO_DATE(' 2010-08-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
  tablespace RTRN_PART_201007
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201008 values less than (TO_DATE(' 2010-09-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201008
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201009 values less than (TO_DATE(' 2010-10-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201009
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201010 values less than (TO_DATE(' 2010-11-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201010
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201011 values less than (TO_DATE(' 2010-12-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201011
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201012 values less than (TO_DATE(' 2011-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201012
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201101 values less than (TO_DATE(' 2011-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201101
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201102 values less than (TO_DATE(' 2011-03-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201102
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201103 values less than (TO_DATE(' 2011-04-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201103
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201104 values less than (TO_DATE(' 2011-05-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201104
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201105 values less than (TO_DATE(' 2011-06-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201105
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201106 values less than (TO_DATE(' 2011-07-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201106
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201107 values less than (TO_DATE(' 2011-08-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201107
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201108 values less than (TO_DATE(' 2011-09-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201108
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201109 values less than (TO_DATE(' 2011-10-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201109
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201110 values less than (TO_DATE(' 2011-11-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201110
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201111 values less than (TO_DATE(' 2011-12-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201111
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201112 values less than (TO_DATE(' 2012-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
   tablespace RTRN_PART_201112
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201201 values less than (TO_DATE(' 2012-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201201
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201202 values less than (TO_DATE(' 2012-03-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
     tablespace RTRN_PART_201202
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201203 values less than (TO_DATE(' 2012-04-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201203
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201204 values less than (TO_DATE(' 2012-05-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201204
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201205 values less than (TO_DATE(' 2012-06-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
     tablespace RTRN_PART_201205
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201206 values less than (TO_DATE(' 2012-07-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201206
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201207 values less than (TO_DATE(' 2012-08-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
   tablespace RTRN_PART_201207
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201208 values less than (TO_DATE(' 2012-09-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201208
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201209 values less than (TO_DATE(' 2012-10-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201209
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201210 values less than (TO_DATE(' 2012-11-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201210
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201211 values less than (TO_DATE(' 2012-12-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201211
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201212 values less than (TO_DATE(' 2013-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
      tablespace RTRN_PART_201212
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201301 values less than (TO_DATE(' 2013-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
      tablespace RTRN_PART_201301
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201302 values less than (TO_DATE(' 2013-03-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201302
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201303 values less than (TO_DATE(' 2013-04-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201303
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201304 values less than (TO_DATE(' 2013-05-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
   tablespace RTRN_PART_201304
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201305 values less than (TO_DATE(' 2013-06-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201305
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201306 values less than (TO_DATE(' 2013-07-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201306
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201307 values less than (TO_DATE(' 2013-08-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201307
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201308 values less than (TO_DATE(' 2013-09-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201308
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201309 values less than (TO_DATE(' 2013-10-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201309
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201310 values less than (TO_DATE(' 2013-11-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201310
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201311 values less than (TO_DATE(' 2013-12-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201311
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    ),
  partition PART_201312 values less than (TO_DATE(' 2014-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace RTRN_PART_201312
    pctfree 1
    initrans 1
    maxtrans 255
    storage
    (
      initial 8M
      next 1M
      minextents 1
      maxextents unlimited
    )
)

--COMPRESS --FOR OLTP
as select *
from retailer_transaction RT
WHERE RT.DWH_NUM = 1441336376

Published by: user5716448 on March 26, 2013 07:16

>
Fine regular table but challenging syntax below but tabel properties don't show no compression
>
What are properties? You have not shown any query or result that indicates if the table is compressed or not.
>
Now HSOING at the TABLE LEVEL or ON TABLE PORPETIES BUT WHEN check user_tab_partitions shows compressed for oltp
>
I don't know what all this means.

New - you post anything indicating if the table is compressed or not. And without the DDL for the source table, no one can try to reproduce your results.

Thanks for the use of tags code ad some of the necessary DOF but you edit your message and must REMOVE all definitions of extra partition since everything they do is inflate the list.

It works for me 11.2.0.1.0 vanilla

create table EMP_PART parallel
COMPRESS FOR OLTP
partition by range (hiredate)
INTERVAL (NUMTOYMINTERVAL(1,'MONTH'))
subpartition by hash (deptno)
subPARTITIONS 4
(
  partition all_data values less than (to_date('01/01/2013', 'mm/dd/yyyy')
))
as select * from emp

select table_name, compression, compress_for, composite, partition_name
from user_tab_partitions

TABLE_NAME     COMPRESSION     COMPRESS_FOR     COMPOSITE     PARTITION_NAME
EMP_PART     ENABLED     OLTP     YES     ALL_DATA

Size of partition on interval range partitioned Table happens when SYSDATE is used in a Where Clause

We have tables interval range partitioned on a DATE, with a partition for each day column - very standard and straight out of doc Oracle.
A 3rd party application queries the tables to find the number of rows based on the date range that is located on the column used for the partition key.
This application uses the date range specified from the current date - i.e. for last two days would be «...» StartDate > SYSDATE-2 "- but the partition size is irrelevant and the explain command plan shows that each partition is included."
In presenting the request uses the date in a variable partition size location and query table is obviously much better.
DB is 11.2.0.3 on RHEL6, and default settings - i.e. nothing that could influence the behavior of the optimizer to something unusual.
I can't work on why this would be the case. It is very easy to reproduce with cases of simple test below.
I would be very interested to hear any views on why it's that way and if anything can be done to allow the size of the partition to work with a query including SYSDATE because it would be difficult to get the application code has changed.
In addition to make a case to change the code, I need an explanation of why query using SYSDATE is not advisable and I know this information.
(1) create a simple partitioned table
```
CREATETABLE part_test
   (id                      NUMBER NOT NULL,
    starttime               DATE NOT NULL,
    CONSTRAINT pk_part_test PRIMARY KEY (id)) 
PARTITION BY RANGE (starttime) INTERVAL (NUMTODSINTERVAL(1,'day')) (PARTITION p0 VALUES LESS THAN (TO_DATE('01-01-2013','DD-MM-YYYY')));
```
(2) fill in the rows of the table 1 million distributed among 10 partitions
```
BEGIN
    FOR i IN 1..1000000
    LOOP
        INSERT INTO part_test (id, starttime) VALUES (i, SYSDATE - DBMS_RANDOM.value(low => 1, high => 10));
    END LOOP;
END;
/
EXEC dbms_stats.gather_table_stats('SUPER_CONF','PART_TEST');
```
(3) to query the Table of data from the last 2 days using SYSDATE in paragraph
```
EXPLAIN PLAN FOR 
SELECT  count(*) 
FROM    part_test
WHERE   starttime >= SYSDATE - 2;
```
-------------------------------------------------------------------------------------------------------
| ID | Operation | Name | Lines | Bytes | Cost (% CPU). Time | Pstart. Pstop |
-------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT |           |     1.     3 × 7895 (1) | 00:00:01 |       |       |
|   1. GLOBAL TRI |           |     1.     3 ×            |          |       |       |
|   2.   RANGE OF PARTITION ITERATOR.           |   111K |   867K | 7895 (1) | 00:00:01 |   KEY | 1048575.
|* 3 |    TABLE ACCESS FULL | PART_TEST |   111K |   867K | 7895 (1) | 00:00:01 |   KEY | 1048575.
-------------------------------------------------------------------------------------------------------
Information of predicates (identified by the operation identity card):
---------------------------------------------------
3 - filter("STARTTIME">=SYSDATE@!-2)
(4) now do the same query, but with SYSDATE - 2 presented as a literal value.
This query returns the same response but very different cost.
```
EXPLAIN PLAN FOR
SELECT count(*) 
FROM part_test
WHERE starttime >= (to_date('23122013:0950','DDMMYYYY:HH24MI'))-2;
```
-------------------------------------------------------------------------------------------------------
| ID | Operation | Name | Lines | Bytes | Cost (% CPU). Time | Pstart. Pstop |
-------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT |           |     1.     8.   131 (0) | 00:00:01 |       |       |
|   1. GLOBAL TRI |           |     1.     8.            |          |       |       |
|   2.   RANGE OF PARTITION ITERATOR.           |   111K |   867K |   131 (0) | 00:00:01 |   356 . 1048575.
|* 3 |    TABLE ACCESS FULL | PART_TEST |   111K |   867K |   131 (0) | 00:00:01 |   356 | 1048575.
-------------------------------------------------------------------------------------------------------
Information of predicates (identified by the operation identity card):
---------------------------------------------------
3 filter ("STARTTIME" > = TO_DATE (' 2013-12-21 09:50 ',' syyyy-mm-dd hh24:mi:ss'))))
Thank you in anticipation
Jim

sysdate is not constant and its value may change from time optimization of execution; but the optimizer can deduce that he will be a known running value and then produce a plan that will make the size of partition running. This is the meaning of 'KEY' in the column pstart – the partition of departure will be known at run time and the size of partition will take place in order to eliminate the previous partitions.

Concerning

Jonathan Lewis

retrieve the information of partition table with lack of offline data file
I just restored a backup of a database. When I unzipped data files, I discovered that a single data file was so damaged in the starting order of the database, I had to put the offline data file. The tablespace which reports the data file holds the information of partition of a table. Since I have no archives from when the data file has been created, I know it is not possible to recover the data file, I have to recover as many lines as possible other files in the tablespace data but when export or create the table as what to choose in the affected partition get ORA-00376 : cannot read file 1624 at the moment.

is there a way to tell oracle to ignore the data offline file and export the remaining data file information?

Just to clarify my situation a little more;
iI have a table called PPGA_ACTABOPRE that is partitioned by HASH and has 20 partitions, each partition in a different tablespace and tablespace each have about 8 files of data. A data file in the partition 9 is missing and I want is to get the information from the files of the remaining data, but whenever I issue a select statement or an exp or anything I get ORA-00376.

I try to set the flag to ignore blocks corrupt with run DBMS_REPAIR. SKIP_CORRUPT_BLOCKS ('PPGA', 'PPGA_ACTABOPRE'); and then select the info but it did not work.

Any suggestion would be appreciated;
Thanks in advance
For the actabopre_p08 partition, some files are available, and we're not. You can access data at the segment level, because some extensions are missing.

You would need to access the data by rowid. You could loop through dba_extents and use dbms_rowid.create to generate a list of ROWID that may exist in the available data files.

This may help: -.

http://kerryosborne.Oracle-guy.com/2009/02/saving-rows-from-corrupt-blocks/
http://kerryosborne.Oracle-guy.com/scripts/save_u.SQL

Published by: Robert Geier on March 12, 2010 15:33

Delete the data in partitioned tables

Hello
Oracle 11.2.0.3.0 version, running on Linux Enterprise.
I need to remove all the data from two tables (several 100 million lines each) that are partitioned.
(1) table 1 is a partition table have varied to a DATE column
(2) Table2 is a partition of reference table; partitioning is referenced on a relationship of foreign key to Table1 (column: key Table1.Primary)
As I have no need for data, but want to keep the structure of the table, I would ideally like to delete partitions at the same time that the deletion of the data, so that the 2 tables partitioned and empty.
Additionally, Table1 has some partitioned index I would be rebuilt as an index unpartitioned (given that Table1 will be empty).
I thought I would start by removing all partitions of Table1 (via "ALTER TABLE DROP PARTITION nom_partition Table1"), but when the script came to the last partition, I got this error message:
ORA-14083: cannot delete the only one partition of a partitioned table
ORA-06512: at "SYS." DROP_PARTITIONS', line 46
If someone could advise as to the best approach to what I want to achieve with regard to the two tables? Two tables down and recreate them then without partitions would be the easiest way?
Thanks in advance for any guidance.

If someone could advise as to the best approach to what I want to achieve with regard to the two tables? Two tables down and recreate them then without partitions would be the easiest way?

Yes - delete the tables and re-create them.

As says the exception that you cannot delete the last partition. A table is partitioned either or it is not.

There was no interest at all to use DBMS_REDEFINITION to redefine tables because you do not want the data anyway.

The list of issue table
I have a list stored in the mysql database which looks like this: 12, 45, A, B, 87, 98

I need to use coldfusion to retrieve the list and convert each element to an element of a table. that is to say:
tempArray [0] = 12;
tempArray [1] = 45;

and so on. I need to do this because I'm back the created table flashing.

Thanks for your help!
The problem is not create table, which seems fine. The question I see is that you do not return the table, just the results of the query. If you need to return only the table, change your cfreturn to . If you need to return the results of the query and the table, then you will need to combine them somehow, as you can only return a thing with cfreturn.

CR

convert the list to a table

Is it possible to convert a list of items in a table of Pages?

I stopped "downgraded" Pages when Apple using this program dtp invaluable cheap old version 5... So I could be wrong and should be corrected by more knowledgeable people, but the only way I can see to turn a list into a table is to insert a table with the appropriate number of columns and lines (or remove those unnecessary thereafter) and spent in your list. For example:

How to create the list in SDK v5.0

Hello

I have SDK 5.0 with me.

I want to create a list as in the SDK v6.0but sdk v 5.0 software

for example, for version 6.0

MainManager Manager = getMainManager();
SimpleList listField = new SimpleList (mainManager);
listField.add ("Item 1");
listField.add ("Item 2").
listField.add ("Item 3").

Can someone help me in this creation.

When I want to go find info according to the selected item in the list.

Also, please tell me how to select the item.

Thank you

Afonso

Problem solved

listF.getSelectedIndex () used;

Analysis of query and get the list of used tables

Hi all
I need to parse the sql query (simple & complex as well) and for a list of the tables used in the query.
And need to validate the fact that list the tables against a whitelist that is kept in the file.
I tried to write my own parser, because there are many ways to write complex queries, I'm unable to cover all scenarios.
I need help, is there other ways to get the list of tables used in a query?
Thank you
Manon...

In general you would add a condition 1 = 2 just to restrict the display of the entire table. Then should not be causing any noticeable performance degradation. You can even use ROWNUM< 2.="" that="" will="" do="" a="" count="" stopkey.="" which="" could="" be="">

SQL > select * from emp where rownum<>

no selected line

SQL > select * from table (dbms_xplan.display_cursor);

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
SQL_ID, 97f4bd002xfy0, number of children 0
-------------------------------------
Select * from emp where rownum<>

Hash value of plan: 4269703525

---------------------------------------------------------------------------
| ID | Operation | Name | Lines | Bytes | Cost (% CPU). Time |
---------------------------------------------------------------------------
|   0 | SELECT STATEMENT |      |       |       |     2 (100) |          |
|* 1 | COUNT STOPKEY |      |       |       |            |          |
|   2.   TABLE ACCESS FULL | EMP |     1.    38.     2 (0) | 00:00:01 |
---------------------------------------------------------------------------

Information of predicates (identified by the operation identity card):
---------------------------------------------------

1 Filter (ROWNUM<>

19 selected lines.

But its always good to bench mark it yourself.

create the list of layers in a document

I'm looking for a script that will allow me to create a list of all the layers (divorced) in a document. I can create a string delimited by commas... but can not create a list of column...
Help... Please

Great help!

Thank you, problem solved.

Compression is disabled when performing the update on partitioned tables

Hi all
I'm on Oracle Database 11 g Enterprise Edition Release 11.2.0.3.0.
My question is related to the Compression of the Oracle.
I have an infra partitioned table enabled with Compression of the base. Active compressed State, I update some columns in this table (command Update Normal and merger as well) but the end result shows the increase in the size of the table and the compression is still in the ACTIVE State. After that, if I compress the secondary partition explicitly the table back to its original size.
Is this a bug? I read a whitepaper on 11g itself, compression is turned on in the case of all DML operations, so why this behavior?
Thank you
Ishan

Ishan,

take a look at http://docs.oracle.com/cd/E11882_01/server.112/e25494/tables.htm#CJAGFBFG , it seems that the distinction between OLTP and compression of base is sometimes a bit vague ("operations that allow compression include:...") "), but I also find the statement"insert rows inserted without using direct-path access and updated rows are uncompressed. "So I would say it's not a bug but a limitation of the service. Updates just to not mix well with compression.

Martin

How to create the list of indented bullet points

Hi all! I understand how to generate a bulleted list in which the balls line up on the left side of the text above/below in the list. However, I would like to create an indented bulleted list. And for some reason I'm not able to understand this! I enclose a sample of what I'm trying to do. Any help would be greatly appreciated. Thank you!
julice

OK, I've found a workaround. Looking at my example:

I put the left margin of 'éducation'-10.

The balls I put in:

Dash:-10

Left margin: 35

Who did the trick!

create the view of several tables of days
Hello
I'll have existing oracle db with the daily stat data, tables strangely named data_mon, data_tue, data_wed... For my batch that I intend to use the view with multiple day data, let say for the last 5 days.
Do not know how better to implement my sql with these suffixes _mon statement to make it more or less dynamic.
I create also ever seen from several tables, then, probably, that I can do something that will add daily updated data and remove data from 5 days?

You will appreciate comments on the details and the whole concept. I have prev sql server experience.

Thank you
T
user12943718 wrote:
Hello
I'll have existing oracle db with the daily stat data, tables strangely named data_mon, data_tue, data_wed... For my batch that I intend to use the view with multiple day data, let say for the last 5 days.
Do not know how better to implement my sql with these suffixes _mon statement to make it more or less dynamic.
I create also ever seen from several tables, then, probably, that I can do something that will add daily updated data and remove data from 5 days?

You will appreciate comments on the details and the whole concept. I have prev sql server experience.

Thank you
T

Change the data model if you have 1 table for a day.

You have just a DATA table and a column to indicate the day of the application.

Then you don't need a view, do not need anything dynamic, do not need to break your head against a wall for a simple query... etc.

create the list item

Hello
can you help me with creating a list item?
I wrote the following
{DECLARE
T1 RECORDGROUP;
A1 NUMBER;
BEGIN
Q1: = CREATE_GROUP_FROM_QUERY ("rg_name",
' select customer_id in
(: ctrl_orders.cust_phone customers);
clear_list ("ctrl_orders.cust_phone");
populate_list ('ctrl_orders.cust_phone', Q1);
end;
}

Sorry, I make a mistake.
You should not create group record in the node record group on your form.
Now, I copy a code:

declare
rg_name varchar2(40) :='xxx';
rg_id RecordGroup;
errcode NUMBER;
BEGIN
rg_id :=Find_Group( rg_name );
If Id_Null(rg_id) then
     rg_id :=Create_Group_From_Query( rg_name, 'select customer_id, customer_id from customers',FORM_SCOPE,200);
elsif not id_null(rg_id) then
     delete_group(rg_id);
     rg_id :=Create_Group_From_Query( rg_name, 'select customer_id, customer_id from customers',FORM_SCOPE,200);
end if;

errcode := populate_group_with_query(rg_id,'select customer_id, customer_id from customers');
clear_list('CTRL_ORDERS.CUST_PHONE');
populate_list('CTRL_ORDERS.CUST_PHONE', rg_name);

end;

hope it helps you,
Fabrizio

create the list-range partition table

Similar Questions

Maybe you are looking for