Solution : https://service.sap.com/sap/support/notes/1430621 (SAP Service marketplace login required)
Summary :
The SAP note addresses performance issues and lock-wait situations in the VBDATA table on DB2 LUW due to data type definitions. These problems are linked to the use of LONG VARCHAR FOR BIT DATA, causing internal locks and severe performance degradation when combined with high concurrent UDI and SELECT operations. From DB2 LUW 9.7 onwards, changing to BLOB(32K) reduces these issues considerably because of LOB inlining. The recommended solution involves replacing LONG VARCHAR with VARCHAR(), creating special tablespaces and bufferpools, and using the Online Table Move (OTM) tool to migrate the table effectively, ensuring data security and integrity by avoiding unwanted codepage conversions.
Key words :
heavy concurrent update / delete / insert, sap update processes perform badly, terms db2luw db6 vbdata update, lob data implies internal locks, create temporary tablespace psaptemp32 pagesize 32, create tablespace abc#vbdatad pagesize 32, create tablespace abc#vbdatai pagesize 32, 'abc#vbdatad' 'abc#vbdatai' '', field undergo codepage conversion, pagesize 32k create bufferpool
Related Notes :
| 1543745 | DB6: Using and troubleshooting ADMIN_MOVE_TABLE |
| 1451361 | DB6: Best Practices for HP-UX systems running DB2 LUW |
| 1423066 | Optimization of the performance in EWM |
| 1039544 | DB6: Stored procedure for online table move |
| 29824 | DB6: Mapping of data types (DDIC -> DB) |