When index is unusable on table, it prevents the updating/inserting of new data
Everyday a clean up task would messed up a partitioned table. Specifically the following command would make the indexes unusable :
ALTER TABLE table_name DROP PARTITION partition_name;
Thus the table would have unusable indexes. This problem prevents from importing new data.
Description of the partitionned table
The table with unusable indexes is partitioned and has two indexes. One index is on the primary key and the other index on a date column MY_TABLE_DATE.
The table is partitioned with the method “Range Partitioning”
Range partitioning maps data to partitions based on ranges of partition key values that you establish for each partition. It is the most common type of partitioning and is often used with dates. For example, you might want to partition sales data into monthly partitions.
The table is partitionned with the date and has a primary key :
create table MY_TABLE
ID NUMBER GENERATED BY DEFAULT AS IDENTITY ,
MY_TABLE_DATE DATE NOT NULL,
NAME VARCHAR2(3) NOT NULL,
SURNAME VARCHAR2(20) NOT NULL,
PARTITION BY RANGE (MY_TABLE_DATE )
(PARTITION P_20100101 VALUES LESS THAN (TO_TIMESTAMP('2010/01/01 00:00:00','YYYY/MM/DD HH24:MI:SS') )
Actually this primary key is a problem according to Oracle documentation. Indeed the partitionned column should be part of the primary key. Read on from « Partitioned Index-Organized Tables » :
For partitioning an index-organized table
Partition columns must be a subset of primary key columns
To make the partitionned column part of the primary key , do something like this:
ALTER TABLE MY_TABLE DROP CONSTRAINT TABLE_PK;
ALTER TABLE MY_TABLE ADD CONSTRAINT TABLE_PK PRIMARY KEY (ID, MY_TABLE_DATE) USING INDEX LOCAL TABLESPACE tab_p_specified_space;
Unfortunately this modification of the partitioned table did not fix the problem either.
In order to fix unusable indexes I used the command “UPDATE INDEXES” suggested by this article https://docs.oracle.com/database/121/VLDBG/GUID-1D59BD49-CD86-4BFE-9099-D3B8D7FD932A.htm#VLDBG1122
“UPDATE INDEXES” will rebuild the indexes after the command DROP PARTITION is executed.
requestDeletePartition := 'ALTER TABLE BASE.MY_TABLE DROP PARTITION TO_CHAR(Date,'YYYYMMDD') || 'UPDATE INDEXES' ;
Unfortunately the result was the following error :
SQLCODE : -14048
SQLERRM : ORA-14048: a partition maintenance operation may not be combined with other operations
I spend sometimes trying to figure out the solution for this error . The solution is simple . I added a space between ‘ and UPDATE INDEXES like this :
requestDeletePartition := 'ALTER TABLE BASE.MY_TABLE DROP PARTITION TO_CHAR(Date,'YYYYMMDD') || ' UPDATE INDEXES' ;
The solution will rebuild indexes after dropping the partition. This fix is not sustainable for every scenario. Because it means to launch the command of rebuilding indexes everyday on a table with potentially millions of data. When the indexes are being rebuilt, the table cannot be used. Thus this command should be launched when nobody is using the application.
Another tested solution
On google we can quickly find interesting articles how to fix the problem :
ALTER INDEX index_name REBUILD
This is a similar solution to the previous one. The table is not usable when the indexes are being rebuilt.
Other solution possible
I did not test this solution but it should fix the problem too.