This content has been marked as final. Show 5 replies
This error means that the ILM Assistant cannot properly determine which tablespace the table currently resides on. Iis independent of the setup of the storage tiers and lifecycle definitions.
I have been unable to reproduce this error, can you give me some addition information to help diagnose it -
What version of the database and the ILM Assistant are you running?
Does this problem occur for just that one table, several tables, or all tables?
Is there anything special about the failing table(s)? Is it an IOT? Use object columns?
Has the table been manually altered since the last table list refresh in the ILM Assistant?
I'm using version 1.2 of ILM and the database is version 10.2.0.3.
This happens for a number of tables that I am working with in this tablespace and there's nothing special about the table - already partition on the primary read-write. No objects on the table and it's not an IOT.
The table is static and there are no changes to the table since the last refresh.
Found the issue. The table was listed as a Candidate table and table partitioning unavailable. This table has a range partition on it - but the key is a surrogate key (int) not on a date column and this seems to cause the issue.
So - in the current setup I will have to re-configure my table and add a date column and partition by that column.
Yes, in the current version we only support partition level management for tables with range partitioning on a date column. In future versions of the tool, there will likely be support for additional types of partitioning and non-date partitioning keys.
I am still not certain as to what caused the error you were seeing though. When I create a table that is partitioned by range on an integer column, it shows up in the Lifecycle Tables screen as having Incompatible partitioning and being Ineligible for management.