SHAREPLEX_LOBMAP table is very large and capture is running slow, is there a way to decrease the size
SharePlex_LOBMAP is maintained to track out of row lob mapping information. The LOB map is used by the Capture process to map LOBIDs and rows when supplemental PK/UK logging is not enabled. LOB mapping is enabled by default.
SOLUTION:
If supplemental logging for pk/uk is enabled on source database and application is not using dbms_lob package to write, append or erase lob on source, then
1. stop capture
2. set SP_OCT_ENABLE_LOBMAP=0
sp_ctrl> set param SP_OCT_ENABLE_LOBMAP 0
3. sqlplus onto the source database as SharePlex user
truncate table shareplex_lobmap;
4. start capture
Note: If application is using dbms_lob package to write lob data and you disable this parameter, it is possible to run into out of sync on lob tables. You may want to run compare/repair on lob tables to see if it stays in sync. If it is not in sync, then you should re-enable this parameter by setting it to 1. In future release, additional statistics will be available in 'show capture detail' to help determine if it is safe to disabling lobmap (SPO-13836 Enhancement)