Unusual large DB table SYS_LOB0000063510C00085$$
Hi Team,
We are trying to understand why SYS_LOB0000063510C00085$$ is significantly huge?Is there any remediation to fix the size of this table? We are in the process of migration from 5.5 to 7.2 and would like to see if there is an opportunity to that this table can be skipped while exporting or could be reduced in size?
NBB_WORK is our work table. The SYS_LOB0000063510C00085$$ table corresponding to it(last row below) is of very large size.
OWNER SEGMENT_NAME SEGMENT_TYPE S.BYTES/1024/1024 TABLE_NAME COLUMN_NAME
------------------------------ ---------------------------------------------------------------- ------------------ ----------------- ------------------------------ ------------------------------
Hi Team,
We are trying to understand why SYS_LOB0000063510C00085$$ is significantly huge?Is there any remediation to fix the size of this table? We are in the process of migration from 5.5 to 7.2 and would like to see if there is an opportunity to that this table can be skipped while exporting or could be reduced in size?
NBB_WORK is our work table. The SYS_LOB0000063510C00085$$ table corresponding to it(last row below) is of very large size.
OWNER SEGMENT_NAME SEGMENT_TYPE S.BYTES/1024/1024 TABLE_NAME COLUMN_NAME
------------------------------ ---------------------------------------------------------------- ------------------ ----------------- ------------------------------ ------------------------------
OSB_RULES_PRD SYS_LOB0000063650C00049$$ LOBSEGMENT 115.1875 PC_ASSIGN_WORKLIST PZPVSTREAM
OSB_RULES_PRD SYS_LOB0000063890C00085$$ LOBSEGMENT 160 NBB_BRN_WORK PZPVSTREAM
OSB_RULES_PRD SYS_LOB0000063728C00053$$ LOBSEGMENT 379.1875 PR4_RULE_PROPERTY PZPVSTREAM
OSB_RULES_PRD SYS_LOB0000063734C00039$$ LOBSEGMENT 396.1875 PR4_RULE_FILE PZPVSTREAM
OSB_RULES_PRD SYS_LOB0000063725C00051$$ LOBSEGMENT 904.125 PR4_RULE_FLOW PZPVSTREAM
OSB_RULES_PRD SYS_LOB0000063722C00123$$ LOBSEGMENT 1984.125 PR4_RULE PZPVSTREAM
OSB_RULES_PRD SYS_LOB0000087496C00085$$ LOBSEGMENT 2884.1875 NBB_RMT_WORK PZPVSTREAM
OSB_RULES_PRD SYS_LOB0000063510C00085$$ LOBSEGMENT 521128.125 NBB_WORK PZPVSTREAM
Pegasystems Inc.
AU
From the naming convention, I understand that the NBB_WORK is your work object table. It looks like this table contains huge number of work objects, hence huge in size.
I would suggest you to purge & archive (house keeping) of old work objects so that the table size can be reduced before migration.
CIBC
CA
Hi Krishna,
Thanks for the reply. Yes NBB_WORK is our work table but it is 6+ GB only. Our concern is the segment table "SYS_LOB0000063510C00085$$" which is 500 GB+. Do we need to keep this table or we can delete the data in the table. Seems to be its a system generated table. Please suggest if we can delete data in this table or ignore this table during migrating to PEGA 7.2 version.
Regards
Sourav
Pegasystems Inc.
US
That SYS_LOB* table is a database system table. In some databases like Oracle and DB2 if a blob column is above a certain size the database will store the blob in a separate system table instead of inline with the other columns in that row. Essentially what is in the pzPVStream column in your work table for example is probably just a pointer to the actual location of the blob in this sys_lob table. If you delete data from this table you are removing the blob. Talk to your DBA about this table but I certainly would not be deleting data from it. You should look into purge/archive for older records.