Composite range - range partitioning gives ORA-14202

i am trying to do e composite range - range partitioning, but the table is not created. i get an error, which i cannot look up at ora-codes, it says : value is to high for subpartition, which confuses me...
CREATE TABLE "NJ_VE_AERIAL_RDT"
(     "RASTERID" NUMBER NOT NULL ENABLE,
"BANDBLOCKNUMBER" NUMBER NOT NULL ENABLE,
     "PYRAMIDLEVEL" NUMBER NOT NULL ENABLE,
     "ROWBLOCKNUMBER" NUMBER NOT NULL ENABLE,
     "COLUMNBLOCKNUMBER" NUMBER NOT NULL ENABLE,
     "FILENAME" VARCHAR2(100 CHAR) NOT NULL ENABLE,
     "FILESIZE" NUMBER(12,0) NOT NULL ENABLE,
     "NORTH" NUMBER(19,15) NOT NULL ENABLE,
     "SOUTH" NUMBER(19,15) NOT NULL ENABLE,
     "EAST" NUMBER(19,15) NOT NULL ENABLE,
     "WEST" NUMBER(19,15) NOT NULL ENABLE,
     "BLOCKMBR" "MDSYS"."SDO_GEOMETRY" ,
     "RASTERBLOCK" BLOB,
     "INFO_CREATOR" VARCHAR2(100 BYTE) DEFAULT 'novalue' NOT NULL ENABLE,
     "INFO_CREATED" TIMESTAMP (6) WITH LOCAL TIME ZONE DEFAULT CURRENT_TIMESTAMP NOT NULL ENABLE,
     "INFO_LASTMODIFIER" VARCHAR2(100 CHAR) DEFAULT 'novalue' NOT NULL ENABLE,
     "INFO_LASTMODIEFIER" TIMESTAMP (6) WITH LOCAL TIME ZONE DEFAULT CURRENT_TIMESTAMP NOT NULL ENABLE,
     CONSTRAINT "NJ_VE_RDT_PK" PRIMARY KEY
("RASTERID"
,"BANDBLOCKNUMBER"
,"PYRAMIDLEVEL"
,"ROWBLOCKNUMBER"
,"COLUMNBLOCKNUMBER"))
PARTITION BY RANGE (WEST) INTERVAL (1)
SUBPARTION BY RANGE (NORTH)
SUBPARTITION TMEPLATE (
SUBPARTITION s0 VALUES LESS THAN (15)
,SUBPARTITION s0 VALUES LESS THAN (5)
(PARTITION p0 VALUES LESS THAN (0));
What is my problem ? My current solution is fully dropping subpartitioning. but thats a cheesy workaround...
ingo
Message was edited by:
Ingo Jannick

achso ?!
this works, but even switching the subpartition definitions results in the mentioned error. adding another sub does the same.
my guess is that it is a range by interval issue. i have to figure that out...
Working:
CREATE TABLE "NJ_VEL_RDT"
(     "RASTERID" NUMBER NOT NULL ENABLE,
"BANDBLOCKNUMBER" NUMBER NOT NULL ENABLE,
     "PYRAMIDLEVEL" NUMBER NOT NULL ENABLE,
     "ROWBLOCKNUMBER" NUMBER NOT NULL ENABLE,
     "COLUMNBLOCKNUMBER" NUMBER NOT NULL ENABLE,
     "FILENAME" VARCHAR2(100 CHAR) NOT NULL ENABLE,
     "FILESIZE" NUMBER(12,0) NOT NULL ENABLE,
     "NORTH" NUMBER(19,15) NOT NULL ENABLE,
     "SOUTH" NUMBER(19,15) NOT NULL ENABLE,
     "EAST" NUMBER(19,15) NOT NULL ENABLE,
     "WEST" NUMBER(19,15) NOT NULL ENABLE,
     "BLOCKMBR" "MDSYS"."SDO_GEOMETRY" ,
     "RASTERBLOCK" BLOB,
     "INFO_CREATOR" VARCHAR2(100 BYTE) DEFAULT 'novalue' NOT NULL ENABLE,
     "INFO_CREATED" TIMESTAMP (6) WITH LOCAL TIME ZONE DEFAULT CURRENT_TIMESTAMP NOT NULL ENABLE,
     "INFO_LASTMODIFIER" VARCHAR2(100 CHAR) DEFAULT 'novalue' NOT NULL ENABLE,
     "INFO_LASTMODIEFIER" TIMESTAMP (6) WITH LOCAL TIME ZONE DEFAULT CURRENT_TIMESTAMP NOT NULL ENABLE,
     CONSTRAINT "NJ_VE_PK" PRIMARY KEY
( "RASTERID",
"BANDBLOCKNUMBER",
"PYRAMIDLEVEL",
"ROWBLOCKNUMBER",
"COLUMNBLOCKNUMBER"))
PARTITION BY RANGE(WEST) INTERVAL (5)
SUBPARTITION BY RANGE(NORTH)
SUBPARTITION TEMPLATE
SUBPARTITION s1 VALUES LESS THAN (65)
,SUBPARTITION s0 VALUES LESS THAN (MAXVALUE)
(PARTITION p0 VALUES LESS THAN (15))
;

Similar Messages

Create local spatial index on range sub-partitions?

Is is possible to create a local spatial index on a table with range sub-partitions? We're trying to do this on a table that contains lots of x,y,z point data.
Trying to do so gives me the error: ORA-29846: cannot create a local domain index on a composite partitioned tableAccording to the spatial documentation:The following restrictions apply to spatial index partitioning:
- The partition key for spatial tables must be a scalar value, and must not be a spatial column.
- Only range partitioning is supported on the underlying table. All other kinds of partitioning are not currently
supported for partitioned spatial indexes.So there is nothing saying it can or can't be done. The examples I've seen in the documentation tend to partition based on a single value and don't use subpartitioning.
Example of what we're trying to do:SQL> SELECT * FROM V$VERSION;
BANNER
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
PL/SQL Release 11.1.0.7.0 - Production
CORE    11.1.0.7.0      Production
TNS for 64-bit Windows: Version 11.1.0.7.0 - Production
NLSRTL Version 11.1.0.7.0 - Production
SQL>
SQL> --- Create a table, partioned by X and subpartitioned by Y
SQL> CREATE TABLE sub_partition_test
2 (
3      x               NUMBER,
4      y               NUMBER,
5      z               NUMBER,
6      geometry        MDSYS.SDO_GEOMETRY
7 )
8 PARTITION BY RANGE (x)
9 SUBPARTITION BY RANGE (y)
10     (
11     PARTITION p_x100 VALUES LESS THAN (100)
12     (
13                     SUBPARTITION sp_x100_y100 VALUES LESS THAN (100),
14                     SUBPARTITION sp_x100_y200 VALUES LESS THAN (200),
15                     SUBPARTITION sp_x100_yMAXVALUE VALUES LESS THAN (MAXVALUE)
16     ),
17     PARTITION p_x200 VALUES LESS THAN (200)
18     (
19                     SUBPARTITION sp_x200_y100 VALUES LESS THAN (100),
20                     SUBPARTITION sp_x200_y200 VALUES LESS THAN (200),
21                     SUBPARTITION sp_x200_yMAXVALUE VALUES LESS THAN (MAXVALUE)
22     ),
23     PARTITION p_xMAXVALUE VALUES LESS THAN (MAXVALUE)
24     (
25                     SUBPARTITION sp_xMAXVALUE_y100 VALUES LESS THAN (100),
26                     SUBPARTITION sp_xMAXVALUE_y200 VALUES LESS THAN (200),
27                     SUBPARTITION sp_xMAXVALUE_yMAXVALUE VALUES LESS THAN (MAXVALUE)
28     )
29 );
Table created.
SQL>
SQL> -- Insert some sample data
SQL> INSERT INTO sub_partition_test (x, y, z, geometry)
2 VALUES (1, 1, 50, SDO_GEOMETRY(3001, 2157, SDO_POINT_TYPE(1, 1, 50), NULL, NULL));
1 row created.
SQL> INSERT INTO sub_partition_test (x, y, z, geometry)
2 VALUES (50, 150, 50, SDO_GEOMETRY(3001, 2157, SDO_POINT_TYPE(50, 150, 50), NULL, NULL));
1 row created.
SQL> INSERT INTO sub_partition_test (x, y, z, geometry)
2 VALUES (150, 150, 50, SDO_GEOMETRY(3001, 2157, SDO_POINT_TYPE(150, 150, 50), NULL, NULL));
1 row created.
SQL> INSERT INTO sub_partition_test (x, y, z, geometry)
2 VALUES (150, 250, 50, SDO_GEOMETRY(3001, 2157, SDO_POINT_TYPE(150, 250, 50), NULL, NULL));
1 row created.
SQL> INSERT INTO sub_partition_test (x, y, z, geometry)
2 VALUES (150, 300, 50, SDO_GEOMETRY(3001, 2157, SDO_POINT_TYPE(150, 300, 50), NULL, NULL));
1 row created.
SQL> INSERT INTO sub_partition_test (x, y, z, geometry)
2 VALUES (220, 210, 50, SDO_GEOMETRY(3001, 2157, SDO_POINT_TYPE(220, 210, 50), NULL, NULL));
1 row created.
SQL> INSERT INTO sub_partition_test (x, y, z, geometry)
2 VALUES (220, 150, 50, SDO_GEOMETRY(3001, 2157, SDO_POINT_TYPE(220, 150, 50), NULL, NULL));
1 row created.
SQL> INSERT INTO sub_partition_test (x, y, z, geometry)
2 VALUES (220, 250, 50, SDO_GEOMETRY(3001, 2157, SDO_POINT_TYPE(220, 250, 50), NULL, NULL));
1 row created.
SQL> INSERT INTO sub_partition_test (x, y, z, geometry)
2 VALUES (220, 300, 50, SDO_GEOMETRY(3001, 2157, SDO_POINT_TYPE(220, 300, 50), NULL, NULL));
1 row created.
SQL> INSERT INTO sub_partition_test (x, y, z, geometry)
2 VALUES (320, 250, 50, SDO_GEOMETRY(3001, 2157, SDO_POINT_TYPE(320, 250, 50), NULL, NULL));
1 row created.
SQL> INSERT INTO sub_partition_test (x, y, z, geometry)
2 VALUES (320, 160, 50, SDO_GEOMETRY(3001, 2157, SDO_POINT_TYPE(320, 160, 50), NULL, NULL));
1 row created.
SQL> INSERT INTO sub_partition_test (x, y, z, geometry)
2 VALUES (320, 290, 50, SDO_GEOMETRY(3001, 2157, SDO_POINT_TYPE(320, 290, 50), NULL, NULL));
1 row created.
SQL> INSERT INTO sub_partition_test (x, y, z, geometry)
2 VALUES (320, 320, 50, SDO_GEOMETRY(3001, 2157, SDO_POINT_TYPE(320, 320, 50), NULL, NULL));
1 row created.
SQL>
SQL> -- Create some metadata
SQL> DELETE FROM user_sdo_geom_metadata WHERE TABLE_NAME = 'SUB_PARTITION_TEST';
1 row deleted.
SQL> INSERT INTO user_sdo_geom_metadata VALUES ('SUB_PARTITION_TEST','GEOMETRY',
2 SDO_DIM_ARRAY(
3     SDO_DIM_ELEMENT('X', 0, 1000, 0.005),
4     SDO_DIM_ELEMENT('Y', 0, 1000, 0.005)
5 ), 262152);
1 row created.
SQL>
SQL> -- Create an Unusable Local Spatial Index
SQL> CREATE INDEX sub_partition_test_spidx ON sub_partition_test (geometry)
2    INDEXTYPE IS MDSYS.SPATIAL_INDEX
3 LOCAL
4 UNUSABLE;
CREATE INDEX sub_partition_test_spidx ON sub_partition_test (geometry)
ERROR at line 1:
ORA-29846: cannot create a local domain index on a composite partitioned tableThanks,
John

Ok, thanks. That's what we're planning on doing now.
SQL> CREATE TABLE partition_test
2 (
3      x               NUMBER,
4      y               NUMBER,
5      z               NUMBER,
6      geometry        MDSYS.SDO_GEOMETRY
7 )
8 PARTITION BY RANGE (x, y)
9     (
10     PARTITION p_x100y100 VALUES LESS THAN (100, 100),
11     PARTITION p_x100y200 VALUES LESS THAN (100, 200),
12     PARTITION p_x100yMAX VALUES LESS THAN (100, MAXVALUE),
13     PARTITION p_x200y100 VALUES LESS THAN (200, 100),
14     PARTITION p_x200y200 VALUES LESS THAN (200, 200),
15     PARTITION p_x200yMAX VALUES LESS THAN (200, MAXVALUE),
16     PARTITION p_x300y100 VALUES LESS THAN (300, 100),
17     PARTITION p_x300y200 VALUES LESS THAN (300, 200),
18     PARTITION p_x300yMAX VALUES LESS THAN (MAXVALUE, MAXVALUE)
19 );
Table created.
SQL>
SQL> INSERT INTO user_sdo_geom_metadata VALUES ('PARTITION_TEST','GEOMETRY',
2     SDO_DIM_ARRAY(
3        SDO_DIM_ELEMENT('X', 0, 1000, 0.005),
4        SDO_DIM_ELEMENT('Y', 0, 1000, 0.005)
5     ), 262152);
1 row created.
SQL> CREATE INDEX partition_test_spidx ON partition_test (geometry)
2     INDEXTYPE IS MDSYS.SPATIAL_INDEX
3 LOCAL
4 UNUSABLE;
Index created.

Range interval partitioning

Hi,
Using Oracle 11.20.3
We wish to have a range-hash composite partitioned table, one partition for each month.
However, want to esnure are always a partition tehrfore would like to use range interval partitioning.
Have a few questions, if have partition say 201301 to 201312 but get somew rosw which have value in date in June 2014 would it create
a new partition for each month i.e 201401, 201402 etc or just one for 201406?
Wanyt esnure system can cope automatically with following scenario
Daty1 have partitions 201301 to 201312
Day2 get record for 201406 (June 2014)
Day 3 get record for 201403 (March 2014)
We have no control of the range of dates we could get but don't want tpo have to manually create partitions fro all tehse dates in advance - want system to handled it automatically.
Also can you simply rename the system generated partition names to something more meaningful later.

>
Using Oracle 11.20.3
We wish to have a range-hash composite partitioned table, one partition for each month.
However, want to esnure are always a partition tehrfore would like to use range interval partitioning.
Have a few questions, if have partition say 201301 to 201312 but get somew rosw which have value in date in June 2014 would it create
a new partition for each month i.e 201401, 201402 etc or just one for 201406?
Wanyt esnure system can cope automatically with following scenario
Daty1 have partitions 201301 to 201312
Day2 get record for 201406 (June 2014)
Day 3 get record for 201403 (March 2014)
We have no control of the range of dates we could get but don't want tpo have to manually create partitions fro all tehse dates in advance - want system to handled it automatically.
>
Do NOT be afraid of breaking Oracle by actually trying things yourself.
DROP TABLE emp_part
CREATE TABLE emp_part (empno number(4), ename varchar2(10),
deptno number(2), created_date DATE default sysdate)
partition by range (created_date)
SUBPARTITION BY HASH(deptno) subpartitions 4
( partition p_prior_to_2014 values less than (to_date('01-01-2014', 'mm-dd-yyyy')));Add some data for 2014 and see for yourself what happens.
>
Also can you simply rename the system generated partition names to something more meaningful later.
>
Yes - assuming you mean more meaninful to a human. Oracle doesn't care what the name is.
And you can just as easily manipulate the partition (delete, insert, drop truncate) regardless of the name since you don't need to use the name to do those things.
You either know the date for the partition you want to work with or you don't. If you know then just tell Oracle and it will work with the correct partition. If you don't believe me try it with the sample code I gave you. Add some data to get a couple of interval partitions created and then drop one of them using Oracle's extended partition syntax. See this example in the 'Dropping Interval Partitions in the VLDB and Partitioning Guide
http://docs.oracle.com/cd/B28359_01/server.111/b32024/part_admin.htm#i1007479
>
The following example drops the September 2007 interval partition from the sales table. There are only local indexes so no indexes will be invalidated.
ALTER TABLE sales DROP PARTITION FOR(TO_DATE('01-SEP-2007','dd-MON-yyyy'));
>
That code doesn't require the partition name. You just need to specify a date that falls IN the partition that you want to drop. You have to do that whether you know the name of the partition or not. Don't 'gunk up' your system with code to rename things unless there is some real need to.

Range interval partitioning with null value

Hello,
I have question, how can I create table with partition and after that I will insert null value in the partition key like this kind of
range interval partitioning with null value.
I have Oracle 11g.
Thanks
Mohammed

user13777053 wrote:
Thank you, but my question is about range interval not for range?http://docs.oracle.com/cd/E11882_01/server.112/e25523/partition.htm#VLDBG00220
A MAXVALUE literal can be defined for the highest partition. MAXVALUE represents a virtual infinite value that sorts higher than any other possible value for the partitioning key, *including the NULL value.*
So since you're trying to partition by interval (which doesn't support a MAXVALUE clause) you're out of luck.
There's probably fancy hacks and what not you could try to implement, but i'm not about to recommend any of those here :)
Cheers,

