Posted: 30 Sep 2016 15:11 EDT Last activity: 5 Oct 2016 8:23 EDT
Unusual large DB table SYS_LOB0000063510C00085$$
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_WORKis our work table. The SYS_LOB0000063510C00085$$ table corresponding to it(last row below) is of very large size.
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.
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.