Skip to main content

Search

Welcome to Tibero GTS!

system tablespace full phenomenon (after index online rebuild)

Document Type | Troubleshooting

Category | Utility

Applicable Product Versions | 6FS06, 6FS07

Error Codes | 8033, 6001

Document Number | TUTTS009

 

Issue

After the index rebuild operation, a 6001 error occurs following the drop action of the created JOURNAL TABLE.
Also, when executing an INSERT statement on a specific column from the AP client, an 8033 error occurs.
Note
  • 6001 error: ERROR_DD_OBJ_NOTFOUND(-6001) DD search failed
  • 8033 error: Specified schema object was not found.
 

 

Cause

After performing an index online rebuild, the size of SYS_JOURNAL_5647 in the system tablespace gradually increases, causing a tablespace full phenomenon.
Considering that the segment size of the journal table is increasing, it indicates that journaling is continuously maintained.

During the online rebuild, a statement cancel was performed but an unrepaired index remained, and the journal table existed. At this time, instead of repairing, the journal table was forcibly dropped, and although journaling was specified for the index, the actual journal table was missing, causing a not found error during DML operations.
 
 

Solutions

1. Check for indexes that remain unrepaired

select * from _dd_idxon;

OBJ_ID  TYPE_NO   FLAGS
------ --------- -------
 5647        1       0

 

2. Perform DBMS_REPAIR.ONLINE_INDEX_CLEAN

After performing the repair, the system tablespace usage does not increase and no errors occur.
DECLARE
isClean BOOLEAN;
BEGIN
isClean := FALSE;
isClean := DBMS_REPAIR.ONLINE_INDEX_CLEAN( 5647);
END;
/

 

 

 

Related to