Solution : https://service.sap.com/sap/support/notes/116698 (SAP Service marketplace login required)
Summary :
This SAP Note addresses performance issues and deadlocks related to the VB protocol tables (VBHDR, VBMOD, VBDATA) in SAP R/3 environments operating with DB2. The problems arise when DB2 Optimizer uses suboptimal access paths due to the specific table characteristics influenced by RUNSTATS. To resolve these issues, the note suggests ensuring only the primary index exists for each table, setting the VOLATILE attribute in DB2 V8, and extensively updating catalog statistics for DB2 V7. The process involves manipulating numerous system catalog tables to maintain optimal system performance and avoid further statistics-based reoptimizations.
Key words :
vb protocol tables includes, asynchronous update protocol tables, vb protocol tables, vb protocol table, frequent deadlocks involving, optimal access path, avoid regularly repeating, asynchronous update protocol, asynchronous update processing, systables set cardf=-1
Related Notes :
| 765983 | DB2/zOS: Reducing number of DSNACCOR REORG recommendations |
| 711245 | DB2/390: Catalog modifications |
| 507824 | DB2/390 V7: Real Time Statistics and DSNACCOR |
| 192320 | DB2/390: Ensuring index access for volatile tables |
| 181286 | DB2/390: Excluding tablespaces from RUNSTATS |
| 132424 | DB2-z/OS: Optimizing access to the TRFC Tables |
| 122599 | DB2/390: Performance of the update |
| 113008 | DB2/390: Maintaining Catalog Statistics |
| 83335 | DB2/390: Deadlocks, bad performance on cluster tables |
| 82953 | DB2/390: Tables Isolation and Buffer Pools Tuning |
| 82072 | DB2/390: Invalidating Cached Statements |