A tablespace was dropped a long time ago but Capacity Manager is still showing it in the console tree. According to help file, under topic "A look at the Capacity Manager Tree", indicates that a tablespace may be shown as historic and it is shown when a tablespace is found only in the repository but not in the data dictionary for the monitored database. This circumstance can occur when a snapshot has not been collected since a tablespace was dropped. The tablespace node is cleared the next time a snapshot is collected for its database.
However, the snapshot job has been run successfully many times.
Product defect.
WORKAROUND
Determine the database label for the database (the name it appears under in the CMO navigation panel for databases) and the tablespace name.
Logon to the repository database as the owner of the CMO repository and run the following:
delete from quest_cmo_capacity_object a
where a.object_name = '&&ENTER_TABLESPACE_NAME_HERE'
and a.database_id in (select b.database_id from quest_cmo_databases b
where b.database_label = '&&ENTER_DATABASE_LABEL_HERE')
and a.object_type_code in (select c.object_type_code
from quest_cmo_object_type c
where c.object_type = 'TABLESPACE') ;
Since "on cascade delete" foreign keys is enabled, deleting this row from the CMO object table should also delete all the history for that object.
STATUS
Waiting for fix in a future release of Capacity Manager for Oracle.
