Partition of such index is in unusable state

Hi,
We have upgraded the system 3O.B to BI 7.0 after upgrade we are getting following dump in the system for cube while accessing
Database error text........: "ORA-01502: index 'SAPPRW./BIC/FZUCCA_C1~100' or partition of such index is in unusable state"
How to rebuild the signal index in BI ?

Hi,
I am getting a similar dump for some master data. Have you managed to solve the problem? I have process chain, and everything seems to work correctly, but the system administrator informs us that we are getting system dumps.
Please inform how to solve the problem.
Thank you for your help.
Ravi
e.g.
ORA-01502: index 'SAPSR3./BIC/B0000521000KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000539000KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000546000KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000563000KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000569000KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000689000KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000691000KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000696000KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000697000KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000701000KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000703001KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000715000KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000828001KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000856000KE' or partition of such index is in unusable state
ORA-01502: index 'SAPSR3./BIC/B0000872000KE' or partition of such index is in unusable state

Similar Messages

How to fix ORA-01502: index or partition of such index is in usable state?

Greetings,
I received the ORA-01502: index or partition of such index is in un-usable state from one of our Oracle forms, and the problem was caused by using SQL Loader w/ the "DIRECT" load option. As a result of that, the system won't allow any updates including insert/delete to the problematic table w/ the index in un-usable state. I am trying to fix the problem but so far no luck:
When I tried to delete the duplicate rows from the table, I received the ORA-01502: index or partition of such index is in un-usable state error message;
When I tried to rebuild the index by using the following command:
ALTER INDEX index_name REBUILD
I received the "ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
Any help, suggestions or advice on this would be greatly appreciated.
Thanks millions in advance!

The duplicate key rows were inserted to the database by using the DIRECT parameter of the sql loader to specify direct path loading which bypasses integrity constraints. Since the issue exists in our production database and I am primarily an A/P w/ some responsibilities of DBA , I could really use your help to fix our production problem. I would really appreciate if you or any other guru could review my plan and code below for the fixes followed w/ some questions and give me your feedback/comments/suggestions as soon as possible:
1 - Drop the offending index by using the following command:
DROP INDEX <offending index name>
2 - Run the following script to detect duplicate rows:
SELECT *
FROM <Table_Name> A
WHERE
A.rowid >
any(SELECT B.rowid FROM <Table_Name> B
WHERE
B.KEY1 = A.KEY1
and
B.KEY2 = A.KEY2
and
B.KEY3 = A.KEY3
and
B.KEY4 = A.KEY4
3. Run the following script to remove the duplicates:
DELETE
FROM <Table_Name> A
WHERE
A.rowid >
any(SELECT B.rowid FROM <Table_Name> B
WHERE
B.KEY1 = A.KEY1
and
B.KEY2 = A.KEY2
and
B.KEY3 = A.KEY3
and
B.KEY4 = A.KEY4
4 - Rebuild the index by using the following line command:
ALTER INDEX index_name REBUILDBut wait, how about data? Don't I need to back up and reload the data? Do I need to drop and recreate the table? Anything else I should be taking into considerations?
p.s. Although, we only have a total of 35,736 rows of data from this table, but I want to make sure I do it right the first time.
Thanks a lot and any/all the help!

Error in Update optimizer statistics - index is in unusable state

Hello,
we have this error in log Check and update optimizer statistics:
12.02.2009     23:21:20     'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPPB1"', TABNAME => '"/BIC/FZPPC0002"', ESTIMATE_PERCENT => 10, METHOD_OPT =
12.02.2009     23:21:20     ORA-20000: index "SAPPB1"."/BIC/FZPPC0002~010" or partition of such index is in unusable state
12.02.2009     23:21:20     ORA-06512: at "SYS.DBMS_STATS", line 13452
12.02.2009     23:21:20     ORA-06512: at "SYS.DBMS_STATS", line 13472
12.02.2009     23:21:20     ORA-06512: at line 1
12.02.2009     23:21:20     BR0886E Checking/collecting statistics failed for table SAPPB1./BIC/FZPPC0002
i can temporary fix this problem when i delete and recreate index via SE14, but this help only for one next running update statistics, every next running update statistics has same error: index "SAPPB1"."/BIC/FZPPC0002~010" or partition of such index is in unusable state. Exist any definitive solution for this problem. Thanks

Hi,
Two methods for checking/repairing Indexing issues
1)RSRV for a particular cube
2)SAP_INFOCUBE_INDEXES_REPAIR report
You can also use this sql to rebuild an Index.
alter index <index name> rebuild online; Or you can rebuild Index by using ABAP report 'RSANAORA'.
Please check below thread it may help you.
/message/6483705#6483705 [original link is broken]
https://forums.sdn.sap.com/click.jspa?searchID=12942068&messageID=2052264
Thanks,
Sushil

