A Standard Reorg (offline) with Rebuild Index Online option selected was aborted. There is a SYS_JOURNAL_<object_id> table remaining on the target tablespace. In Scripts/Job Monitor, there is a Clean up option but when selected, it gives a "Cannot cleanup because this is not a LiveReorg script".
When rebuilding an index online, it will do a full tablescan on the base table. At the same time it will maintain a journal table for DML data, which has changed during this index rebuilding operation.
RESOLUTION 1
SMON should cleanup the failed online index rebuild operation and so correct this. However, if the table is highly active with transactions, SMON may not be able to get the required lock and so the index will not get cleaned up. In such situations, manually cleanup the failed index rebuild using the DBMS_REPAIR.ONLINE_INDEX_CLEAN procedure.
The dbms_repair.online_index_clean would solve the problem, however this is not available on 10GR1 or in previous releases.
RESOLUTION 2
Identify and drop/rename the related journal tables manually:
SQL> Select Object_Name, Object_Type From Dba_Objects Where Object_Name Like 'SYS_JOURNAL%';
Drop/Rename the tables that resulted from the above query.
Restarting the database is required after removing the journal table otherwise ORA-00600: may be encountered as documented in Note 351585.1 (Metalink)
Following Metalink Doc ID have been quoted
247487.1
351585.1
272762.1
803008.1
427626.1