Range - Interval Partition and List Subpartition.

Hi
I am trying to create the Range(Interval) Partition with List Sub partition (dynamically). Here the LOCATION_CD List is Dynamic. Basically Location_CD is Country name. e.g USA, IND,GER.....
Below Works good...
CREATE TABLE TEMP
SEQUENCE_ID NUMBER,
RESERVATION_DATE TIMESTAMP,
LOCATION_CD VARCHAR2(5)
PARTITION BY RANGE (RESERVATION_DATE)
INTERVAL (NUMTOYMINTERVAL(1,'MONTH'))
SUBPARTITION BY LIST(LOCATION_CD)
SUBPARTITION TEMPLATE
( SUBPARTITION CD_01 VALUES ('USA'),
SUBPARTITION CD_02 VALUES ('IND'),
SUBPARTITION CD_03 VALUES ('GER')
PARTITION TEMP values LESS THAN (TO_DATE('01-JAN-2000','DD-MON-YYYY'))
Today there are 3 Countries but going forward it can be more or less.
I like the Interval Range Partition concept, where the new partition is automatically gets added.
But at the same time can the new list sub partition be added ? If this doesn't work...can we have another alternative approach or partition technique ?
Please suggest.
Thanks
Jitesh R.

Why didn't you just perform two inserts and answer the question yourself?
orabase> CREATE TABLE T (
2 SEQUENCE_ID      NUMBER,
3 RESERVATION_DATE TIMESTAMP,
4 LOCATION_CD      VARCHAR2(5))
5 PARTITION BY RANGE (RESERVATION_DATE)
6 INTERVAL (NUMTOYMINTERVAL(1,'MONTH'))
7 SUBPARTITION BY LIST(LOCATION_CD)
8 SUBPARTITION TEMPLATE (
9 SUBPARTITION CD_01 VALUES ('USA'),
10 SUBPARTITION CD_02 VALUES ('IND'),
11 SUBPARTITION CD_03 VALUES ('GER')) (
12 PARTITION root values LESS THAN (TO_DATE('01-JAN-2000','DD-MON-YYYY')));
Table created.
orabase> insert into t values (1, TO_DATE('02-JAN-2000'), 'USA');
1 row created.
orabase> select partition_name, subpartition_name
2 from user_tab_subpartitions
3 where table_name = 'T';
PARTITION_NAME                 SUBPARTITION_NAME
ROOT                           ROOT_CD_03
ROOT                           ROOT_CD_02
ROOT                           ROOT_CD_01
SYS_P84                        SYS_SUBP83
SYS_P84                        SYS_SUBP82
SYS_P84                        SYS_SUBP81
6 rows selected.
orabase> insert into t values (1, TO_DATE('02-JAN-2000')+400, 'USA');
1 row created.
orabase> select partition_name, subpartition_name
2 from user_tab_subpartitions
3 where table_name = 'T';
PARTITION_NAME                 SUBPARTITION_NAME
SYS_P88                        SYS_SUBP85
SYS_P88                        SYS_SUBP86
SYS_P88                        SYS_SUBP87
SYS_P84                        SYS_SUBP81
SYS_P84                        SYS_SUBP82
SYS_P84                        SYS_SUBP83
ROOT                           ROOT_CD_01
ROOT                           ROOT_CD_02
ROOT                           ROOT_CD_03
9 rows selected.

Range interval partitioning - ability to set tablespace?

Hi,
We have a range partitioned table, considering making it a range-interval partitioned one.
I know can query/identify partitions by using syntax to the range to which the partition relates.
If set to range interval, wht tablespace are new ones created in, is it the default tablespace of the database or can you ensure they are automatcially created in specific tablespace.
Is there any way of setting name to be something more meaninful automatically rather than having to write sql to query data dictionary to do this?
Many Thanks

There are no undocumented features in Oracle.
What did the documentation tell, apart from it isn't possible?
Sybrand Bakker
Senior Oracle DBA

Why don't be used composite index in partition table.

A table has done range list partition.
Then, I create a composite index named INDEX_N2(COLUMN_005, COLUMN_002). --COLUMN_005 AND COLUMN_002 ARE VARCHAR2
When I run the SQL
select 1
from table1 T1
where T1.COLUMN_005 = 'x'
and T1.COLUMN_002 = 'y'
And view the explain plan, INDEX_N2 has been used.
But when I join the COLUMN_005 to other column, the index will not be used.
The SQL is like below.
select 1
from table1 T1, table T2
where T1.COLUMN_005 = T2.COLUMN_002 --T2.COLUMN_002 IS VARCHAR2
and T1.COLUMN_002 = 'y'
The explain plan is like below
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | Pstart| Pstop |
| 0 | SELECT STATEMENT | | 426 | 44730 | 65367 (1)| 00:13:05 | | |
|* 1 | HASH JOIN | | 426 | 44730 | 65367 (1)| 00:13:05 | | |
| 2 | PARTITION RANGE ALL| | 8 | 792 | 5 (0)| 00:00:01 | 1 | 32 |
| 3 | PARTITION LIST ALL| | 8 | 792 | 5 (0)| 00:00:01 | 1 | 8 |
|* 4 | TABLE ACCESS FULL| TABLE1 | 8 | 792 | 5 (0)| 00:00:01 | 1 | 256 |
| 5 | PARTITION RANGE ALL| | 1112K| 6519K| 65355 (1)| 00:13:05 | 1 | 34 |
| 6 | PARTITION LIST ALL| | 1112K| 6519K| 65355 (1)| 00:13:05 | 1 | LAST |
| 7 | TABLE ACCESS FULL| TABLE2 | 1112K| 6519K| 65355 (1)| 00:13:05 | 1 | 442 |
Query Block Name / Object Alias (identified by operation id):
1 - SEL$1
4 - SEL$1 / T1@SEL$1
7 - SEL$1 / T2@SEL$1
Predicate Information (identified by operation id):
1 - access("T1"."COLUMN_005"="T2"."COLUMN_002")
4 - filter("T1"."COLUMN_002"='y')
Column Projection Information (identified by operation id):
1 - (#keys=1)
2 - "T1"."COLUMN_005"[VARCHAR2,150]
3 - "T1"."COLUMN_005"[VARCHAR2,150]
4 - "T1"."COLUMN_005"[VARCHAR2,150]
5 - "T2"."COLUMN_002"[VARCHAR2,20]
6 - "T2"."COLUMN_002"[VARCHAR2,20]
7 - "T2"."COLUMN_002"[VARCHAR2,20]
Note
- dynamic sampling used for this statement
My Questin is:
Two columns are include the columns of index.
Why it can't be used?
Thanks

I create a new index on column2, (INDEX_N3)
and change SQL to
select 1 from table T1 where
T1.COLUMN_002 = '848K 36892'
This time INDEX_N3 will be used.
but change SQL to
select 1 from table T1 where
T1.COLUMN_002 = '848K 36892'
and T1.COLUMN_004 = '1000'
The explain plan will show full scan.
Why？
Thanks.

PRIMARY KEY PARTITIONED INDEXES 생성방법 (ORA-2429, ORA-1408)

제품 : ORACLE SERVER
작성날짜 : 2004-08-13
PRIMARY KEY PARTITIONED INDEXES 생성방법 (ORA-2429, ORA-1408)
============================================================
PURPOSE
primary key partitioned indexes 를 생성하는 방법을 알아 봅니다.
SCOPE
Oracle Partitioning Option은 8~10g Standard Edition에서는 지원하지
않는다.
Example:
SQL> -- 먼저 partitioned table TEST_A 를 생성합니다.
SQL>
SQL> CREATE TABLE test_a (col1 number, col2 number, col3 varchar2(20))
2 PARTITION BY RANGE (col1, col2)
3 (partition part_test_a_1 values less than (10, 100),
4 partition part_test_a_2 values less than (20, 200),
5 partition part_test_a_3 values less than (30, 300),
6 partition part_test_a_4 values less than (40, 400));
Table created.
SQL> -- partitioned table TEST_B 를 생성합니다.
SQL>
SQL> CREATE TABLE test_b (col1 number, col2 number, col3 varchar2(20))
2 PARTITION BY RANGE (col1, col2)
3 (partition part_test_b_1 values less than (10, 100),
4 partition part_test_b_2 values less than (20, 200),
5 partition part_test_b_3 values less than (30, 300),
6 partition part_test_b_4 values less than (40, 400));
Table created.
SQL> -- TEST_A 테이블에
SQL> -- non-unique local partitioned index, IX_TEST_A 를 생성합니다.
SQL>
SQL> CREATE INDEX ix_test_a ON test_a(col1, col2)
2 LOCAL
3 (partition ix_test_a_1,
4 partition ix_test_a_2,
5 partition ix_test_a_3,
6 partition ix_test_a_4);
Index created.
SQL> -- TEST_B 테이블에
SQL> -- unique global partitioned index, IX_TEST_B 를 생성합니다.
SQL>
SQL> CREATE UNIQUE INDEX ix_test_b1 ON test_b(col1, col2)
2 GLOBAL PARTITION BY RANGE (col1, col2)
3 (partition ix_test_b1_1 values less than (20, 200),
4 partition ix_test_b1_2 values less than (maxvalue, maxvalue));
Index created.
SQL> -- TEST_A 테이블에 rimary key constraint (PK_TEST_A) 를 추가 합니다.
SQL>
SQL> ALTER TABLE test_a ADD CONSTRAINT pk_test_a
2 PRIMARY KEY (col2, col1);
Table altered.
SQL> -- index IX_TEST_A 를 drop 하려고 하면 다음 에러가 발생합니다.
SQL>
SQL> DROP INDEX ix_test_a;
drop index ix_test_a
ERROR at line 1:
ORA-02429: cannot drop index used for enforcement of unique/primary key
SQL> -- TEST_B 테이블에 partition IX_TEST_B1 에서 사용된 같은 columns 들을 사용해서
SQL> -- 새로운 두번째 index (IX_TEST_B2) 를 생성하려고 하면
SQL> -- 다음 에러가 발생합니다.
SQL>
SQL> CREATE INDEX ix_test_b2 ON test_b(col1, col2)
2 LOCAL;
create index ix_test_b2 on test_b(col1, col2)
ERROR at line 1:
ORA-01408: such column list already indexed
SQL> -- TEST_B 테이블에 primary key constraint (PK_TEST_B) 를 추가 합니다.
SQL>
SQL> ALTER TABLE test_b ADD CONSTRAINT pk_test_b
2 PRIMARY KEY (col1, col2);
Table altered.
SQL> -- index IX_TEST_B1 를 drop 하려고 하면 다음 에러가 발생합니다.
SQL>
SQL> DROP INDEX ix_test_b1;
drop index ix_test_b1
ERROR at line 1:
ORA-02429: cannot drop index used for enforcement of unique/primary key
SQL> -- indexes 들과 각 indexes 이 걸려있는 tables 의 목록입니다.
SQL>
SQL> SELECT index_name, partition_name, status
2 FROM user_ind_partitions
3 ORDER BY index_name, partition_name;
INDEX_NAME PARTITION_NAME STATUS
IX_TEST_A IX_TEST_A_1 USABLE
IX_TEST_A IX_TEST_A_2 USABLE
IX_TEST_A IX_TEST_A_3 USABLE
IX_TEST_A IX_TEST_A_4 USABLE
IX_TEST_B1 IX_TEST_B1_1 USABLE
IX_TEST_B1 IX_TEST_B1_2 USABLE
6 rows selected.
SQL> -- TEST_A 테이블에서 primary key constraint 를 drop 합니다.
SQL>
SQL> ALTER TABLE test_a DROP CONSTRAINT pk_test_a;
Table altered.
SQL> -- TEST_B 테이블에서 primary key constraint 를 drop 합니다.
SQL>
SQL> ALTER TABLE test_b DROP CONSTRAINT pk_test_b;
Table altered.
SQL> -- indexes 들과 각 indexes 이 걸려있는 tables 의 목록을 다시 봅니다.
SQL> -- 여기서 주의해서 보아야 할 것은 non-unique local partitioned index (IX_TEST_A)
SQL> -- 은 drop 되지 않고 USABLE 상태로 남아 있다는 것입니다.
SQL> -- 이렇게 되는 이유는 index (IX_TEST_A) 가 non-unique 이기 때문입니다.
SQL> -- 반면 unique global partitioned index (IX_TEST_B) 은 drop 되었습니다.
SQL>
SQL> SELECT index_name, partition_name, status
2 FROM user_ind_partitions
3 ORDER BY index_name, partition_name;
INDEX_NAME PARTITION_NAME STATUS
IX_TEST_A IX_TEST_A_1 USABLE
IX_TEST_A IX_TEST_A_2 USABLE
IX_TEST_A IX_TEST_A_3 USABLE
IX_TEST_A IX_TEST_A_4 USABLE
만일 index 가 primary key 에 정의되어 있는 columns 들과 같은 columns
을 사용해서 만들어 졌다면 primary key 는 그 underlying index 를 사용합니다.
이것은 index 가 unique 이건 non-unique 이건 또는 global 이건 local partioned index
이건 관계없이 적용됩니다.
위의 예제에서 primary key 가 non-unique index 위에 생성되었다는 것을
주의해 보시기 바랍니다. 이렇게 되는 이유는 index 안의 값들이 사실
모두 unique 하기 때문입니다. 그렇지 않을 경우 다음 에러가 발생하게 됩니다.
"ORA-02437: cannot enable (STEELY.PK_TEST_B) - primary key violated."
2개의 indexes 가 같은 순서의 같은 columns 을 사용해서 만들어 질 수는 없습니다.
위의 예제에서 TEST_B 테이블에 두번째 index (IX_TEST_B2) 를 만들려고
했을때 다음에러가 발생하는것을 확인할 수 있었습니다.
"ORA-01408: such column list already indexed."
하지만 columns 들의 순서를 바꾼다면 같은 columns 들을 사용하더라도
추가적으로 indexes 를 생성할 수 있습니다.
index (IX_TEST_A) 와 primary key (PK_TEST_A) 에 정의된 column 순서는
반대로 되어 있습니다. 그러나 primary key 는 IX_TEST_A 를 underlying index
로 사용하고 있습니다.
테이블에서 primary key constraint 가 drop 되었을때
만일 index 가 UNIQUE index 로 생성되었다면 대응하는 index 또한 drop 됩니다.
이 현상은 LOCAL 또는 GLOBAL partitioned indexes 모두에 적용됩니다.
partitioning 을 최대한 활용하기 위해서는 partitioned tables/indexes
를 생성할 때에 STORAGE clause 를 반드시 사용해야 합니다.
Reference Documents
<Note:74224.1>

First, thanks for posting the code that lets us reproduce your test. That is essential for issues like this.
Because the primary key is global you will not be able to use
INCLUDING INDEXES
WITH VALIDATION;And you will need to add the primary key to the temp table
ALTER TABLE DEMO_INTERVAL_DATA_LOAD_Y ADD CONSTRAINT IDX_DEMO_ROLL_Y PRIMARY KEY (ROLL_NUM);The the exchange will work. You will need to rebuild the primary key after the exchange.

9.0.1: select on dba_users as sys gives ORA-03106

Hi,
Select username from dba_users logged as sys gives
ORA-03106: fatal two-task communication protocal error.
Install done from zipped OTN files, server 9.0.1, OS Linux SuSe 7.2. Character set UTF8. Is UTF8 incompatible with 9i?
Any treatment ideas are greatly appreciated.
Thanks
Anatoliy Smirnov

resolved
thanks

Gives ORA-12560: TNS: protocol adapter error when installing oracle 10g

I tried to install oracle 10g r2 in server 2008. but it gives ORA-12560: TNS: protocol adapter error when installing. how I can fix this issue??? please help me ASAP. because its urgent.
thanks in advance.
chamara

Welcome to the forums !
Pl indicate which version of 10g you are installing and on which version of Win 2008. Neither 10gR1 nor 10gR2 are certified to be installed on Win 2008 R1, AFAIK.
For 10gR2, only 10.2.0.5 is certified for Win 2008 R2 - see MOS Doc 1173433.1 (How to Install Oracle 10.2.0.5 on MS Windows 7 / Windows 2008R2)
Also see MOS Doc 740926.1 (Where can I find the Database / Client software to download for Microsoft Vista, or Windows 2008R1?).
Both 10gR1 and 10gR2 are now in extended support - is there a reason you are not using 11gR2 ?
HTH
Srini

Fine Grain Access Control gives ORA-02014

Using Fine Grain Access Control on Oracle 8i 8.1.6, when a policy is enabled on a table then queries of the form "select * from table for update nowait" give "ORA-02014 cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc.".
Similar queries without the "for update nowait" work OK.
Does anyone have a fix or workaround?
null

I ran into this. If you're using a function to add to/add a where clause to your statement, when the where clause gets appended to the end and generates an error. You should be seeing trace files in the udump area of oracle that show you the actual sql line that is being created in error. I modified my function to add the FOR UPDATE NOWAIT in the correct place.

Range interavl partitioned table not being created in compressed format

Hi,
Using oracle 11.2.03. and trying to create a table with compress
Normal table fine but trying syntax below but tabel properties show no compression
Tried compress at top of sql as per belwo and at bottom
Aldso tried compress and compress for oltp - same bahviour not getting compressed.
nOW HSOING AT TABLE LEVEL OR ON TABLE PORPETIES BUT WHEN check user_tab_partitions shows as compressed for oltp
Thanks
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 = 1441336376Edited by: user5716448 on 26-Mar-2013 07:16

>
Normal table fine but trying syntax below but tabel properties show no compression
>
What properties? You didn't show any query or result that shows if the table is compressed or not.
>
nOW HSOING AT TABLE LEVEL OR ON TABLE PORPETIES BUT WHEN check user_tab_partitions shows as compressed for oltp
>
I have no idea what any of that means.
Again - you didn't post anything showing 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 using code tags and posting some of the DDL needed but you should edit your post and REMOVE all of the extra partition definitions since all they do is bloat the listing.
This works for me in vanilla 11.2.0.1.0
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

Upgrade 11.1.0.7 to 11.2.0.3 gives ora-1403,ora-6512

We are upgrading the databse from 11.1.0.7 to 11.2.0.3 on hpux ia 64 using manual upgrade.
We ran catupgrade.sql and after that utu112.sql.
However the utu112.sql gives the following status->
@utlu112s.sql
.Oracle Database 11.2 Post-Upgrade Status Tool 03-30-2013 01:53:44
Component Current Version Elapsed Time
Name Status Number HH:MM:SS
Oracle Server
. ORA-01403: no data found
. ORA-06512: at line 5
. ORA-06512: at line 5
. ORA-01403: no data found
. VALID 11.2.0.3.0 00:35:25
JServer JAVA Virtual Machine
. VALID 11.2.0.3.0 00:04:23
Oracle XML Database
. VALID 11.2.0.3.0 00:04:56
Oracle Database Java Packages
. VALID 11.2.0.3.0 00:00:18
Gathering Statistics
. 00:12:34
Total Upgrade Time: 00:57:39
PL/SQL procedure successfully completed.
Also, when we did select from dba_registry it gave all components as valid
Oracle Database Catalog Views VALID 11.2.0.3.0
Oracle Database Packages and Types VALID 11.2.0.3.0
JServer JAVA Virtual Machine VALID 11.2.0.3.0
Oracle Database Java Packages VALID 11.2.0.3.0
Oracle XML Database VALID 11.2.0.3.0
I want to know, should i consider the database upgrade as sucess ot what to do next.
The upgrade log also shows same error- grep "^ORA-" upgrade11gR2.log
ORA-01403: no data found
ORA-06512: at line 5
ORA-01403: no data found
ORA-06512: at line 5
Thanks in advance!!

Pl post a link to the instructions you followed, along with all of the errors from the actual upgrade log file. Is there a reason for not using DBUA ? Have you opened an SR for this issue ?
HTH
Srini

Database give ORA-600 error after cold backup

HI,
I have oracle 10g install on linux system. i take cold backup of my database using
sql> shutdown immediate
and then copy all files to any other location.
but when i start my database it gives me error like
Errors in file /opt/oracle/fina/bdump/fina_smon_4422.trc:
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [4193], [136], [139], [], [], [], [], []
Fri Dec 4 15:23:18 2009
Errors in file /opt/oracle/fina/bdump/fina_smon_4422.trc:
ORA-00600: internal error code, arguments: [4193], [67], [70], [], [], [], [], []
Fri Dec 4 15:23:19 2009
Doing block recovery for file 2 block 1702
Block recovery from logseq 13, block 3531 to scn 758385
Fri Dec 4 15:23:19 2009
Recovery of Online Redo Log: Thread 1 Group 1 Seq 13 Reading mem 0
Mem# 0 errs 0: /opt/oracle/fina/dbs/redo01.log
Block recovery completed at rba 13.3532.16, scn 0.758386
Doing block recovery for file 2 block 153
Block recovery from logseq 13, block 3531 to scn 758436
Fri Dec 4 15:23:19 2009
Recovery of Online Redo Log: Thread 1 Group 1 Seq 13 Reading mem 0
Mem# 0 errs 0: /opt/oracle/fina/dbs/redo01.log
Block recovery completed at rba 13.3612.16, scn 0.758437
Fri Dec 4 15:23:19 2009
Errors in file /opt/oracle/fina/bdump/fina_smon_4422.trc:
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [4193], [67], [70], [], [], [], [], []
Fri Dec 4 15:23:29 2009
Errors in file /opt/oracle/fina/bdump/fina_smon_4422.trc:
ORA-00600: internal error code, arguments: [4193], [136], [139], [], [], [], [], []
Fri Dec 4 15:23:29 2009
Errors in file /opt/oracle/fina/bdump/fina_pmon_4410.trc:
ORA-00474: SMON process terminated with error
Fri Dec 4 15:23:29 2009
PMON: terminating instance due to error 474
Instance terminated by PMON, pid = 4410i have seen this happen sometime after cold backup database give errors. is taking cold backup of database is not safe.
Please suggest.

Umesh,
Since it is case of Ora 600, for which only last solution is oracle support, but i would like to mention that your are getting ORA-00600: internal error code, arguments: [4193].... So, this 4193 is cause to read following links too:
http://www.orafaq.com/forum/t/47048/2/ and. see Metalink note 153788.1 and 39282.1.
Regards
Girish Sharma

Alter system kill session always gives ORA-00030

Hello
Im writing a tool for oracle and one of its features requires killing user session (Im connecting with JDBC). The database Im testing on is 11.2.0.2.
I find the sid and the serial# without problems, than I issue the "alter system kill session 'x,y' immediate" command.
So far so good, but I always get an ORA-00030 error saying this session cannot be found.
I double check and the session does exist in the database.
Because I want the tool to make the kill, killing via the OS is not an option.
Its doesn't look like a permission problem because it gives the same error even when connected as system.
Whats wrong ? does this kill command work at all ? Whats its limitations ?
Thanks
Guy Shilo
Edited by: user13266377 on Jun 9, 2011 1:15 AM

user13266377 wrote:
Hello
Im writing a tool for oracle and one of its features requires killing user session (Im connecting with JDBC). The database Im testing on is 11.2.0.2.
I find the sid and the serial# without problems, than I issue the "alter system kill session 'x,y' immediate" command.
So far so good, but I always get an ORA-00030 error saying this session cannot be found.
I double check and the session does exist in the database.
Because I want the tool to make the kill, killing via the OS is not an option.
Its doesn't look like a permission problem because it gives the same error even when connected as system.
Whats wrong ? does this kill command work at all ? Whats its limitations ?
Thanks
Guy Shilo
Edited by: user13266377 on Jun 9, 2011 1:15 AMyou cannot kill the session already killed or disconnected from the session.
refer the link:- this may help you to write scripts to kill session using dbms_scheduler
Grant restricted and kill sessions.

Composite range - range partitioning gives ORA-14202

Similar Messages

Maybe you are looking for