[Last Call] Learn about multicloud storage options and how to improve your company's cloud strategy. Register Now

Solved

Partitioning Indexes Question

Posted on 2012-12-22

Oracle Database

3 solutions

Medium Priority

1,672 Views

Last Modified: 2012-12-30

Trying to create this index partition

CREATE INDEX bb_bb60_stats.activity_accumulator_iecontent
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
CREATE INDEX bb_bb60_stats.activity_accumulator_iecontent
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL
(
PARTITION aa_2010_04 TABLESPACE BB_BB60_STATS_INDX,
PARTITION aa_2010_05 TABLESPACE BB_BB60_STATS_INDX,
PARTITION aa_2010_06 TABLESPACE BB_BB60_STATS_INDX,
PARTITION aa_2010_07 TABLESPACE BB_BB60_STATS_INDX,

Getting the message
"Index created.

PARTITION AA_2010_04 TABLESPACE BB_BB60_STATS_DATA
*
ERROR at line 5:
ORA-14010: this physical attribute may not be specified for an index partition
"
What attribute am I specifying that I should not?

Comment

Question by:xoxomos

[X]

Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

Help others & share knowledge
Earn cash & points
Learn & ask questions

Join The Community

13 Comments

LVL 23

Expert Comment

by:Steve Wales

ID: 387171832012-12-23

I don't claim to be an expert on partitioning, but it looks like you are creating the index twice with the same name ?

Oracle in general doesn't like two things of the same type in the database with the same name.

(Unless something about partitioning requires you to do it this way, but nothing I could find in the documentation suggested that)

Author Comment

by:xoxomos

ID: 387172112012-12-23

Thanks
That's what I thought also but when i removed the first SQL command and just ran the second, I got some kind of error. I'll run over that again now and come back with the error message. Did a search on it in mySupport, came back with basically 'returned no rows' on the Knowledge thing :-)

Author Comment

by:xoxomos

ID: 387172192012-12-23

I'll run this now:
DROP INDEX bb_bb60_stats.activity_accumulator_iecontent;
DROP INDEX bb_bb60_stats.activity_accumulator_ie1;
DROP INDEX bb_bb60_stats.activity_accumulator_ie2;
DROP INDEX bb_bb60_stats.activity_accumulator_ie3;
DROP INDEX bb_bb60_stats.activity_accumulator_ie4;
DROP INDEX bb_bb60_stats.activity_accumulator_ie5;
DROP INDEX bb_bb60_stats.activity_accumulator_ie6;
DROP INDEX bb_bb60_stats.activity_accumulator_pk1;
CREATE INDEX bb_bb60_stats.activity_accumulator_iecontent
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
COMMIT;
CREATE INDEX bb_bb60_stats.activity_accumulator_ie1
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
COMMIT;
CREATE INDEX bb_bb60_stats.activity_accumulator_ie1
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
COMMIT;
CREATE INDEX bb_bb60_stats.activity_accumulator_ie2
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
COMMIT;
CREATE INDEX bb_bb60_stats.activity_accumulator_ie2
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
COMMIT;
CREATE INDEX bb_bb60_stats.activity_accumulator_ie3
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
COMMIT;
CREATE INDEX bb_bb60_stats.activity_accumulator_ie3
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
COMMIT;
CREATE INDEX bb_bb60_stats.activity_accumulator_ie4
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
COMMIT;
CREATE INDEX bb_bb60_stats.activity_accumulator_ie4
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
COMMIT;
CREATE INDEX bb_bb60_stats.activity_accumulator_ie5
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
COMMIT;
CREATE INDEX bb_bb60_stats.activity_accumulator_ie5
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
COMMIT;
CREATE INDEX bb_bb60_stats.activity_accumulator_ie6
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
COMMIT;
CREATE INDEX bb_bb60_stats.activity_accumulator_ie6
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;
COMMIT;
CREATE INDEX bb_bb60_stats.activity_accumulator_pk1
.......................................................................;

Author Comment

by:xoxomos

ID: 387172332012-12-23

It's finished dropping whatever is there now starting the CREATE. That will run about fifty minutes, make a significant amount of noise on OEM's 'Performance' screen, the error out.

Author Comment

by:xoxomos

ID: 387173292012-12-23

ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL
*
ERROR at line 2:
ORA-01408: such column list already indexed.
When I issue the drop, it says index does not exist
When i issue the CREATE it says index does exist.

Author Comment

by:xoxomos

ID: 387173542012-12-23

