Skip to Content
0
Jan 23, 2023 at 09:10 AM

Table SXMSCLUP corrupted post Oracle TABLESPACE reorg

169 Views

Dear Expert,

We have a table SXMSCLUP, which has a LOB SYS_LOB0000022703C00008$$ stored under the field CLUSTD. Now this Table is huge and we had raised an Oracle SR to check on this. Oracle suggested that we should go for a reorg of this table in order to free up unused or fragmented space.

We did that and a lot of space was released. Post reorg, from the SAP application side the table SXMSCLUP was corrupted and we had to restore the DB back to its original state (i.e. before reorg) and then the table was again behaving properly.
The table SXMSCLUP has a TABART mapping with "APPL1" "PSAPSTA" in TAORA. We did not consider any changes to be made in TAORA table as part of the reorg.

What we have performed for reorg:

  1. Create new tablespace PSAPSTA_NEW -> add datafiles
    2. ALTER TABLE SAPSTA.SXMSCLUP MOVE TABLESPACE PSAPSTA_NEW;
    3. ALTER TABLE SAPSTA.SXMSCLUP MOVE LOB(CLUSTD) STORE AS SECUREFILE (TABLESPACE PSAPSTA_NEW);
    4. ALTER TABLE SAPSTA.SXMSCLUP MOVE TABLESPACE PSAPSTA;
    5. ALTER TABLE SAPSTA.SXMSCLUP MOVE LOB(CLUSTD) STORE AS SECUREFILE (TABLESPACE PSAPSTA);
    6. DROP TABLESPACE PSAPSTA_NEW

So we just want to understand what are the considerations or steps for correctly performing the reorg activity specific to SAP.

Best Regards


------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.