Document Type | Troubleshooting
Category | Patch/Upgrade
Applicable Product Versions | 6FS06, 6FS07, 6FS07PS, 7FS02, 7FS02PS
Document Number | TPATS018
Issue
When performing a global index parallel rebuild, temporary objects used remain in the recyclebin, resulting in an increase in recyclebin contents and consequently occupying unnecessary space.
The presence of temporary tables remaining in the Recyclebin can be confirmed as follows.
SQL> select * From dba_recyclebin; TIBERO _TIBERO_TBL4580000 _TIBERO_TBL4579900 TABLE USR 2024-01-26:10:58:33 2024-01-26:10:58:35 4444938 TIBERO _TIBERO_IDX4580100 _TIBERO_IDX4579900 INDEX USR 2024-01-26:10:58:34 2024-01-26:10:58:35 4444938 45800
Cause
Certain DDL operations internally create temporary objects and then delete (drop) them.
This issue occurs because the dropped temporary objects are stored in the Recyclebin due to the process involved.
In the slog, the drop of the temporary table and the handling of that drop involving rename and recyclebin can be confirmed as follows.
[2024-01-26T10:58:33.470221] [DDL-208] [I] Executing DDL: alter index idx2 rebuild parallel 8
[2024-01-26T10:58:33.472117] [DDL-208] [I] Executing internal DDL: CREATE INTERNAL TABLE "TIBERO"."_TIBERO_TBL4579900" AS SELECT /*+ DEFAULT_STAT */ * FROM "TIBERO"."TRR" WHERE ROWNUM < 1;
[2024-01-26T10:58:34.138075] [DDL-208] [I] Internal DDL execution succeeded
[2024-01-26T10:58:34.167134] [DDL-208] [I] Executing internal DDL: CREATE INTERNAL INDEX "TIBERO"."_TIBERO_IDX4579900" ON "TIBERO"."_TIBERO_TBL4579900"("C1","C2") GLOBAL PARTITION BY HASH("C1","C2") PARTITIONS 8 PARALLEL 8 TABLESPACE "USR" NOLOGGING;
[2024-01-26T10:58:34.455534] [DDL-208] [I] Internal DDL execution succeeded
[2024-01-26T10:58:34.464742] [DDL-208] [I] create isgmt(idxre) obj_id:45799, sgmt_id:45810
[2024-01-26T10:58:34.946201] [DDL-208] [I] Executing internal DDL: DROP TABLE "TIBERO"."_TIBERO_TBL4579900";
[2024-01-26T10:58:34.986640] [DDL-208] [I] Executing internal DDL: ALTER INDEX "TIBERO"."_TIBERO_IDX4579900" RENAME TO "_TIBERO_IDX4580100";
[2024-01-26T10:58:35.135022] [DDL-208] [I] Internal DDL execution succeeded
[2024-01-26T10:58:35.234862] [DDL-208] [I] Executing internal DDL: ALTER TABLE "TIBERO"."_TIBERO_TBL4579900" RENAME CONSTRAINT "_TIBERO_CON1062100728" TO "_TIBERO_CON1062100690";
[2024-01-26T10:58:35.236782] [DDL-208] [I] Internal DDL execution succeeded
[2024-01-26T10:58:35.239235] [DDL-208] [I] Executing internal DDL: ALTER TABLE "TIBERO"."_TIBERO_TBL4579900" RENAME CONSTRAINT "_TIBERO_CON1062200761" TO "_TIBERO_CON1062200026";
[2024-01-26T10:58:35.240047] [DDL-208] [I] Internal DDL execution succeeded
[2024-01-26T10:58:35.242450] [DDL-208] [I] Executing internal DDL: ALTER TABLE "TIBERO"."_TIBERO_TBL4579900" RENAME CONSTRAINT "_TIBERO_CON1062300783" TO "_TIBERO_CON1062300279";
[2024-01-26T10:58:35.243289] [DDL-208] [I] Internal DDL execution succeeded
[2024-01-26T10:58:35.248145] [DDL-208] [I] Executing internal DDL: ALTER TABLE "TIBERO"."_TIBERO_TBL4579900" RENAME TO "_TIBERO_TBL4580000";Solutions
Apply the patch to resolve the issue. (Applied Patch: 317806a)
CautionApply the patch through technical support provided by Tmax Tibero.
NoteYou can resolve the error by setting a workaround as follows.