SQL query show only one non system generated index.

SQL> select owner, index_name from dba_indexes where table_owner = 'BB_BB60_STATS'
2 and table_name = 'ACTIVITY_ACCUMULATOR';

OWNER INDEX_NAME
------------------------------ ------------------------------
BB_BB60_STATS ACTIVITY_ACCUMULATOR_IECONTENT
BB_BB60_STATS SYS_IL0000122326C00013$$

SQL>

LVL 23

Assisted Solution

by:Steve Wales

Steve Wales earned 400 total points

ID: 387173722012-12-23

It doesn't say that there is an index of that name, it says that those columns already exist in another index somewhere.

Does that table have a primary key ? If you add a primary key constraint it automatically builds an index.

Check the values in dba_ind_columns for that table as well as dba_constraints. Do you have a Primary Key (P) constraint using those columns ?

Author Comment

by:xoxomos

ID: 387173852012-12-23

Yes
ACTIVITY_ACCUMULATOR_IECONTENT is the index on the primary key.
For the moment I would leave that be and try creating one or more of the other indexes.

Author Comment

by:xoxomos

ID: 387173962012-12-23

SQL> select index_name, column_name from dba_ind_columns
2 where table_owner = 'BB_BB60_STATS'
3 and table_name = 'ACTIVITY_ACCUMULATOR';

INDEX_NAME
------------------------------
COLUMN_NAME
--------------------------------------------------------------------------------
ACTIVITY_ACCUMULATOR_IECONTENT
CONTENT_PK1

Author Comment

by:xoxomos

ID: 387177842012-12-23

SQL> select constraint_name from dba_constraints
2 where table_name = 'ACTIVITY+ACCUMULATOR'
3 and owner = 'BB_BB60_STATS';

no rows selected

SQL>

LVL 17

Accepted Solution

by:k_murli_krishna

k_murli_krishna earned 1600 total points

ID: 387202152012-12-25

All above can be explained in the following:

1) PK constraint is a rule that prohibits multiple rows from having the same value in the same column or combination of columns.

2) Oracle Database enforces a UNIQUE key or PRIMARY KEY integrity constraint on a table by creating a unique index on the unique key or primary key.

3) Thus, when your table ACTIVITY_ACCUMULATOR was created with primary key as CONTENT_PK1, a unique index is created by Oracle with same name as primary key constraint name

4) Your very first statement in your very first post:
CREATE INDEX bb_bb60_stats.activity_accumulator_iecontent
ON bb_bb60_stats.activity_accumulator (content_pk1) LOCAL;

This runs through since this is a duplicate index unlike the unique index created by Oracle to enforce uniqueness. Index with (same name in the same schema) OR (same type on the same set of coulmn(s) with matching sort specifiers i.e ASC or DESC) are not allowed.

Now you are trying to create an index partition but the top main part i.e. CREATE INDEX is exactly same as above. The error you are getting is not about index already exists but syntax error in creating index partition described as below:

ORA-14010:
this physical attribute may not be specified for an index partition
Cause: unexpected option was encountered while parsing physical attributes of an index partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE; only TABLESPACE may be specified for Hash partitions
Action: remove invalid option(s) from the list of physical attributes of an index partition

Please go through the following link on how to create table partitions and extending on that as how to create index partitions:

Partitioned Tables and Indexes
http://docs.oracle.com/cd/B10501_01/server.920/a96524/c12parti.htm

Assisted Solution

by:xoxomos

xoxomos earned 0 total points

ID: 387205012012-12-25

Thanks krishna, looks like you are right here. I've started creating indexes script again.

Author Closing Comment

by:xoxomos

ID: 387305732012-12-30

Thanks all.

Featured Post

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to use Access Control Lists in Oracle

Article by: sdstuber

Working with Network Access Control Lists in Oracle 11g (part 1) Part 2: http://www.e-e.com/A_9074.html So, you upgraded to a shiny new 11g database and all of a sudden every program that used UTL_MAIL, UTL_SMTP, UTL_TCP, UTL_HTTP or any oth…

Oracle Database

How to use Network Access Control Lists in Oracle

Article by: sdstuber

Working with Network Access Control Lists in Oracle 11g (part 2) Part 1: http://www.e-e.com/A_8429.html Previously, I introduced the basics of network ACL's including how to create, delete and modify entries to allow and deny access. For many…

Oracle Database

Executing a SQL Script from a Unix Shell Script and Passing Parameters

Video by: Steve

This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.