Indexes are in unusable state

hi
i am beginner....
indexes are in unusable state...
how can i make it actual state

Maybe you can use
alter index your_index_name rebuild online;?

ORA-01502 : index SYS.I_PROCEDURE1 is in unusable state

Oracle EE 9.2.0.8 on Windows 2003 SP2
Some SYS tables where moved by mistake with statement : "alter table sys.xxx move tablespace system;"
This caused some unusable SYS indexes but I cannot rebuild them. Each time I get same error :
ORA-01502: index 'SYS.I_PROCEDURE1' or partition of such index is in unusable state
Tracing showed me that some recursive SQL is going on and that fails because of the unusable index I_PROCEDURE1
This is the recursive sql who fails :
SQL> select audit$,options from procedure$ where obj#=115;
ERROR at line 1:
ORA-01502: index 'SYS.I_PROCEDURE1' or partition of such index is in unusable state
How do get out of this situation ?
Have already tried without succes :
- alter session set skip_unusable_indexes=true;
- altered some parameters to favor full table scans (optimizer_mode, db_file_multi_block_read_count
- tried to drop index (same error)
Thanks.
Benny Derous

Are you saying that you cannot rebuild that particular index, or other indexes? It works for me:orcl> alter index sys.i_procedure1 rebuild;
Index altered.
orcl> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
PL/SQL Release 11.2.0.3.0 - Production
CORE 11.2.0.3.0 Production
TNS for 32-bit Windows: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
orcl>

In what way can an index go in invalid state????????

I did a lot of activity in my database and i found one of my index is in invalid state...i got an error
......Error occured is ORA-01502: index 'MUMBAI.SYS_C0013323' or partition of such index is in unusable state......
Can anybody tell me what activity (or set of activies) can lead to invalid state of Index????/
How to check if any other index is is Invalid state????????
Thanx in Advance
Gagan

Hello,
Following are some reason for index to be marked UNUSED;
Operations like Import Partition or conventional path SQL*Loader
that offer an option to bypass local index maintenance. When the
Import is complete, the affected local index partitions are marked
IU.
Partition maintenance operations like ALTER TABLE MOVE PARTITION
that change rowids. These operations mark the affected local index
partition and all global index partitions IU.
Partition maintenance operations like ALTER TABLE SPLIT PARTITION
that modify the partition definition of local indexes but do not
automatically rebuild the index data to match the new definitions.
These operations mark the affected local index partitions IU. ALTER
TABLE SPLIT PARTITION also marks all global index partitions IU
because it results in changes to rowids.
Index maintenance operations like ALTER INDEX SPLIT PARTITION that
modify the partitioning definition of the index but do not
automatically rebuild the affected partitions. These operations
mark the affected index partitions IU. However, if you split a
USABLE partition of a global index, resulting partitions are created
USABLE. If the partition that was split was marked IU, then so are
the partitions resulting from the split. Note that dropping a
partition of a global index that is either IU or is not empty causes
the next partition of the index to become IU.
Above points are mentioned at Metalink.
Hope that this will help you.....

Using UNUSABLE on Unique Index gives "initially in unusable state" error

I am doing the following:
1. Truncate table
2 Alter PK Index Disable
2. Alter Unique Index Unusable
3. Insert /*+ APPEND NOLOGGING*/ into my table
My problem is, I get an "ORA-26026: unique index ... initially in unusable state" error when I try to do the Insert. If I make the Unique index non-unique it isn't a problem. If I drop the index and recreate it its not a problem - so uniqueness doesn't appear to be the issue. Can you not use UNUSABLE with a Unique index, I couldn't find any reference to this in the 10g docs.
I am using 10.1.0.4.
Thanks
Richard

26026, 0000, "unique index %s.%s initially in unusable state"
//* Cause: A unique index is in IU state (a unique index cannot have
//* index maintenance skipped via SKIP_UNUSABLE_INDEXES).
//* Action: Either rebuild the index or index partition, or use
//* SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.

Indexed columns became unusable. how to resolve it

Hi All,
i have truncated the data using alter command as follows .
alter table table_one truncate partition (partitionname);
After that i was trying to insert data into that table am getting an error. And all indexes columns became unusable. i think doing truncate the partition i am facing this problem.
can any one suggest me to how to make it.. usable.
i am using tode
Thanks
Sree

874823 wrote:
Hi All,
i have truncated the data using alter command as follows .
alter table table_one truncate partition (partitionname);
After that i was trying to insert data into that table am getting an error. And all indexes columns became unusable. i think doing truncate the partition i am facing this problem.
can any one suggest me to how to make it.. usable.
i am using tode
Thanks
SreeI assume you have an unusable global index?
http://docs.oracle.com/cd/B10501_01/server.920/a96521/partiti.htm#27573
Rebuild the index, and next time include the "update global indexes" clause with the truncate command.

Drop Partition update Global Indexes

hello Gurus,
what will happen internally when issue a command
alter table tab_name drop partition part_name update global indexes;
why my insert statement waiting to complete this task on " cursor: pin S wait on X "
thanks in advance ..

Several times i also noticed that wait event for some jobs on 10 2 0 4 on hpux.
I didn't found out what was the reason.
It seems this wait event can be easly related to some bugs.
http://karenmorton.blogspot.com/2008/08/strange-parsing-behavior.html
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents003.htm#sthref3012

Problems with Hints in abap code to use an index in a Select statement

Hi,
I want to use an especific index in a select statement but I can´t get it. I use de next statement:
SELECT ltaklgnum ltaktanum ltakvbeln ltaptapos ltapnltyp ltappvqui
       FROM ltak AS ltak INNER JOIN ltap AS ltap
                        ON ltaktanum = ltaptanum
                        AND ltaklgnum = ltaplgnum
       INTO TABLE l_t_tanum_silo
       WHERE ltap~lgnum EQ ip_lgnum
         AND ltap~pquit EQ ' '
         AND ltak~lgnum EQ ip_lgnum
         AND ltak~kquit EQ ' '
         AND ltak~queue EQ ip_queue
         %_HINTS DB2 ''.
We have DB2 for Linux Unix and Windows 9.5 as DB system.
How can I fix this?
Thanks a lot.
Regards

The DB2 for Linux Unix and Windows is coded DB6 for SAP and not DB2
Look at the following OSS notes
- [Note 129385 - Database hints in Open SQL|https://service.sap.com/sap/support/notes/129385]
- [Note 150037 - Database hints in Open SQL for DB6 (DB2 for LUW)|https://service.sap.com/sap/support/notes/150037]
- [Note 1270314 - DB6: DB2 9.5 Perf. degrad. for queries with INLIST clause|https://service.sap.com/sap/support/notes/1270314]
- [Note 868888 - DB6: Optimization Guidelines|https://service.sap.com/sap/support/notes/868888]
You should use a
SELECT ltak~lgnum ltak~tanum ltak~vbeln ltap~tapos ltap~nltyp ltap~pvqui
FROM ltak AS ltak INNER JOIN ltap AS ltap
ON ltak~tanum = ltap~tanum
    AND ltak~lgnum = ltap~lgnum
INTO TABLE l_t_tanum_silo
WHERE ltap~lgnum EQ ip_lgnum
    AND ltap~pquit EQ ' '
    AND ltak~lgnum EQ ip_lgnum
    AND ltak~kquit EQ ' '
    AND ltak~queue EQ ip_queue
%_HINTS DB6 '<IXSCAN TABLE=''LTAP'' INDEX=''"LTAP~M"'' />'.
In note 868888 there is a sample for a join.
SELECT A~TABSPACE
FROM TADB6 AS A
JOIN IADB6 AS B ON A~TABART = B~TABART
%_HINTS DB6 '<NLJOIN><IXSCAN TABLE=''IADB6'' />'
        DB6 '<IXSCAN TABLE=''TADB6'' /></NLJOIN>'.
Regards

SPLIT PARTITION creating the index in different Table Space

I am splitting the table every month. After splitting the Index is also Splitting. (It is natural). But it is creating in default table Space.
I want to split INDEX and creating into the index table space “ACTIVITY_IND_TS_1”
CREATE TABLE PART
PK_KEY NUMBER(15) NOT NULL,
PK_ID NUMBER(1) NOT NULL
TABLESPACE USERS PARTITION BY RANGE (PK_ID)
PARTITION PK_ID_PRD1 VALUES LESS THAN (1)
LOGGING
TABLESPACE ACTIVITY_TAB_TS_1,
PARTITION PK_ID_PRD2 VALUES LESS THAN (2)
LOGGING
TABLESPACE ACTIVITY_TAB_TS_1,
PARTITION PK_ID_PRD3 VALUES LESS THAN (3)
LOGGING
TABLESPACE ACTIVITY_TAB_TS_1,
PARTITION PK_ID_PRD4 VALUES LESS THAN (4)
LOGGING
TABLESPACE ACTIVITY_TAB_TS_1,
PARTITION PK_ID_PRD_MAXVALUE VALUES LESS THAN (MAXVALUE)
LOGGING
TABLESPACE ACTIVITY_TAB_TS_1
NOCACHE
NOPARALLEL
ENABLE ROW MOVEMENT;
CREATE INDEX PART_IX ON PART(PK_ID)
LOCAL (PARTITION PK_ID_PRD1 TABLESPACE ACTIVITY_IND_TS_1,
PARTITION PK_ID_PRD2 TABLESPACE ACTIVITY_IND_TS_1,
PARTITION PK_ID_PRD3 TABLESPACE ACTIVITY_IND_TS_1,
PARTITION PK_ID_PRD4 TABLESPACE ACTIVITY_IND_TS_1,
PARTITION PK_ID_PRD_MAXVALUE TABLESPACE ACTIVITY_IND_TS_1)
PARALLEL
NOLOGGING;
select unique tablespace_name from user_tab_partitions; -- ACTIVITY_TAB_TS_1
select unique tablespace_name from user_ind_partitions; -- ACTIVITY_IND_TS_1
ALTER TABLE PART SPLIT PARTITION PK_ID_PRD_MAXVALUE
AT (5) INTO (PARTITION PK_ID_PRD5, PARTITION PK_ID_PRD_MAXVALUE);
select unique tablespace_name from user_tab_partitions; -- ACTIVITY_TAB_TS_1
select unique tablespace_name from user_ind_partitions; -- ACTIVITY_TAB_TS_1 ACTIVITY_IND_TS_1
Edited by: sk123 on May 5, 2009 1:05 PM

Hello,
Once you split partition you need to rebuild indexes if you want indexes to be in their own tablespaces
ALTER TABLE PART
SPLIT PARTITION PK_ID_PRD_MAXVALUE AT
(6)
INTO (PARTITION PK_ID_PRD5
TABLESPACE ACTIVITY_TAB_TS_1
PARTITION PK_ID_PRD_MAXVALUE);
ALTER INDEX PART_IX
REBUILD PARTITION PK_ID_PRD5
TABLESPACE ACTIVITY_IND_TS_1;
ALTER INDEX PART_IX
REBUILD PARTITION PK_ID_PRD_MAXVALUE
TABLESPACE ACTIVITY_IND_TS_1;Regards

Exchange Server 2013 Content Index is in "Unknown" state.

Hi Experts,
We have two Exchange Server 2013 CU3 installed in our customer premises 6 months back on top of Windows Server 2012 OS.
From last week, we are getting the content index status as "Unknown" while checking the "Get-Mailboxdatabasecopystatus".
We have tried to reseed the database by using "update-mailboxdatabasecopy -identity <db> -deleteexistingfiles then we came to know the server is not responding on port 3863.
Attached image is for your reference.
Need support from experts to resolve at the earliest.
Regards,
Santhosh
Santhosh Sivaraman MCITP: Microsoft Exchange Server 2007/2010 | MCSE/MCSA

Hi,
I had the same issue and was able to solved by recreate the search index component on the mailbox servers
Recreate the Search Foundation from scratch
Stop and disable the search services and rename the Data Folder "C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data"
Open power shell and navigate to C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Installer
Run the command : .\installconfig.ps1 -action I -dataFolder "c:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data"
Output should be like
[PS] C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Installer>.\installconfig.ps1 -action I -dataFolder "C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data"
Configuring Search Foundation for Exchange....
Successfully configured Search Foundation for Exchange
Rename the Index files for the database that are active on the node .
Start the Search Services
Removed a configuration entry that refers to the ContentSubmitters group. This entry is present in four XML files. Each file is called WcfConfigurator.
you can find each file in the following folder:
%ExchangeInstallPath%\Bin\Search\Ceres\HostController\Data\Nodes\Fsis\NODENAME\Configuration\Local
Here, “%ExchangeInstallPath%” is the Exchange installation root path, and the placeholder NODENAME represents one of the following names. (There is one name for each of the four files that are to be edited.)
AdminNode1
ContentEngineNode1
IndexNode1
InteractionEngineNode1
These are text files. You can use Notepad or any other convenient plain text editor to change them. Make sure that you make only the change that is described here.
Each file contains at most one line that contains the following: <AuthorizedRole>ContentSubmitters</AuthorizedRole>
Remove this line, and then save the file. Repeat this operation for each of the four files, and then restart the Microsoft Exchange Search Host Controller service.
Found the Index files in Crawling state as expected instead of Unknown.
Once all the Active copies are healthy and still the copies in failed and suspended state, then you can reseed the catalog files only using the below command
Update-MailboxDatabaseCopy -Identity BD\MBserver –CatalogOnly
Good Luck..
Regards,
Ayman Saleh

Table partitioning and global indexing

hello all,
the requirement is to do table partitioning with global indexing! & also thr r almost 60 crores of rows are there! so can you tell me the way which can be done better and also please provide me the procedure with documents?
thanks in advance!

Hi,
have a look at online redefinition of a table, see Oracle Manual (10.2): http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tables.htm#ADMIN01514
The steps are described in the manual.
Herald ten Dam
Superconsult.nl

ADD PARTITION시 NEW LOCAL INDEX PARTITION에 관하여

제품 : ORACLE SERVER
작성날짜 : 2004-08-16
ADD PARTITION시 NEW LOCAL INDEX PARTITION에 관하여
==================================================
(※ Oracle Partitioning Option은 8~10g Standard Edition에서는 지원하지 않는다.)
개 요
=======
ALTER TABLE ADD PARTITION을 할 경우 table partition의 경우 table partition,
tablespace, physical storage attribute를 지정할 수 있으나,
local index partition의 경우 관련 syntax를 지원하지 않는다 (8.1.6 현재)
오라클은 자동으로 index partition, tablespace, physical storage attribute를 지정한다.
(ALTER TABLE SPLIT PARTITION도 마찬가지)
new index partition의 이름은 new table partition과 같은 이름이 할당되고,
tablespace, physical storage attribute는 local index에 지정된 default값이 사용되고,
local index에 지정된 default값이 없으면 user의 default tablespace가 사용된다.
그러므로 PARTITION 추가하여 사용하는 경우 index partition 관리에 주의가 요구된다.
다음은 ALTER TABLE ADD PARTITION한 이후에 index partition을 관리하는 예제이다.
예 제
=======
-- Create partition table --
CREATE TABLE tbl_emp (
empno NUMBER,
ename VARCHAR2(20),
job VARCHAR2(20)
PARTITION BY RANGE ( empno ) (
PARTITION pt_tbl_emp01 VALUES LESS THAN( 1000 ) TABLESPACE data_emp01,
PARTITION pt_tbl_emp02 VALUES LESS THAN( 2000 ) TABLESPACE data_emp02,
PARTITION pt_tbl_emp03 VALUES LESS THAN( 3000 ) TABLESPACE data_emp03
-- Create local index --
CREATE INDEX idx_emp ON tbl_emp( empno )
TABLESPACE users --> 여기서 local index default tablespace 지정
LOCAL (
PARTITION pt_idx_emp01 TABLESPACE indx_emp01,
PARTITION pt_idx_emp02 TABLESPACE indx_emp02,
PARTITION pt_idx_emp03 TABLESPACE indx_emp03
-- PK 설정 --
ALTER TABLE tbl_emp ADD CONSTRAINT pk_emp PRIMARY KEY ( empno );
-- Local Index를 PK index로 사용함을 확인 --
SELECT index_name FROM user_indexes WHERE table_name = 'TBL_EMP';
INDEX_NAME
IDX_EMP
DROP INDEX idx_emp
ERROR at line 1:
ORA-02429: cannot drop index used for enforcement of unique/primary key
-- Add partition --
ALTER TABLE tbl_emp
ADD PARTITION pt_tbl_emp04 VALUES LESS THAN( 4000 )
TABLESPACE data_emp04;
-- 추가된 Local index partition의 이름, Tablespace를 확인한다 --
SELECT partition_name, tablespace_name, status
FROM user_ind_partitions
ORDER BY 1;
PARTITION_NAME TABLESPACE_NAME STATUS
PT_IDX_EMP01 INDX_EMP01 USABLE
PT_IDX_EMP02 INDX_EMP02 USABLE
PT_IDX_EMP03 INDX_EMP03 USABLE
PT_TBL_EMP04 USERS USABLE
-- Tablespace는 local index의 default tablespace에 생긴다 --
SELECT index_name, def_tablespace_name
FROM user_part_indexes;
INDEX_NAME DEF_TABLESPACE_NAME
IDX_EMP USERS
--<< Local index partition name 변경 >>--
ALTER INDEX idx_emp
RENAME PARTITION pt_tbl_emp04 TO pt_idx_emp04;
--<< Local index tablespace 변경 >>--
ALTER INDEX idx_emp
REBUILD PARTITION pt_idx_emp04 TABLESPACE indx_emp04;
SELECT partition_name, tablespace_name, status
FROM user_ind_partitions
ORDER BY 1;
-- 변경된 Local index partition의 이름, Tablespace를 확인한다 --
PARTITION_NAME TABLESPACE_NAME STATUS
PT_IDX_EMP01 INDX_EMP01 USABLE
PT_IDX_EMP02 INDX_EMP02 USABLE
PT_IDX_EMP03 INDX_EMP03 USABLE
PT_IDX_EMP04 INDX_EMP04 USABLE
* 다음과 같이 local index의 default tablespace를 변경할 수도 있다.
alter index <indexname>
modify default attributes tablespace <new tablespace name>;

>
1. If i drop one partition of a table why all the local indexes(year_1998 ... year_2000) get dropped but year_idx remains in database? I couldn't find index in dba_part_indexes view but i could find only year_idx line in dba_indexes view.
>
After dropping a partition, the row in DBA_PART_INDEXES still exists, so I'm unsure why it does not appear on your system. The index however does not appear in the DBA_INDEXES view before or after the drop partition:
for example
SQL> select owner, index_name from dba_part_indexes where
2 index_name = 'YEAR_IDX';
OWNER                          INDEX_NAME
APPS                           YEAR_IDX
SQL> alter table all_facts drop partition year_1999;
Table altered.
SQL> select owner, index_name from dba_part_indexes where
2 index_name = 'YEAR_IDX';
OWNER                          INDEX_NAME
APPS                           YEAR_IDX
SQL> select owner, index_name from dba_indexes
2 where index_name = 'YEAR_INDEX';
no rows selected

A question regarding database table partitioning and table indexes in 10g

We are considering partitioning a large table in our 10g database, in order to improve response time. I believe I understand the various partitioning options, but am wondering about the indexes built over the table. When the table is partitioned, will the indexes also be partitioned "automatically"? Or do I need to also partition the indexes as well?
Thank you in advance to any and all who respond to this question.

Hello,
When you build your partiton table you just need to create indexes locally and they will be partitioned automatically, see following example
CREATE TABLE YY_EVENT
PART_KEY       DATE                              NOT NULL,
SUBPART_VALUE NUMBER                             NULL,
EVENT_NAME     VARCHAR2(30 BYTE)                  NULL,
EVENT_VALUE    NUMBER                             NULL
TABLESPACE TEST_DATA
PARTITION BY RANGE (PART_KEY)
PARTITION Y_EVENT_200901 VALUES LESS THAN (TO_DATE(' 2009-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    TABLESPACE TEST_DATA,
PARTITION Y_EVENT_200902 VALUES LESS THAN (TO_DATE(' 2009-03-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    TABLESPACE TEST_DATA
-- This will create paritioned indexes automatically
CREATE INDEX MY_IDX ON YY_EVENT
(EVENT_NAME)
TABLESPACE TEST_DATA
LOGGING
LOCAL;Regards
Edited by: OrionNet on Feb 25, 2009 12:05 PM

Partition of such index is in unusable state

Similar Messages

Maybe you are looking for